initial setup automation
We've got HUNDREDS of databases. Dozens in active development.
Several obvious details are missing from the initial setup of a linked database. These are specific to VSS, but I'm sure apply to other SSC versions:
1) Remember the last used (VSS) Database path.
2) Remember the last Source Control Folder, BUT... SUGGEST the name of the new DB as the terminal project name.
3) Add a Check box to "Auto Commit" ALL objects.
The amount of retyping (or even copy/paste/edit) the same information over and over is quite annoying.
It would be good to have the ability to script DB linking and checkin.
You would specify the the TFS/SVN/Other path and the databases and be able to iterate over the whole instance and link all of the DB's. The ability to automatically commit these changes would be good also.
share database link configuration with other users or across machines rather than having to relink databases for each installation of SQL Source
We are planning to work on setup automation in a future version of SQL Source Control.
In the meantime, I have added a comment that specifies a workaround that may help get additional users linked to numerous databases more quickly
It seems to me there should be a configuration option available to the users to allow RedGate to store the configuration of databases to a specific "RedGateSourceSafeConfigurationDb" database. That way, we could manipulate that table easily to tell RedGate what the linkages are, and RedGate could write to the same table to store the information for new databases/developers.
@Chris, why won't the working folders come through, when I see them in the XML file?
The work around helped a lot. Teaches me to save off that XML file the next time I have to wipe my Windows installation.
But I think you are over thinking the answer a little bit. How about if at the Databases level, you had a link all with a browse to the root and then for each database it found, if there was a corresponding directory, just do the link? Then piecemeal in the missing ones.
AdminChris Smith (Admin, Red Gate) commented
Following changes made in SQL Source Control version 22.214.171.124, you can now pass around a config file to help get additional users linked to nemerous databases more quickly. This release is currently available via the Check For Updates option from the application's Help menu.
Disclaimer: This is clearly not a proper solution for this suggestion (we are planning to work on that in a future version of the product), but it might help you get other users set-up with fewer manual steps!
So, here it goes:
1. Setup SQL Source Control on one machine with all the linked databases that are required. Then copy the following file from that machine:
C:\Users\[username]\AppData\Local\Red Gate\SQL Source Control 3\LinkedDatabases.xml
2. This file should be placed into the same location (C:\Users\[username]\AppData\Local\Red Gate\SQL Source Control 3) on other machines where you would like these databases to be linked ([username] in this path should be the user who will be using the copied configuration on this machine).
3. So, when the new user connects with SSMS to the server where the linked databases reside, they should see green database nodes in the object explorer indicating databases linked to source control. However, when one of these nodes is selected, because SQL Source Control has not got a local working copy of the database schema, it will prompt the user with the following question and they should reply YES to this:
"There are no local files fore the database [database name]. Would you like to link it to source control?"
4. SQL Source Control will then create the local files it needs to work with the database and the user should be up & running.
It is worth noting that at the moment this does not work with Migration Folder locations (they cannot be copied in the above way).
Aaron Jensen commented
We have 19 databases, and dozens of developers. I would like to write a PowerShell script that sets these extended properties so developers can open up SSMS and start working.
Todd Nelson commented
Yeah... us too. Many databases. Need to get them all in there. Would like to add the whole server and have the hierarchy Server.Database all get added to TFS.
AdminDavid Atkinson (Admin, Red Gate) commented
We hope to achieve this by storing a database-level extended property with the repository location. This means that linking a database won't require typing in the URL and folder details. I'm not sure this will make the next version, but hopefully not too much longer after.
AdminDavid Atkinson (Admin, Red Gate) commented
We acknowledge that the one-off set-up is tedious when multiplied by the number of developers. In the next version we'll be starting to store metadata such as version and repository information in database level extended properties. This will allow us in future to auto-link databases once the extended property is detected. This won't make the very next release, but should follow shortly afterwards.
We also have a large number of databases. We also develop in a team environment with multiple database developers. The time it takes to set up source control on our two servers for one person is bad enough.
Since we can't simply export a "config" file of some sort to then send to the other database developers that means each of my team have to waste that same amount of time setting up their workstation. I can't afford that amount of down time.
Although I am really interested in this source control plug-in, I likely won't purchase until there is some way to automate the setup for subsequent developers.