Viewing 15 posts - 53,551 through 53,565 (of 59,072 total)
Thanks for the feedback, Taffy.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2007 at 11:07 am
Jeff, your "auto magic" one came the closest but I got some extra zeros I haven't quite figured yet -
Original Modified
-------------------
A14 A00014
B2 B0002
OBT 0000OBT
YH3 YH0003
XX 0000XX
So - too many...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2007 at 11:04 am
Karthik, it looks as if your code will fail if the length of any part changes because you've hard-coded each length. Also, I wouldn't use the spt_Values table in...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2007 at 10:48 am
If you use SQL Server 2005, then you can make use of CTE as well
Ummm.... I'm pretty sure I'll avoid recursive CTE's just like I avoid Cursors... they're just too...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2007 at 8:25 am
Yep... know that... see my post above...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2007 at 3:38 pm
Heh... dunno... must be a new "feature" than MS built in... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2007 at 12:39 pm
Heh... yeah... it's a shame that MS can't figure out the best of both worlds. Having just seen 2k5 for the first time and the apparent mess they made...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2007 at 12:10 pm
...the app devs don't need to know anything about the database.
Heh... from where I sit, most of them never did, so no real change. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2007 at 12:01 pm
Actually, it's a common problem... take a look at what you have for a "default catalog" when you login... credits to Navy beans says it's "Master".
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2007 at 11:38 am
Thanks, Matt... I was afraid you were going to say that... yet another highly useful tool shot into the bit-bucket by the idiots that designed the interface for 2k5. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2007 at 7:34 am
reply me my id bhadirinath@yahoo.com
Heh... that's a bit selfish and we're not your personal consultants... if an answer is determined, it should be posted here for all to see.
There're...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2007 at 7:20 am
Any code that needs the word DISTINCT in it, should be highly suspect as the source of a lot of reads... hidden RBAR...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2007 at 7:06 pm
Just trying to make sure...
1. Are the 2/3 detail rows in a different table than the "combined" table?
2. If so, are there rows already in the "combined" table...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2007 at 6:36 pm
SELECT * FROM INFORMATION_SCHEMA.PARAMETERS WHERE Specific_Name = 'Award_Category_Insert'
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2007 at 6:30 pm
Um... why not just replace all INT with BIGINT in the table declaration? After all, you're already violating the 8060 rule for row size... what's a little more going...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2007 at 6:10 pm
Viewing 15 posts - 53,551 through 53,565 (of 59,072 total)