Viewing 15 posts - 14,011 through 14,025 (of 18,923 total)
Can we close this fr3@king thread??? It's been almost 170 message already!!!!!
August 24, 2005 at 7:01 am
can you post your final solution so we can benefit from your work?
August 24, 2005 at 6:47 am
You'll have to implement this with a trigger and manually count the next value for the update. Or you could also use a datetime field which would you allow...
August 24, 2005 at 5:51 am
Please do not cross-post, we monitor all boards.
Finish the thread here :
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=9&messageid=213340
August 24, 2005 at 5:49 am
Please do not cross-post, we monitor all boards.
Finish the thread here :
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=9&messageid=213340
August 24, 2005 at 5:49 am
Where is the date kept?? That query becomes almost impossible without that.
August 23, 2005 at 10:31 pm
Do this in the proc :
For each parameter, declare a new variable (same type/length/almost same name). Then copy the parameters' value to those variables, then use those variables in...
August 23, 2005 at 9:54 pm
can you post some sample data and the expected results (gonna be much easier that way)?.
August 23, 2005 at 9:52 pm
I can't even imagine the nightmare... I'm just hopping that it was not a 24/7 shop and that you had time to apply the updates... not to mention a kick...
August 23, 2005 at 9:25 pm
Does it have to be done at the same time of the update or can it be delayed a little? I'm thinking that you could flag the rows that...
August 23, 2005 at 9:22 pm
Table is too large. A row MUST fit in a data page or the insert fails. The data page size is 8060, so any row containing more than...
August 23, 2005 at 9:18 pm
Are you sure they are created?
What happens if you run some insert statements/procs from QA?
August 23, 2005 at 3:13 pm
Viewing 15 posts - 14,011 through 14,025 (of 18,923 total)