Viewing 15 posts - 40,426 through 40,440 (of 59,072 total)
Just make sure that nothing will break if you shift to the new DATE datatype... rumor has it that you can no longer use somedatecolumn+1 to add a day for...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2009 at 4:18 pm
GSquared (12/29/2009)
Nothing "works perfectly right out of the box".
BWAA-HAA!!! Speak for yourself! 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2009 at 8:03 am
Foun-dit!
Fix-dit!
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2009 at 8:01 am
radhika.pathi123 (12/28/2009)
how to perform CLR integration
With extreme caution... most things people write CLR's for are unnecessary and slower than T-SQL. Exceptions are in the categories of certain types of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2009 at 6:24 am
Never mind...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2009 at 6:16 am
My other recommendation is that people like to test their solutions before posting them and, since you're probably under the gun won't have much of an appreciation for it just...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2009 at 5:58 am
tm3 (12/29/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2009 at 5:56 am
Heh... I absolutely agree... all the backups in the world mean squat unless you can restore them. The DBA's a couple of jobs ago went through that. Took...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2009 at 11:51 pm
Did you try what it told you to do?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2009 at 11:45 pm
I've got just the thing for ya...
http://www.sqlservercentral.com/articles/Crosstab/65048/
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2009 at 11:38 pm
Heather May (12/28/2009)
I did start trying to isolate the problem records and so far I've figured out that there's more than one record causing...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2009 at 11:33 pm
Steve Jones - Editor (12/28/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2009 at 11:32 pm
Do you have an example of two numbers that you know caused the overflow error?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2009 at 6:26 pm
It would propably help if you posted the actual errors you're getting.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2009 at 4:34 pm
declare @year char(4)
Declare @visa varchar(25)
declare @visa1985 varchar(25)
set @visa ='56'
Set @year ='1985'
--select @visa = '@visa' + ''+@year+''
--Print @visa
--
--Exec('select '''+@visa+'''')
SELECT @Visa = @Visa+@Year
SELECT @Visa
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2009 at 4:28 pm
Viewing 15 posts - 40,426 through 40,440 (of 59,072 total)