Viewing 15 posts - 52,906 through 52,920 (of 59,091 total)
David.Poole (1/15/2008)
LICH (1/15/2008)
Also "Analyser" should be "Analyzer"
Not if you're British it shouldn't.
Well, at least not until we've had a couple of "P's & Q's" 😀 Got beer? :w00t:
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 7:12 pm
Of course... but I guess I'd rather keep it professional (or at least try to salvage some semblance of professionalism on my part after my initial outburst) by not citing...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 7:05 pm
That would be the one... they're pretty smart making it a new datatype... will actually keep 23:59:59.997 code from breaking... unless it's used on the wrong column type.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 5:57 pm
Heh... glad someone occasionally gets a laugh out of those... 😛
More on the serious side... the "Bat with a nail in it" is actually a metaphore for what I do...
I'll...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 5:24 pm
Right idea but no need for the loop...
SELECT CAST(varchara AS CHAR(10))
+ CAST(varcharb AS CHAR(255))
+ CAST(varcharc AS CHAR(50))
...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 4:58 pm
GSquared (1/15/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 4:45 pm
Wouldn't this be easier?
SELECT CASE
WHEN @Nbr > 0 THEN @Nbr
...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 4:41 pm
Govind (1/15/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 4:34 pm
Spot on, Matt.
I'll also add that SQL Server seems to have "tipping points" depending on the size of the table being updated, etc. What I mean by that is...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 4:24 pm
GSquared (1/15/2008)
Jeff Moden (1/14/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 4:18 pm
Heh... the DBA should know enough to keep from having to set auto-grow to 1.5GB 😉 DBA should setup an alert of sorts when the size of the database...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 6:07 am
sp_helpdb is not what I need although I wish that I could read the code for it!!
That part is the easy part... execute the following code with the results in...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 6:03 am
Adam Haines (1/10/2008)
I Found this workaround on this site. With this you can return a postive number of zero from a function.DECLARE @NBR INT
SET @NBR = -123456789
SELECT round(@NBR,-1-floor(log10(abs(@NBR))))
more info:
http://www.sqlservercentral.com/articles/Advanced+Querying/afixfunctionintsql/2487/
Adam......
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 5:52 am
You can also mail me on the below email address.
A bit selfish, there... no one but you would learn, then. 😉
My first reaction is "stupid people" really did it to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 5:40 am
If I could make a suggestion... I think auto-grow is a bit overrated... sure, in 2k5, they made it almost instantaneous... but auto-growth frequently means that the DBA hasn't planned...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 5:27 am
Viewing 15 posts - 52,906 through 52,920 (of 59,091 total)