December 21, 2014 at 1:40 am
hi all,
Need an advice about Source Control over the Sql Server.
we are using Redgate Source Control on the SSMS.
From my understanding, Redgate is good enough for individual objects.
Is there an option of handling database versions with Redgate ? or any pther toll ?
thanks alot sharon
December 21, 2014 at 3:09 am
RedGate SQL Source Control is only an add-on for SSMS. You would need to find your own solution for source control itself such as Microsoft's Team Foundation or an open source solutions like SVN.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
December 23, 2014 at 1:25 am
Check out the SQL Server Database Project offered within SQL Server Data Tools. The Database Project supports managing the properties of a database (e.g. things like the recovery mode and settings like AUTO_CREATE_STATISTICS) together with the database schema and objects within that database. It will not handle some things like Replication or Log Shipping that challenge the line between database and instance configurations, although you can still incorporate the creation of some instance level objects (e.g. Linked Servers) into a database project that models the master database.
A starter video:
Build SQL Server databases using SSDT without leaving Visual Studio
Get Started with Microsoft SQL Server Data Tools
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply