you've got it right, homebrew01, not simple, but bulk_logged is the way to go..

karl

Hi,

anytime you handle date/time values you should use SET DATEFORMAT, in your case SET DATEFORMAT dmy. I've had a lot of trouble with datetime, because the format does change sometimes...

Hi,

yes, you should do another full backup after the shrink file, because if you have to restore from the earlier backup you will have to do the dbcc shrinkfile again...

And...

Hi,

are there any events in the system event log about not finding the nt domain server?

karl

Hi,

if you set a limit to the rowcount for the jobhistory you don't need to do sp_delete_jobhistory...

Do these jobs execute anything on linked servers? If so, is the duration...

Hi,

what kind of logshipping did you implment, "out of the box" or "custom made"?

If the copying process overlaps with the restore the restore may fail and the database...

Hi,

have a look at msdb, perhaps it's full or the job-history contains too much entries.

do you use sp_delete_backuphistory regularely?

karl

Hi,

did you try to create a view containing the OPENQUERY to the linked Server, and use the function to select from this view?

karl

You could use BigBrother ("Big Brother is Free for Non-Commercial Use")

http://www.bb4.org/

karl

HI,

also you should do a sp_createstats and sp_updatestats, perhaps every night, or weekly if the amount of Data does'nt grow so much.

karl

yes, i'd be very interested.

you can never know enough, which goes especially for undocumented options 🙂

regards karl

Hi,

is the backup file on a network drive or on a local disk?

Perhaps the copying is not finished yet?

regards karl

Hi,

you could exec the following proc for each database:

/* -------------------------------------------------------------------------- */

createproc master.dbo.sp_ScriptDatabase @dbname sysname

as

declare @command varchar(1000)

declare @texttime varchar(10)

set@texttime = convert(varchar, getdate(), 102)

set@command = '"C:\Programme\Microsoft SQL Server\MSSQL\Upgrade\scptxfr.exe" /s servername /I /d...

well, for me, that kind of plan stinks! SQL server is not some puny access db, it needs some thinking to do things right...

as long as the databases are not...

ok, found something on the net:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q224071#XSLTH3188121122120121120120

trace flag T3608

try

d:\..\MSSQL$LATIN_CP850_CIAS\Binn>sqlservr -slatin_cp850_cias -f -T3608

for desaster recovery i recommend using exactly the same layout like on the production server, because...