Viewing 15 posts - 43,441 through 43,455 (of 59,102 total)
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
Cross post... please, no answers here. Go to the following instead...
http://www.sqlservercentral.com/Forums/Topic734177-338-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:53 pm
Jeffrey Williams (6/12/2009)
BTW - if you do not specify file locations in your create database statement, the default location defined for that instance will be used.
Voice of reason, right there.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:49 pm
Leave the first "-o" alone. Change all of the other "-o" to ">>".
Old DOS warrior trick. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:47 pm
This is a classic error that causes huge performance problems. The target of the update must also be included in the FROM clause if a join is present. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:45 pm
For the record, both Temp Tables and Table Variables start out in Memory and spool to TempDB if they get too big.
I suspect neither a Local Temp Table nor a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:38 pm
What helped it was that you got the COALESCE out of the WHERE clause.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:32 pm
Viewing 15 posts - 43,441 through 43,455 (of 59,102 total)