Viewing 15 posts - 56,896 through 56,910 (of 59,067 total)
Yep... then make sure that you rename the column in every stored procedure, view, UDF, foreign key, etc, that uses that column in all databases...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2007 at 6:18 am
What have you tried?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2007 at 6:15 am
Now, THAT's what I'm talkin' 'bout ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2007 at 6:59 pm
You just love patting yourself on the back eh Jeff |
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2007 at 6:56 pm
Might also find it useful to put your "Numbers" or "Tally" table there along with an auxiliary date table... make sure you keep the code to build them safe for when...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2007 at 7:25 am
Micheal Valentine Jones has a faster way but this is an easy way...
Step 1. Create a permanent Tally table... (it has many, many uses)
--===== Create and populate the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2007 at 7:21 am
Heh.... agreed... poor ol' Adam already admitted that the whacko that designed this headed for the hills a long time ago... Who would do this? I can (possibly) understand needing...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2007 at 6:53 am
That's a great suggestion... guaranteed to not duplicate between tables and no trigger overhead.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2007 at 10:31 pm
That's a cool function... change the 36 to 27 and drop the 1-9 from the string and I think it'll work for the 0, A-Z range...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2007 at 1:41 pm
Like I said, keep the identity column and add a calculated column. Takes care of new rows, old rows, etc...
Or, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2007 at 1:31 pm
Heh... speak of the devil and who shows up? I just recommended your sequential numbers function... was writin' while you were postin' ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2007 at 1:12 pm
Hey there Harley,
Thanks for the compliment... You and Paul made my day!
Sadly, in SQL Server 2000, there's no way to return the equivelent of row numbers using a SELECT without using...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2007 at 1:10 pm
I do not think there is a way where you can use Update to update based on counter |
I...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2007 at 1:03 pm
Hey Paul,
I almost forgot a trick with using this if you can't make a "sister table".... you can force the order by using an index hint... like this... (this is...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2007 at 1:00 pm
Heh... thanks, Paul... I always wonder if anyone reads these things... ![]()
Just so you know I'm not using some whacko, back door, undocumented construct,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2007 at 12:30 pm
Viewing 15 posts - 56,896 through 56,910 (of 59,067 total)