Red Gate forums :: View topic - Clean metadata after BAK restore problem!!
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Source Control 3
SQL Source Control 3 forum

Clean metadata after BAK restore problem!!

Search in SQL Source Control 3 forum
Post new topic   Reply to topic
Jump to:  
Author Message
mario17



Joined: 15 Jan 2014
Posts: 9
Location: United States

PostPosted: Thu Apr 03, 2014 12:34 am    Post subject: Clean metadata after BAK restore problem!! Reply with quote

Hi,

I have my db on source control, and I did restore db with REPLACE option from somebody's else BAK. And this broke all my Source Control ddl/data

When I get GET LATEST it says I'm all good, nothing new but I have a lot of balls that indicate that < I have changes to commit>. When I try to commit my changes Action is set = DELETE which I don't want to do. I just want to get latest source controlled DDL,etc.

What would be the solution to clean this data and Really get fresh load from source control?
Is it only because of REPLACE option, maybe I drop/restore db then will work differently??

Is there any FORCE get latest option ????

Tx for help
Mario
Back to top
View user's profile Send private message AIM Address
mario17



Joined: 15 Jan 2014
Posts: 9
Location: United States

PostPosted: Thu Apr 03, 2014 5:06 pm    Post subject: Reply with quote

Bump,..
Can anybody from RG stuff advice please, do I need go with unlink/link, will this clean metadata?


Tx
Mario
Back to top
View user's profile Send private message AIM Address
james.billings



Joined: 16 Jun 2010
Posts: 1144
Location: My desk.

PostPosted: Mon Apr 07, 2014 12:22 pm    Post subject: Reply with quote

Hi,
I'd initially suggest unlinking, restarting SSMS, then relinking. This may clear up the problem.

If not, and you are still seeing drops on the Commit tab, then you need to use the "Undo Changes" option (see here) to update to the repo contents.

Restoring a linked database is generally a bad idea as it alters much of the database without SQL Source Control "knowing", and leads to the sort of problems you're seeing.

It's preferable to sync either with a get-latest if everything is in the repo, or alternatively using SQL Compare/Data Compare which should help stop everything getting out of sync.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group