AndrewSQLDBA (6/9/2010)

---

I always create one package per task per database. So if anything were to change, I have to only delete the one package and the job that fires off...

Yes, the list of databases is generated when the plan is saved.

You have to make a change to the backup task and re-select the list of databases to be backed...

JC-3113 (6/9/2010)

---

Dis-regard those errors above

this is the maint plan error:

One or more selected databases no longer exist on server.

They are no longer in the plan, so why would it say...

The default trace might contain this, since it does capture object creation and drops. You'll have to check it out to see if it still exists.

By default, the alias 'gm' is defined for the cmdlet Get-Member. You are trying to override the alias and you can't do that.

No, switching from FULL to BULK_LOGGED and back to FULL does not break the log chain. If you switch to SIMPLE, that will break the log chain.

Just be aware...

Once the transaction log has grown out large enough to support the rebuild, then it shouldn't grow anymore. If you are shrinking it after that process, all you are...

Are you going to be adding any more data to this database? If not, then you could shrink it and then rebuild indexes. If you are going to...

Well, unfortunately you are going to have to drop the constraint. The constraint is enforced using the index and the index cannot be dropped until the constraint has been...

If this is truly a one to one relationship, why are you creating a separate table? You should just be adding the disposition column to the sales order table.

With...

If you can provide some sample data and table definitions as outlined in the article I link to, we can provide a tested solution that will work.

At this point, the...

Why are you shrinking in the first place? Can you be absolutely sure that space will never be used again? If not, then there really is no reason...

Are you backing up the transaction logs?

Are you shrinking the transaction logs?

Review the article in my signature on managing transaction logs. This should give you an idea of why...

First, importing maintenance plans directly from one system to the other will not work. The plan will be created, but the local connection will be set to the other...

This is a really stupid issue in the way they check the privileges. The issue is caused by how the username is setup in AD and how the login...