Comments
Sort by recent activity
Mike U's comment about the shared model not being compatible with Git does not make any sense to me. Even in dedicated mode, each developer has their own local repository which can change independently of any central remote. I see no difference as far as repositories go. Regarding actual history of changes, the Source Control is independent of the database. / comments
Mike U's comment about the shared model not being compatible with Git does not make any sense to me. Even in dedicated mode, each developer has their own local repository which can change independ...
We decided to use ApexSQL Source Control. It is fully implemented using the shared development environment. It is working nicely, but, as with Git for program code, it takes some training and practice. / comments
We decided to use ApexSQL Source Control. It is fully implemented using the shared development environment. It is working nicely, but, as with Git for program code, it takes some training and prac...
My answer to your previous question does not appear to have posted. We don't see how we can use local databases without spending more time setting them up and maintaining them than we spend making the on the actual database maintenance. To create multiple test databases we would also have to create multiple program environments, link them to the databases, keep the test data updated. The overhead in time, diskspace, servers and effort would be enormous, just to make a small change in a stored procedure. / comments
My answer to your previous question does not appear to have posted. We don't see how we can use local databases without spending more time setting them up and maintaining them than we spend making...
So with SQL Source Control, how does it determine when there has been a change? Does it look at the date and time that the tool created the script file? If so, that seems to be a little short-sited since the change is not happening in the file but rather in the database. If the change is determined by looking in the database, how could two identical files be committed? / comments
So with SQL Source Control, how does it determine when there has been a change? Does it look at the date and time that the tool created the script file? If so, that seems to be a little short-sit...
to create multiple test databases we would also have to create multiple program environments, link them to the databases, keep the test data updated. The overhead in time, diskspace, servers and effort would be enormous, just to make a small change in a stored procedure. / comments
to create multiple test databases we would also have to create multiple program environments, link them to the databases, keep the test data updated. The overhead in time, diskspace, servers and ...
The exact same situation could arise with my C#. Since it is less likely I guess it was decided that the tools would ignore it. I don't see how it overrides standard Git behavior since standard Git behavior does not handle that situation. It would be an extension to make up for a deficiency in Git. / comments
The exact same situation could arise with my C#. Since it is less likely I guess it was decided that the tools would ignore it. I don't see how it overrides standard Git behavior since standard G...
I find it odd that it does not happen with program source code. The commits are separate and have to be merged. "Commits" are something that happens in the repositories, not in the database. / comments
I find it odd that it does not happen with program source code. The commits are separate and have to be merged. "Commits" are something that happens in the repositories, not in the database.
Manages what files? That does not make any sense to me. Which two identical files? We are talking about database objects, not files. / comments
Manages what files? That does not make any sense to me. Which two identical files? We are talking about database objects, not files.
All of the "working folders" that I know about belong to the user. Which working files are shared? / comments
All of the "working folders" that I know about belong to the user. Which working files are shared?
I have not seen any reasonable explanations of problems using shared databases. When I use Git with my C# code, I can see the difference between my local repository and the central one. Is this missing in SQL Source Control? Did they decide that this comparison was not necessary? The repositories are stored independently of the actual database. I do not see the disconnect here. The example given in "Using Shared Mode with Git" indicates that SQL Source Control is lacking the ability to compare a stored procedure in the database I have open to the stored procedure in the central repository. That does not make sense to me. I am using Git with my C# code and I can see the comparison there. Why would Red Gate decide not to implement something as essential as that? / comments
I have not seen any reasonable explanations of problems using shared databases. When I use Git with my C# code, I can see the difference between my local repository and the central one. Is this m...