Comments
Sort by recent activity
Have you logged into the server as the service account to check this? The service account is the context under which xp_cmdshell runs by default. alternatively, if you are on a later version of SQL, you can set a proxy for the xp_cmdshell, which might give you the context for licensing. https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-xp-cmdshell-proxy-account-transact-sql
It's possible that the install of Compare on the server is only for one account.
are you using the full path to the SQL Compare executable? can you post the commands? / comments
Have you logged into the server as the service account to check this? The service account is the context under which xp_cmdshell runs by default. alternatively, if you are on a later version of SQL...
Is SQL Compare installed on the server? The context for xp_cmdshell is a folder on the server. If you can run SQL Compare from the command line on the server, with the service account context, this should work. / comments
Is SQL Compare installed on the server? The context for xp_cmdshell is a folder on the server. If you can run SQL Compare from the command line on the server, with the service account context, this...
The difference pane shows the differences since you can view them without actually selecting the object. When you select the "row", the differences are shown. That way you can decide what is happening with the object.
As Jessica mentioned, CTRL+click will go a little quicker. / comments
The difference pane shows the differences since you can view them without actually selecting the object. When you select the "row", the differences are shown. That way you can decide what is happe...
I'm not sure what you mean here. If you are using git, then you connect to your git repository. The TFS part doesn't matter. If you are trying to connect to the TFS git repository on the server, you're incorrectly setting this up. I use TFS online and the git interface with SQL Source Control. You should have a cloned repository on your local system that you setup as a git cloned repo from TFS. When linking to the database, choose Git, not TFS. / comments
I'm not sure what you mean here. If you are using git, then you connect to your git repository. The TFS part doesn't matter. If you are trying to connect to the TFS git repository on the server, yo...
Also, which SQL Source Control version? / comments
Also, which SQL Source Control version?
I wasn't sure what you were doing. Is there a reason you can't set a git repository on your machine that points to a remote in TFS? I haven't tried the git in TFS. I've used TFS or I've used git that points to the repo in TFS. / comments
I wasn't sure what you were doing. Is there a reason you can't set a git repository on your machine that points to a remote in TFS? I haven't tried the git in TFS. I've used TFS or I've used git th...
If you are using the git interface, that should be the URL you include. For example, I have the local path for my git repo.
For TFS, you should have entered the entire TFS url to your repo. This can include the /tfs item in your setup. Check that tab when your database is selected. / comments
If you are using the git interface, that should be the URL you include. For example, I have the local path for my git repo.
For TFS, you should have entered the entire TFS url to your repo. This ca...
We don't have a programmatic interface for SQL Source Control. This was
built for interactive work with developers and there is no API. / comments
We don't have a programmatic interface for SQL Source Control. This was
built for interactive work with developers and there is no API.
First, you could potentially have a way of auto committing, but you'd just be capturing changes without any context. No comments. That's not necessarily a good way of performing development. In the past, I've used auto scripting to do this. I don't know that SQL Compare could be automated to do this, but I wouldn't recommend it. Instead, I'd say that you should really be using something like SQL Compare to look at the db v VCS and alert you that changes need to be committed.
In terms of dealing with a volume of changes. The person that makes the change should commit it when they think it's done. Auto committing is bad because the work might not be done. You want there to be some decision to do this. If you can't keep up, then perhaps you have other development chaos. / comments
First, you could potentially have a way of auto committing, but you'd just be capturing changes without any context. No comments. That's not necessarily a good way of performing development. In the...
Done: https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/31791202-keep-static-data-stored-in-pk-order
I like this idea. It's really more a Data Compare item, but I'll let them know. / comments
Done: https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/31791202-keep-static-data-stored-in-pk-order
I like this idea. It's really more a Data Compare item, but I'll let the...