Viewing 15 posts - 56,056 through 56,070 (of 59,098 total)
Just to add to the above... In SQL Server 7.0...
If neither Item 4 or 8 are set, that's the equivelent to FULL recovery.
IF Item 4 is set and Item 8...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 23, 2007 at 6:22 pm
Ah... got it... sorry, Remi... thought you lost your mind for a minute
I should have known better.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 23, 2007 at 6:15 pm
Bill,
Slight "lull" in the action here so I thought I'd check... was your question answered or did you have something else in mind? And, I didn't get the chance to...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 23, 2007 at 6:06 pm
Heh... thanks for the feedback, David. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 9:43 pm
Substitute your date column or date variable for GETDATE() in the following...
SELECT DATEADD(yy,DATEDIFF(yy,0,GETDATE()),0)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 9:38 pm
You too... Thanks, Marcus...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 9:30 pm
Heh, too much "potty" time, James?
(just kidding) Me? The shower can wait, I'm headed for a beer!
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 9:28 pm
Sorry David, didn't list all of the switches you needed 'cause I thought you might already know them... You'll need the following switches, as well...
-s"" -w256 -n
Replace the "256" with...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 9:04 pm
Bill,
Thanks for posting code that actually creates some data... usually saves a lot of time for respondents and we appreciated it a LOT!
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 8:38 pm
I always wanted to know how fast that method ran ![]()
--================================================================================================= -- Prepare a test table --=================================================================================================
--===== If the test table exists, drop
IF OBJECT_ID('TempDB.dbo.#TestData') IS...--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 8:36 pm
O-ki-do-ki ![]()
DBCC UPDATEUSAGE(0)
--===== "Space Used on Sterioids" -- Created by Jeff Moden -- If "UnusedKB" is negative, it's likely you need to run DBCC...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 7:41 pm
Your handle says "SQLDBA" so I'm thinking that you know where Books Online is...
lookup DATEADD, Insert, Delete, and WHERE NOT IN.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 7:34 pm
Doesn't help the processing speed at all but does take less size for the dynamic SQL, the WHERE clause should be constructed more like the following...
FROM RecurrentOutcomeParticipants rop
WHERE...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 7:29 pm
use occ_archives
insert into asqcrr.occ_archives.dbo.hvcfids
select * from asqcrr.occ_archives.dbo.hvcfids as dest
Where not exists
(select workitemid
from asqcrr.occ_archives.dbo.hvcfids as source
where source.workitemid = dest.workitemid)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 1:33 pm
Way too much info ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 1:29 pm
Viewing 15 posts - 56,056 through 56,070 (of 59,098 total)