Viewing 15 posts - 43,186 through 43,200 (of 59,098 total)
Thank you very much for taking the time to explain that to me. Most people pose what the want to solve for instead of posting what the problem is...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2009 at 6:16 am
lmu92 (6/30/2009)
Sometimes the occurrence of the word "PIVOT" isn't that bad, obviously... - especially when it comes together with an "UN".
Seems a little easier to deal with than...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2009 at 6:00 am
mandirkumar (6/30/2009)
Thanks to everyone 🙂
Oh no, no, no... you can't go away, yet. I want to know what the business requirements are that caused you to ask this question,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2009 at 5:57 am
Intentional obfuscation of purpose through the joyful infusion of unnecessary code just for the fun of it all. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 9:52 pm
saxena.rohit (6/29/2009)
I need to add a pin for each user in SQL login table..
Why not just accept "PINS" as the password?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 8:38 pm
[font="Arial Black"]I still want to know the business requirement behind all this, please.[/font]
Ok... here's a very simple answer especially if you have more than 3 columns that you need to...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 8:12 pm
mandirkumar (6/29/2009)
Hi ALLI have a table and I need both horizontal and vertical sorting for the table
Example:-
What is the business requirement behind doing this? It...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 7:33 pm
SanjayAttray (6/29/2009)
in SQL server 2005 result is 1.234568E+09while in SQL 2000 result is 1.2345679E+9
Does it make any difference ?
Heh... only if you're answering a QOD and only if both answers...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 6:24 pm
peter (6/29/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 6:09 pm
I'm pretty happy that someone brought up the fact that when you're going to be doing something like genning numbers using systems tables or views, that the end user "must...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 4:23 pm
Heh... solve it all... store everything in one big EAV with SCD 2 applied to eliminate the need for separate auditing or archiving... 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 10:52 am
Lynn Pettis (6/29/2009)
And that will work until the SQL Server 2000 system table "views", like sys.syscolumns, go away in a future version od SQL Server. They have been depreciated.
I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 8:41 am
Peso (6/29/2009)
Or use COLLATIONCONSTRAINT ss CHECK (adp IN ('T', 'F') COLLATE SQL_Latin1_General_Cp437_BIN)
That's a good check but I'd have to introduce someone to a serious volley of high speed pork chops...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 6:41 am
As a side bar, I'm still waiting for the OP to post code where the things he wants to use aren't actually commented out so I can be sure of...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 6:37 am
Scott Coleman (6/29/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 6:33 am
Viewing 15 posts - 43,186 through 43,200 (of 59,098 total)