Viewing 15 posts - 44,941 through 44,955 (of 59,095 total)
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
Looks like a final exam to me... who gets the "A" if we answer them?
It's time to hucker down and do you own work... heh... c'mon, it'll be fun! 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 8:28 pm
I follow the following casing standard...
All SQL Keywords in UPPER CASE.
All database names, table names, procedure names, column names, column aliases, variable names (basically, my stuff) etc, in MixedCase with...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 1:26 pm
GSquared (2/26/2009)
Jeff Moden (11/29/2008)
Heh... milliseconds per calculation mean a lot if you have millions of shipments to make.
Actually, difference is microseconds per calculation, but for the sake of argument, let's...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 1:05 pm
Bruce W Cassidy (2/26/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 1:00 pm
mark_92708 (2/26/2009)
I was reading this thread because I was looking for a solution to this identical problem - trying to concatenate the result strings of one field from a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 12:42 pm
Yep... it's call a "Cross-Tab" or "Pivot"... and the type of table you have is called an "NVP" or "Name/Value Pair" table...
SELECT ID,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2009 at 5:46 am
Viewing 15 posts - 44,941 through 44,955 (of 59,095 total)