We have several projects that have one database in them. I would like to move the databases and scripts (with history) all to a new project for the one section of our company.

What is the best way to go about this so that we are sure to save our history?

Thanks!

I'd have to confirm this but I'm pretty sure that if you create a new project and import the relevant servers/databases, as long as those databases are already part of another project on the same source control database, then their history is automatically imported too.

I'll check this out later on and confirm whether this is the case or not.

---

SQLDBcontrol Support

support@sqldbcontrol.com

I can confirm that this is indeed the case. If you create a new project and import databases that already exist in another project all of the history is retained across different projects.

I have however noticed that Labelling isn't maintained across projects. This is a slight oversight and can easily be remedied by modifying an existing stored procedure.

I should point out that private and public T-SQL scripts and any packages are unfortunately not currently transferable . That said, it wouldn't be difficult to perform this move by providing you with a suitable script.

As this functionality won't be difficult to include we will add this in. But if you need to perform the move prior to the new build please let me know and I will provide you with a script.

---

SQLDBcontrol Support

support@sqldbcontrol.com

Thanks for clearing that up. I don't really need to move labels since we don't use them yet. I don't think that I need a script. I will go ahead and add the databases to the new project and then move the scripts etc by hand. We don't have that many.

Thanks!