Viewing 15 posts - 27,496 through 27,510 (of 59,101 total)
jwillbanks (2/15/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2013 at 9:39 am
byecoliz (2/15/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2013 at 9:37 am
Abu Dina (2/14/2013)
mr.neil.bryan (2/14/2013)
Any tips on making this career change?Has anyone done this?
Many thanks,
Yup, I made this decision in July last year however, as hard as I tired I couldn't...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2013 at 11:26 pm
ScottPletcher (2/14/2013)
In order, here's a quick list of the most important things to do first:
1) Make sure the DBA role will fit you. As a developer,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2013 at 11:07 pm
WARNING! Storing PART NUMBERS as FLOAT will eventually and absolutely screw you to the deck without warning.
DECLARE @PartNumber FLOAT;
SELECT @PartNumber = 1234567890123456;
SELECT @PartNumber AS ScrewedALittle;
SELECT @PartNumber...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2013 at 10:49 pm
Competition for jobs gets more intense all the time and the employees that look for problems and provide solutions without being asked will be the most valuable. They will stand...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2013 at 10:33 pm
Shifting gears, once you get the DB's back up and running, seriously consider upgraded to the latest service pack of SQL Server 2005.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2013 at 9:38 pm
RBarryYoung (2/8/2013)
Ewww, Tom! I hesitate to ask what "squat thrusts" must mean over there. :sick:
BWAAAAAAAAA-HAAAAAAA-HAAAAAAA!!!!! (clutching my sides and just blew a half dozen Cheerios out my nose!) ...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2013 at 9:31 pm
ScottPletcher (2/13/2013)
I wouldn't use a separate schema, first of all because of the security considerations: you'll break the ownership chain, thus forcing a lot more security checks on objects.
I believe...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2013 at 9:19 pm
Grant Fritchey (2/13/2013)
I hope no one is shocked when I basically agree with you. I like the concept of grouping through words, but clear language, not embedded codes.
I'll strongly second...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2013 at 9:10 pm
Grant Fritchey (2/13/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2013 at 8:39 am
I strongly recommend that you avoid killing SPIDs if at all possible. Killing a SPID can actually leave it in a permanent 0% rollback that consumes a whole lot...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2013 at 6:57 am
sku370870 (2/12/2013)
Following Jeff Moden's answer (and link) - I modified my code to have a sort key that ended up returning...
\6
\6\7
\6\7\12
\6\7\8
\6\7\8\13
... which seems to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2013 at 11:06 pm
Paul White (2/12/2013)
It's quite easy to go mad trying to do this sort of thing in T-SQL today (future things like ordered aggregates might help, I don't know).
A cursor...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2013 at 8:46 pm
Sean Lange (2/11/2013)
DON'T use things you don't need, like the BEGIN and END for the proc itself - completely unneeded and doing nothing but cluttering up the screen.
Actually begin...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2013 at 4:11 pm
Viewing 15 posts - 27,496 through 27,510 (of 59,101 total)