Alteryx Connect

Find answers, ask questions, and share expertise about Alteryx Connect.
Andy Uttley, Alteryx ACE, makes music with Alteryx | Math + Music

Migrating Data Sources

Highlighted
12 - Quasar
12 - Quasar

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.

Highlighted
Alteryx
Alteryx

@Treyson 

 

Does the DB sit on the same server?

Highlighted
12 - Quasar
12 - Quasar

Nope. Same DB, schemas, table names, etc. Just a new server.

Highlighted
Alteryx
Alteryx

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.

Highlighted
12 - Quasar
12 - Quasar

@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?

Highlighted
Alteryx
Alteryx

Do you want to delete the old DB entirely @Treyson ?