Viewing 15 posts - 35,611 through 35,625 (of 59,102 total)
SKYBVI (12/21/2010)
Does education (bachelor's or master's) also influence the pay in case of SQL server DBA ??Regards,
Sushant
I've not seen it to be so. I will say that some companies...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2010 at 10:04 am
DKlein (12/21/2010)
Jeff, what would you suggest for a small company?
That, of course, depends on the budget. Raid 5 certainly helps protect the data but is a slower compared to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2010 at 9:57 am
Sjeef (12/21/2010)
Now would be a good time to get away from Raid 5 if you can.
Hi Jeff,
Is Raid 1 more preferred for database files over Raid 5.?
I know raid 5...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2010 at 9:54 am
Mad Myche (12/21/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2010 at 9:44 am
Phil Parkin (12/23/2009)
Jeff Moden (12/22/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2010 at 9:35 am
dlinetsky (12/21/2010)
REPLICATE('0',10-LEN(SomeNumber)) + CAST(somenumber AS VARCHAR(10)), which has always worked well for me, but appears to be...--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2010 at 9:31 am
vinothraj (12/21/2010)
I dont know why its gets differs.. attached screenshot.. by the by, my machine is i5
Which code did you use for that test? If the answer is that...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2010 at 9:25 am
SQLkiwi (12/20/2010)
Wildcat (12/20/2010)
How could a NOLOCK hint to the target table on the DELETE or UPDATE statement? Make no sense to me.
Precisely. It's just an oversight in the parser:
--...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2010 at 12:29 am
vinothraj (12/20/2010)
Jeff Moden (12/17/2010)
vinothraj (12/16/2010)
I've checked elapsing time for each of those and got approximate time is less for current_timestamp than getdate().Is current_timestamp better? i think so....
Please post the test...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2010 at 11:20 pm
Ok... since I don't subscribe to SQL Server Magazine, I can't get to the actual code listings but I cobbled together a non-RBAR function that uses the Tally Table instead...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2010 at 10:27 pm
bitbucket-25253 (12/20/2010)
SELECT so.Name AS 'Table',sc.Name AS 'Column'
FROM sys.sysobjects...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2010 at 9:19 pm
fabricioaraujorj (12/20/2010)
Jeff Moden (12/17/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2010 at 9:14 pm
Mad Myche (12/20/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2010 at 9:12 pm
James Stover (12/20/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2010 at 9:01 pm
Agh! Gotta remember to read down. Remi already suggested what I just did.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2010 at 8:54 pm
Viewing 15 posts - 35,611 through 35,625 (of 59,102 total)