Viewing 15 posts - 20,491 through 20,505 (of 59,072 total)
Ed Wagner (6/2/2015)
Jack Corbett (6/2/2015)
Alvin Ramard (6/2/2015)
Brandie Tarvin (6/2/2015)
So long as no one brings up the whipped cream incident, everything should be fine.
What about the pork chops?...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 3, 2015 at 6:01 am
Eirikur Eiriksson (6/2/2015)
Alvin Ramard (6/2/2015)
I might need a pork chop soon. I won't care if it's coated in whipped cream, BBQ sauce, or anything else!
Maybe mint jelly or for...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 3, 2015 at 5:58 am
Lenochka (6/1/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 3, 2015 at 5:56 am
Andy DBA (6/2/2015)
fundpc (6/2/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 3, 2015 at 5:53 am
SQL-DBA-01 (6/2/2015)
Hi Luis
I can go to online site to steal their password if incase I have a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2015 at 8:11 pm
This is a tough one. You have to find the connection on the DB2 side of the house and kill it before the SQL Server connection will rollback.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2015 at 8:03 pm
Ozzmodiar (6/2/2015)
There is a very elegant solution to this problem using the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2015 at 7:59 pm
Frank Cazabon (6/2/2015)
Thanks to all, especially the link to the bug when restarting the service.
It's actually not a "BUG". It's a performance feature. They preallocate 1,000 IDs to...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2015 at 7:56 pm
devsql123 (6/2/2015)
Hi Folks i am in similar situation...can you please see my post and reply me.My Post title is: "Trying to get running Total in SQL Server"
Thanks
Devsql
Eirikur's most recent answer...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2015 at 5:52 am
While this is a good example and it's a good article (thank you SQLMickey for taking the time to write it), it IS an example of 1. "Divide'n'Conquer" methods...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2015 at 5:18 am
There's a pretty good chance on most systems that 1) 100,000 rows would not cause a 1.3 second blip. It would normally take an order of magnitude higher number...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2015 at 9:30 pm
Maybe it's just me. I might be getting too old for this business. I don't understand why people make such ridiculous posts.
http://www.sqlservercentral.com/Forums/FindPost1690570.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2015 at 8:05 pm
mark.the.dba (6/1/2015)
/quote]
I hope they...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2015 at 8:00 pm
mark.the.dba (6/1/2015)
I updated the script to handle tables in different schema's. I was using this today and found I have issues when the tables had different schema's.
I hope they...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2015 at 8:00 pm
Union all should have worked but it's impossible to tell without seeing your code, at the very least.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2015 at 7:50 pm
Viewing 15 posts - 20,491 through 20,505 (of 59,072 total)