Quantcast
Channel: THWACK: Message List
Viewing all articles
Browse latest Browse all 20396

Re: Moving PM DB from one Remote SQL server to another

$
0
0
Obviously if we don't need to go through ALL of those other steps (which don't seem to apply to this situation at all) there's no point in touching anything.

Please do not skip steps. We wrote these steps for very explicit reasons. Every time a customer has skipped a step it results in a support call in which we point out the step they skipped.

ALL steps are REQUIRED anytime the database is moved from one SQL Server instance to another SQL Server instance, regardless of where those instances are physically located.


 

Do you *KNOW* if this is all that needs to happen on the PM side?

 

Yes, I know this for a fact. You might find some reassurance from reading my bio. I've been working with Patch Manager for over six years.


 

I feel like throwing me at a doc and saying "Make necessary changes" isn't really helpful.

 

Follow the steps *exactly* and you'll be fine -- which is why we wrote the KB article.

Would it have made you feel more secure if I'd copied and pasted the contents of the article into this reply?




Viewing all articles
Browse latest Browse all 20396

Trending Articles