Comments
Sort by recent activity
Brian
In our TEST/UAT environments there are additional roles/users that have permissions on the procedures being deployed. As such we don't want these permissions reverting to what is set in the DEV environment.
The script that is generated contains the following,
PRINT N'Altering permissions on [dbo].[SendEmailGeneric]'
GO
REVOKE EXECUTE ON [dbo].[SendEmailGeneric] TO [ApplicationSupport]
GO
I've tried various switches/options, but it seems explicitly including items overrides the ignore options.
I would expect the included items to be compared as per the specified switches and options.
Cheers
Phil / comments
Brian
In our TEST/UAT environments there are additional roles/users that have permissions on the procedures being deployed. As such we don't want these permissions reverting to what is set in the D...
Brian
The table we had was dropped by another user on a dedicated development setup.
Your other option would be to delete the table from source control directly, not using SQL Source Control.
Cheers
Phil / comments
Brian
The table we had was dropped by another user on a dedicated development setup.
Your other option would be to delete the table from source control directly, not using SQL Source Control.
Chee...
I've solved my "Expressions are only allowed as the first element of a pipeline." error by escaping the pipe character with a backtick.
But that still leaves me with a deployment script messing around with permissions. / comments
I've solved my "Expressions are only allowed as the first element of a pipeline." error by escaping the pipe character with a backtick.
But that still leaves me with a deployment script messing aro...
Thanks Brian
The problem can be replicated easily enough.
Just set things up to have a "drop table" listed in Get Latest. Perform some sort of transaction on the table to be dropped, but don't commit the transaction.
Perform a get latest in SSC. SSC will be blocked by the uncommitted transaction. While waiting, click the cancel button.
Cheers
Phil / comments
Thanks Brian
The problem can be replicated easily enough.
Just set things up to have a "drop table" listed in Get Latest. Perform some sort of transaction on the table to be dropped, but don't comm...
But all 13 workspaces listed in the initial screenshot are shown as SQL Source Control workspaces. / comments
But all 13 workspaces listed in the initial screenshot are shown as SQL Source Control workspaces.
Cheers. / comments
Cheers.
Its a pretty sore point at the moment as we're moving from SVN, Bugzilla and non controlled databases, to TFS and SSC. This is just one more item for the devs to be upset about.
We haven't finalised our process for updating developers local databases with fresh data from production. So we're having to restore their local databases at once a day, 2-3 times a day in extreme cases. This means we have to re-link and get latest.
The repeated restores may have upset the workspaces as well, but I'll submit another post about that. / comments
Its a pretty sore point at the moment as we're moving from SVN, Bugzilla and non controlled databases, to TFS and SSC. This is just one more item for the devs to be upset about.
We haven't finalise...
Ok, this is now breaking the product. Definitely needs some work done on it. http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/2598920-tfs-migration-script-unusable-with-custom-port / comments
Ok, this is now breaking the product. Definitely needs some work done on it.http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/2598920-tfs-migration-script-unusable-with-custo...
So is there no way for this to be changed? Is the port number really hardcoded!! / comments
So is there no way for this to be changed? Is the port number really hardcoded!!
Thanks Brian.
When you link a database, the port shown in the dialog is 8080. If there is no "setting" for it, then it must be hardcoded.
This makes it a bit fiddly as we have to change the port to 80 every time we link a database. / comments
Thanks Brian.
When you link a database, the port shown in the dialog is 8080. If there is no "setting" for it, then it must be hardcoded.
This makes it a bit fiddly as we have to change the port to...