Viewing 15 posts - 3,046 through 3,060 (of 8,416 total)
Dave Ballantyne (7/2/2010)
The Dixie Flatline (7/1/2010)
July 2, 2010 at 7:04 am
mpdillon (7/2/2010)
I can go back to my previous practice of choosing the smallest data type. I can use 1.0 * in all my divisions without too much trouble.
Many people do...
July 2, 2010 at 6:38 am
Eugene Elutin (7/2/2010)
Paul may have willing to explain why SQL doesn't keep result of SELECT Cast(2 as decimal(18,6))/3 as decimal(18,6) but adds two more digits after decimal points...
The rules are...
July 2, 2010 at 6:23 am
Eugene Elutin (7/2/2010)
Interesting to see how SQL...
July 2, 2010 at 6:20 am
GilaMonster (7/2/2010)
virender.singh (7/2/2010)
@paul-2 : I will cheer for newzeland during next india-newzeland battle;-)Cheer for South Africa next time we play India! We're more likely to win. 😉 :hehe:
Humph! 😎
July 2, 2010 at 3:20 am
Eugene, I see we posted similar advice at the same time. Just one thing:
Eugene Elutin (7/2/2010)
July 2, 2010 at 2:23 am
In general, you should choose a data type based on the values to be stored.
If you need to perform a calculation on those quantities (usually a division) that requires a...
July 2, 2010 at 2:17 am
Eugene, you included some tags in that link by mistake. This version works:
http://msdn.microsoft.com/en-us/library/dd425070(SQL.100).aspx
I'm not sure it will help virender too much, but it's all good useful information.
As far as...
July 2, 2010 at 1:28 am
The SELECT * INTO statement (like all data modification statements) runs inside an implicit transaction. The locks taken during the creation of the table and adding records to it...
July 2, 2010 at 1:22 am
It's often impossible to diagnose the cause after you have restarted the server. If it happens again, try to connect via the DAC and gather as much information you...
July 2, 2010 at 12:49 am
lmu92 (6/30/2010)
The best one I've seen so far is by Jeff Moden and posted here.
Interesting. Even though I am credited on that post with a couple of optimisations,...
July 2, 2010 at 12:33 am
leonardo_gt (6/30/2010)
...which is more convenient to use: a function or procedure? in terms of performance are the same?
In very general terms, it is often possible to write a stored procedure...
July 1, 2010 at 4:17 am
Gianluca Sartori (6/30/2010)
Functions don't have predetermined cached query plans, stored procedures do.
That's a common misconception, which I think goes back to the days when SQL Server had a 'procedure cache'...
July 1, 2010 at 4:08 am
Tara-1044200 (6/29/2010)
PaulThe definition very simple which consists of 53 columns with varchar(16) and 4 datetime fields and the row count is 345039256
The reason I asked for the CREATE TABLE statement...
July 1, 2010 at 3:36 am
Viewing 15 posts - 3,046 through 3,060 (of 8,416 total)