Recently, we migrated a DB from a 2008 SQL Server instance to a 2016 SQL Server Instance.
I need to scrape this new instance and I am curious as to the best path forward. All the objects have the same names, its just that the box that everything sits on is different. Do I need to just delete that whole data source in Connect? I am worried that I am going to lose my metadata around those tables.
I understand how to pull the new instance, just don't want to break the actual Connect instance.
I need some guidance.
In which case the new db will be loaded into the Connect catalogue as a new asset.
The Connect asset ID is created as a hash of concatenaded values - eg hostname/IP, schema name, table name, column name so if your new database is hosted on a different server, the asset will be given a new ID.
As for the metadata you may have entered manually for the old database, this can be exported from Connect as an XLS file, remapped to the new db and re-imported so nothing is lost.
@MichalM I have some follow ups on this.
I did the export of the entire object and this was all that was in the XML file:
<?xml version="1.0" encoding="UTF-8"?><xf3-dump xmlns="http://semanta.cz/schema/xf3/export"
What do I need to delete in order to remove that asset? If I recall I need to delete the stage? Is that correct?
This does seem like very useful and necessary functionality @Treyson - especially since it's quite common to have to move a DB to a new server; and you absolutely don't want to lose the investment of all the metadata that the users have captured.
I realize the question from @Treyson was a long time ago but, for anyone else who needs to know how to completely and safely purge an asset, here are the steps: