Viewing 15 posts - 53,371 through 53,385 (of 59,072 total)
What are you using to call the proc? In other words, let's see the EXEC statement 'cause the code in the proc is mostly correct. Only thing wrong...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 7:23 pm
Heh... to many conversions and concatenation for me... the following does the trick as well...
SELECT STUFF(CONVERT(VARCHAR(30),GETDATE(),107),1,3,DATENAME(mm,GETDATE()))
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 4:54 pm
The best answer would be "to protect the results". I've seen it happen before... DBA's can decide there's a problem with a table or they need to instantiate some...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 4:48 pm
Thanks for the feedback! Good to know that it wasn't BCP.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 4:36 pm
Heh... I'm still trying to figure out why anyone would try to cache a 54 million row table...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 4:33 pm
Step 1, I would think, is to hunt down the vendor that provides you with the information... and then yank their tonsils out through their nose. Wow! They...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 4:28 pm
You're welcome... thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 4:19 pm
You're welcome and thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 4:17 pm
I haven't check all the code, but I see that you have a RETURN that I commented out in red...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 4:16 pm
Heh... use the heat of compression to make hot water, the thermal losses of expansion to provide refrigeration, and the left over pressure to drive a low pressure turbine.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 4:10 pm
Ken,
Yeah, you're right... go breaks the stride of variables... AQT won't handle it. Still not sure why you need the "GO"'s. Yeah, they force an early display but...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 4:08 pm
Ummm... my mistake, I think... you're probably taking about the "WINDOWS" server System Admin, huh?
That might be a different story but, still, I'd be inclined to let the DBA in....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 2:50 pm
If you dunno, you may be in trouble...
Who's going to set the files sizes? Who's going to do the load balancing for TempDB and other databases? Who's going...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 12:47 pm
Heh... If you're going to copy code 100%, the least you could do is put my name on it 😉
First, why are you using this as a proc... why...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 12:33 pm
Lowell, as always, brings up some excellent points and I, too, hate these types of sequence tables. They're a real pain and if the code isn't written perfectly, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 12:09 pm
Viewing 15 posts - 53,371 through 53,385 (of 59,072 total)