Viewing 15 posts - 48,076 through 48,090 (of 59,095 total)
Heh... thanks for posting your solution. Sometimes the problem just boils down to "must look eye." 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 7:47 pm
Jack Corbett (9/25/2008)
Chris Harshman (9/25/2008)
I'm suprised that Jeff Moden hasn't jumped all over this. 😉
Based on some of Jeff's other posts, he is pretty busy with work right now,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 7:42 pm
marius.draganescu (9/25/2008)
That is what I was suspecting, too... I guess I will have to do this in VB, process one line at a time.Thanks you very much for your opinion!
Marius
Heh......
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 7:18 pm
skottikalapoodi (9/26/2008)
MY DATA TYPE IS DECIMAL ONLY.ACTUALLY WHAT I WANT IS, I DON'T WANT IT TO BE ROUNDED
DECIMAL WHAT??? What is the actual datatype of the column...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 7:14 pm
Heh... "Loop" and "Lose" are both 4 letter words beginning with "L". 😛 Please see the following article for how to perform concatenation and some of the pitfalls to...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 7:10 pm
By the way... the methods shown in the articles are a bit faster than the XML methods and can also be used in SQL Server 2000. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 7:05 pm
It's super simple to pass a single dimensional array to SQL Server as a comma delimited string and then to split it into a temp table or table variable using...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 7:04 pm
Those sprocs are the ones that SQL Server runs behind the scenes for nearly every stored proc. The real problem is not those, but the query the query that...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 6:58 pm
Do you have any SQL Server Agent jobs that are failing? I've found that, depending on what they do, they can leave open connections that hold on to resources....
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 6:51 pm
BWAAHAA! No need to do the Polka with Convert, folks! 😛 Read the original post!
I have one [font="Arial Black"]datetime [/font]column named Hours in SQL Server Table1...
Notes4we, I recommend...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 6:33 pm
Just remember that TRUNCATE doesn't work in the presence of foreign keys. I believe they can be disabled rather than dropped, though.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 5:54 pm
prasanna_pathangi (9/25/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 5:47 pm
It doesn't matter if you have a max of 8000 characters for a variable, or not. You cannot print more than 8000 characters in SQL Server in a single...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 5:29 pm
Actually, there IS a limit on the size of stored procedures and batches... it's (65,536 * Network packet size) for batches and the lesser of batch size or 250 MB...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 5:11 pm
Yes... there's a huge problem... you have a double nested correlated subquery in the SET clause... and THAT will be executed, in it's entirety, once for every row qualified by...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 5:01 pm
Viewing 15 posts - 48,076 through 48,090 (of 59,095 total)