Viewing 15 posts - 44,941 through 44,955 (of 59,101 total)
Just curious... why do you need to do this?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 11:14 pm
Heh... must be a one way street... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 11:13 pm
Use this as a source of rowcounts, instead of all that RBAR and counting...
/**********************************************************************************************************************
Purpose:
Returns a single result set similar to sp_Space used for all user tables at once.
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 11:07 pm
If column one contains, say, whole numbers greater than zero and you want the index seek without contraining column 1 to a single value, the following will usually all it...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 11:01 pm
Keeping in mind that a "Page" is 8KB, you could try this and get some pretty good information about the table and all of it's indexes... all at once...
DBCC SHOWCONTIG...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 10:49 pm
Lookup "deadlocks [SQL Server], avoiding" in Books Online.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 10:32 pm
Please see the article at the link in my signature below for better answers quicker. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 10:30 pm
Senthil T (2/26/2009)
We have this table {uniqueid, userid, reportname}. A user can have more than one reportname. The reportname should be unique for each user, but this rule was not...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 10:28 pm
I'd bet credits to Navy beans that a legacy system also has legacy code. Search sys.SQL_Modules.Definition for the column name using LIKE '%columnamehere%' and then use the OBJECT_NAME(OBJECT_ID) on...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 10:26 pm
Grant Fritchey (2/26/2009)
while @RevStateyr...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 10:08 pm
Darwin knew this was possible...
http://www.sqlservercentral.com/Forums/Topic665342-148-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 9:30 pm
Grant Fritchey (2/26/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 9:26 pm
Roy Ernest (2/26/2009)
That worked fine.... Thank You all for helping me out. Appreciate it very much. 🙂Roy
How's the performance, Roy?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 9:22 pm
GilaMonster (2/26/2009)
Jeff Moden (2/26/2009)
All database names, table names, procedure names, column names, column aliases, variable names (basically, my stuff) etc, in MixedCase with no underscores....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 8:45 pm
Bruce W Cassidy (2/26/2009)
So what's the value of upper case?
Works better on old eyes like mine. That and...
This is very much personal preference stuff though.
Heh... correct... well... except in...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 8:41 pm
Viewing 15 posts - 44,941 through 44,955 (of 59,101 total)