Viewing 15 posts - 47,146 through 47,160 (of 59,095 total)
I've gotta agree with Michael... the questions have gotten a lot worse. Yeah, I agree that they're probably for the reasons Steve and a couple of others have identified,...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 9:08 pm
Rajesh (11/18/2008)
Hi,You should be using derived column transformation, and use substring or available string functions. This would help.
Raj
Easy enough to say... what formula would you use to return the following...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 8:35 pm
Jack Corbett (11/18/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 8:30 pm
Must look eye... let the code be the teacher...
SELECT [font="Arial Black"]CASE WHEN N IS NULL THEN 5 ELSE 4 END, N[/font]
FROM
(
SELECT N
from Tally
where N < 11
UNION ALL
SELECT NULL
) X
ORDER...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 8:20 pm
ALZDBA (11/18/2008)
(and preferably client side)
Do not bother sqlserver with how you want things actually presented for the human eye.
One...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 8:13 pm
No... I'm not talking about "growth" rates.... I'm talking about setting the database size correctly so it never has to grow. Database growth should never take you by surprise...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 8:08 pm
riga1966 (11/18/2008)
The field data type is INT.I want to display it always as "01","02","03" format.
What is the best way to do it?
Now that you have a couple of answers, please...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 8:04 pm
If you set a column as a DATETIME datatype, and the data put into that column is in the YYYYMMDD format, no conversion is necessary... it'll just work because of...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 7:56 pm
Heh... you guys are missing it... OP wants to know why performance IMPROVED so much after the upgrade so they can go back to the original database and make it...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 7:15 pm
I agree... do an estimate to figure out what the total size should be with a year of data and add 20 to 25% to that number. Set the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 7:11 pm
If they're all like the one you posted with a couple of cursors calling another sproc that probably has another cursor in it, you could be in for some real...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 7:06 pm
Please post what you tried so we can see things like what you tried to GROUP BY. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:57 pm
The data should actually match the table definition... instructions in the atricle everyone has posted would really make this easy.
Msg 515, Level 16, State 2, Line 3
Cannot insert the value...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:51 pm
metro17 (11/18/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:44 pm
James A. Lawrence (11/18/2008)
Sorry! Already mentioned above!
Still, thanks for the thought.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:45 pm
Viewing 15 posts - 47,146 through 47,160 (of 59,095 total)