Database

I had this problem before and you should know that its really easy and simple to solve it whether you are installing sql server on vista or seven you should run the installation as administrator another suggestion: if you are the only user on this pc you may find it useful to make your default user the administrator because lots of things on vista and seven really needs administrator previliges to wrok the right way and if you dont have good experience and afraid of missing something just keep the User Account Control turned on and whenever you will do something that might need a permission it will show you a confirmation message even if you are using the adminitrator account I hope it helped :-)

With this approach you could use any over(18) and duration(30) values. select time, value from ( select *, (select count(time) from @temp t2 where t2.time > t1.time and t2.time <= dateadd(mi, 30, t1.time)) as reccount, (select count(time) from @temp t2 where t2.value >= 18 and t2.time > t1.time and t2.time <= dateadd(mi, 30, t1.time)) as okcount from @temp t1 where value > 18 ) t where t.reccount = t.okcount

Change this line set @userID = Scope_Identity(); to set @userID = Scope_Identity(); Select @UserID as UserID As Mika suggested you are not returning a result dataset and @UserID is not an out parameter so the value is being ethered. Never underestimate the power of human stupidity RAH

As this is a concurrency problem it's kinda hard pointing out the problem without seeing the whole scenario. However to demonstrate the problem, do the following: 1. Create a test table and insert data into it CREATE TABLE Test ( a NUMBER PRIMARY KEY NOT NULL ); INSERT INTO Test VALUES (1); COMMIT; 2. Now in this session start a transaction and delete the rows. Leave the transaction open -- SESSION 1 ALTER SESSION SET ISOLATION_LEVEL=SERIALIZABLE; DELETE FROM Test; 3. Start another session and select data from the test table in serializable mode -- SESSION 2 ALTER SESSION SET ISOLATION_LEVEL=SERIALIZABLE; SELECT a FROM Test FOR UPDATE OF a; 4. The session 2 hangs and waits for the result from session 1. Now go back to session 1 and commit the transaction: -- SESSION 1 COMMIT; The result in session 2 is: SELECT a FROM Test FOR UPDATE OF a * ERROR at line 1: ORA-08177: can't serialize access for this transaction Hopefully this clarifies the problem. Best regards, mika The need to optimize rises from a bad design.My articles[^]

Try D-Softs database compare tool

Try this to compare and sync two sql server database D-Softs Database Compare Tool

You can try D-Softs Database Compare Tool

Hi, Could be some kind of syntax issue in the SQL statement itself. Also if I rememeber correctly the parameter usage in the sql statement may be provider specific so if the SQL statement is otherwise fine could it be because of the question mark. You could try literals as a test n order to see if that's the case. Also perhaps the following link would help you: http://msdn.microsoft.com/en-us/library/ms677554(v=VS.85).aspx[^] The need to optimize rises from a bad design.My articles[^]

I wouldn't worry about it: the fact that you've done it is enough. "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me

Here it is: SELECT substring(DATENAME(month, getdate()),1,3) AS MonthName I Love T-SQL "Don't torture yourself,let the life to do it for you." If my post helps you kindly save my time by voting my post. www.aktualiteti.com

Use a Windows Service (for very frequent actions) or a Windows Scheduled Task (for less-frequent actions).

Hello, I managed to get my subscription working. Here is what I have done on my test environment. My client uses oracle-instant-client 11.2.0.1. My db server is running Oracle 11.2.0.1 release. Both client and server are on Centos OS. Previously, I have client on Centos and server on Solaris. I have done quite few tests with combination of different client, server and their OS. I found that the Oracle version and the OS platform contributed to the issue that I had. As a preliminary quick test, I also ran my client on the same box where my db server was running. In my case, this worked fine. Hopefully, this will help. Cheers, sw

You are putting UI processing in the database query, wrong tool for the job. The data is interpreted as a string literal. Move your UI code to RSS, there is a function area where you can put in the code to do that. Never underestimate the power of human stupidity RAH

Check this[^], looks like it could be that the root password could be incorrect. The MySQL root password could be different to your OS root password. It could also be that there is a port conflict which is why it works when you start it in a different way.

Unfortunately conciseness isn't Google's primary strength. :(( Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.

You cannot directly use local variables inside your SQL statements. You can use a Parameter object to pass a value from a variable to the statement. For example see, http://msdn.microsoft.com/en-us/library/ms677589(VS.85).aspx[^] The need to optimize rises from a bad design.My articles[^]

No problem :) The need to optimize rises from a bad design.My articles[^]