Comments
Sort by recent activity
Hi Sergio - I have contacted one of your colleagues directly who has been looking at this. / comments
Hi Sergio - I have contacted one of your colleagues directly who has been looking at this.
Hi Eddie,
I don't think so in that I have a change to a database object in there too which should be getting identified.
Chris / comments
Hi Eddie,
I don't think so in that I have a change to a database object in there too which should be getting identified.
Chris
Hi Laurent,
You could use a filter to ignore all users but it sounds like you have some users in source control - if you do want those users included then you would need to use a filter to only include those ones. I normally exclude all users from source control as it makes things much easier.
Chris / comments
Hi Laurent,
You could use a filter to ignore all users but it sounds like you have some users in source control - if you do want those users included then you would need to use a filter to only inc...
Hi Andrea,
That's not what I'm seeing: I've currently got a few databases on different SQL instances connected to SQL Source Control and they all have the option you indicated set (looks like it is set as standard) but only one of the SQL instances has those objects in the tempdb.
Anyway, we can work around the error by giving execute rights on the SP in tempdb if necessary - perhaps one to publish in your FAQs?
Chris / comments
Hi Andrea,
That's not what I'm seeing: I've currently got a few databases on different SQL instances connected to SQL Source Control and they all have the option you indicated set (looks like it is...
Hi Andrea,
I'm using version 5.6.1.5788
Will all users specifically require permission to execute that stored procedure? All that is in the link you quoted is ALTER TRACE and VIEW SERVER STATE permissions to access the default trace but this SP sounds like something different.
I have also seen that this SP (and the dbo.RG_AllObjects_v4 table) does not exist in other SQL Server instances where there is a database under source control - in what circumstances does the table and SP get created?
Thanks,
Chris / comments
Hi Andrea,
I'm using version 5.6.1.5788
Will all users specifically require permission to execute that stored procedure? All that is in the link you quoted is ALTER TRACE and VIEW SERVER STATE perm...
Thanks Ben / comments
Thanks Ben
Hi Ben, the DBA has successfully executed the script and can lock/unlock objects. It is me who still sees the message about setting up locking. We're assuming that I need some additional permissions to use locking? I'm in the db_owner role on the database we're developing but have no access to the RedGate database. Chris / comments
Hi Ben, the DBA has successfully executed the script and can lock/unlock objects. It is me who still sees the message about setting up locking. We're assuming that I need some additional permission...
Hi Laurent, I had the same question about a month ago. If your TFS Server has an internet connection you can use the Register-DlmSerialNumber Powershell cmdlet, otherwise you can activate manually. Here are the instructions I got for that from RedGate:
1) Open a command prompt or powershell window as administrator
2) Run cd "c:\program files (x86)\red gate\DLM Automation 2\SC"
3) Run the following (kindly make sure to run as is and *not* include your serial number) .\SQLCompare.exe /activateSerial:
4) A dialog box will pop up and prompt you for your serial number - enter your serial number in the text box
5) Click "Activate"
6) This will fail and then give you an option to "Activate Manually" --please click this and follow the instructions as usual for manual activation (you'll need to copy and paste the provided request/response text to/from a machine with internet connection)
Chris / comments
Hi Laurent, I had the same question about a month ago. If your TFS Server has an internet connection you can use the Register-DlmSerialNumber Powershell cmdlet, otherwise you can activate manually....
Hi Andrew, I'm not sure that's the functionality I have been seeing - from my test above, I have used a filter (to exclude a table) in SQL Source Control but that filter is not then picked up in my release pipeline. Unless I'm missing something somewhere?
Chris / comments
Hi Andrew, I'm not sure that's the functionality I have been seeing - from my test above, I have used a filter (to exclude a table) in SQL Source Control but that filter is not then picked up in my...
Hi noelc,
Check out the text in the red box in the link "If you specify SQL Compare options in SQL Source Control, these are not used by DLM Automation addons.".
I've just run a quick test with a table:
1) I created a table in my Dev and Live databases
2) I specifically excluded the table from source control by adding a filter on the table name
3) I committed the filter (the table definition is NOT in my repository due to the filter)
4) I ran my build and release process
-> the table was dropped from my Live database (ie the filter in my repository was not used)
5) I added the same filter from step 2) to the filter file I use in my release process
6) I re-created the table in my Live database
7) I ran my build and release process
-> the table still exists in my Live database (ie the filter defined in the release process was used)
Hope that makes sense
Chris / comments
Hi noelc,
Check out the text in the red box in the link "If you specify SQL Compare options in SQL Source Control, these are not used by DLM Automation addons.".
I've just run a quick test with a t...