Viewing 15 posts - 43,396 through 43,410 (of 59,063 total)
GilaMonster (6/13/2009)
Lynn Pettis (6/13/2009)
Who decides who can vote and who can't, Steve?
Exactly the problem.
SO attempts to solve that by giving points for 'good' and 'correct' answers, and...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2009 at 11:13 am
benoit.rocco (6/13/2009)
I was using SQL Server Management Studio, but connected to a SQL2000 server, it's for that reason the function ROW_NUMBER() didn't exist ^^
Ah... thank you Benoit. That...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2009 at 11:08 am
Paul White (6/13/2009)
You could also put tempdb on a RAM disk.
Heh... I always forget the simple stuff. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2009 at 11:06 am
I guess the next question would be, how "real time" does the running total thingy need to be? We might be able to eliminate the need for the cursor...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2009 at 11:01 am
Ok folks... NOW you can test for performance because NOW you can generate substantial amounts of test data quite easily. The following code creates a million rows of randomized...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2009 at 10:52 am
Aaron (6/13/2009)
That's good feedback.
Heh... I've found that many concurrency issues simply vanish in the presence of high speed code. What I'd be interested in is how fast the trigger...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2009 at 10:07 am
Paul White (6/13/2009)
Jeff Moden (6/12/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2009 at 9:57 am
Aaron (6/13/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2009 at 9:53 am
Aaron,
The post Paul White wrote that starts with "I would usually write it like this:" is more of what I would have done and for the same reasons. That...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2009 at 9:48 am
Aaron (6/13/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2009 at 9:45 am
Heh... wasn't talking about SO. I was talking about here. And by heavy hitters, I'm not necessarily talking about folks with a lot of points. I'm talking...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2009 at 12:36 am
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2009 at 12:28 am
Like this...
[font="Courier New"]--===== Disable all triggers on user tables in database
DECLARE @SQL VARCHAR(MAX)
SELECT @SQL =''
SELECT @SQL = @SQL +
+ 'DISABLE TRIGGER ALL ON ' + Table_Schema + '.' +Table_Name +';'
FROM Information_Schema.Tables
WHERE Table_Type = 'BASE TABLE'
EXEC (@SQL)
--===== Enable all triggers on user tables in database
DECLARE @SQL VARCHAR(MAX)
SELECT @SQL =''
SELECT @SQL = @SQL +
+ 'ENABLE TRIGGER ALL ON ' + Table_Schema + '.' +Table_Name +';'
FROM Information_Schema.Tables
WHERE Table_Type = 'BASE TABLE'
EXEC (@SQL)[/font]
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 11:35 pm
Vivien Xing (6/11/2009)
500+ GB database is considered as a VLDB nowadays.
Who made that rule? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 11:02 pm
Tim Hobbs (6/12/2009)
Many thanks for this - I'm now reading up about CTE's!!!Regards
Tim
It's not the CTE that did the magic. It's the way one ROW_NUMBER was compared to another....
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:59 pm
Viewing 15 posts - 43,396 through 43,410 (of 59,063 total)