Viewing 15 posts - 1,621 through 1,635 (of 7,636 total)
Mike M (9/2/2009)
September 3, 2009 at 11:47 am
As Gus says, you just make a big @cmd string, as big as you need. Put the 'USE [' + @dbname + '];' at the beginning and that should...
September 3, 2009 at 11:41 am
Paul White (9/3/2009)
...
-- Dear Lord, why am I using a cursor here?
-- (probably an updatable, global, dynamic cursor at that!)
...
Definitely my favorite comment of the day! 🙂
September 3, 2009 at 9:58 am
HINT: you are updating the MIN record in a group, but you want to update the MAX instead. So look at changes like: "MAX" vs "MIN", "" and ORDER...
September 3, 2009 at 9:54 am
I believe that eHarper is onto the key to this problem. There is a notorious "feature" of SQL Server and Windows in that their Day Zeros are one day...
September 3, 2009 at 6:58 am
RBarryYoung (8/31/2009)
Where is sp_exec_init documented?
Still waiting for an answer ... ?
September 1, 2009 at 3:39 pm
Can you show us an example of what you mean? Plus the BULK INSERT command that you are currently using? thnx...
September 1, 2009 at 6:39 am
Elliott W (8/31/2009)
September 1, 2009 at 6:08 am
Well, A) you cannot do that, and B) that's not what the error message is about.
August 31, 2009 at 8:08 pm
Try making the t2 index on DATE_TIME into a clustered index.
August 31, 2009 at 8:01 pm
The error message is self-explanatory. What is your question?
August 31, 2009 at 7:36 pm
rajdba (8/31/2009)
...The solution to clear it out is recycle SQL Server or Single User mode with rollback immediate;...
No, these are no different the KILL-ing the process. ROLLBACK IMMEDIATE, simply...
August 31, 2009 at 7:27 pm
Sourav (8/31/2009)
...Any other solution?
No there is no other solution. In fact those previously mentioned are not "solutions" either.
Killing a process is easy, but killing a DML transaction in progress...
August 31, 2009 at 7:23 pm
Viewing 15 posts - 1,621 through 1,635 (of 7,636 total)