PS Did you ever figure out why the database went to Suspect? Was there anything of interest in the SQL Server Error Log?

yi.hua72 (12/10/2012)

---

Hi all, I had the issue twice back to June, and Oct this year.

Our environment uses log shipping between two long distance geographical locations. One day on June(another on...

Hemant.R (12/10/2012)

---

hi ,

whenever you restore any database ,that activity related info got stored in

restorehistory table of msdb

plz check with using this

select destination_database_name,USER_NAME,restore_date from restorehistory order by restore_date desc

if...

Steve Jones - SSC Editor (12/10/2012)

---

Thanks, I'll pass along to our Devs, but not sure this will be a high priority for us.

Is this just IE or have you tried...

nice follow-through! thanks for posting back

It would be neat (at least to me) if after you pulled together your decision points and settled into a convention you posted those to this thread. I think it...

Fourier

I think the point is, is there an easy way to setup 25 databases for log shipping without hitting the wizard 25 times.

My answer would be sure, anything can be...

use of schemas as containers for grouping and securing like objects

What you are trying to do in effect is modify the system tables underneath the sys.database_principals catalog view which is disallowed when the database is read-only. Instead you'll need to...

It is likely related to collation. For ANSI data types (VARCHAR, CHAR and TEXT) SQL Server will replace any characters in the data not present in the codepage (per the...

It is not uncommon at all. Basically what you want is to initialize the subscriber using a backup from the publisher. When you setup the publication you'll let SQL Server...

Since you're on SQL 2000 you do not have the option of doing page restores. As Gail outlined, you can restore from backup that do not include the corruption (including...

Are you sure the TL backup completed successfully?

It should not matter the name of the file, or even that it has an extension. SQL Server will still read it as...

Not that I know of. Not unless you had a trace running that would show that information or there was a trigger on the msdb.dbo.sysjobs table that recorded who made...