Activity overview
Latest activity by DavidRG
Sorry for the delay in getting back to you!
We're not yet sure what's going on, so can you please download and run https://aka.ms/vscollect to collect the full detailed logs, send them to us (support@red-gate.com), and then we'll send them onto Microsoft for them to analyse and see what happened. / comments
Sorry for the delay in getting back to you!
We're not yet sure what's going on, so can you please download and run https://aka.ms/vscollect to collect the full detailed logs, send them to us (suppo...
Hi Greg,
Migrations V1 used extended properties -- called "SQLSourceControl Database Revision" and "SQLSourceControl Scripts Location"
Whereas, Migrations V5 now uses a table instead -- called "DeploymentMetadata" in the schema "RedGateLocal".
We are in the process of transitioning all of our tools away from Migrations V1 and on to Migrations V5 (there is an upgrade process in SQL Source Control 5 where you can upgrade any migration scripts that are in the old format if you've got any).
What you're observing is an effect of us removing some of the Migrations V1 code but not all of it -- basically when SQL Compare goes down the new Migrations V5 code path it doesn't add the extended properties, but when it goes down the old Migrations V1 code path it does add them.
It should be fine that the extended properties are sometimes missing, by which I mean, it shouldn't cause any problems to automated database deployments. If you observe any weird behaviour with the extended properties being missing then get back in touch, and we'll investigate [image]
If you're relying on the extended properties yourself in your own code, then you should now start relying on the DeploymentMetadata table -- it's documented at https://documentation.red-gate.com/disp ... ntMetadata / comments
Hi Greg,
Migrations V1 used extended properties -- called "SQLSourceControl Database Revision" and "SQLSourceControl Scripts Location"
Whereas, Migrations V5 now uses a table instead -- called "Dep...
Hi,
This can also occur if you've disabled JavaScript for the DLM Dashboard site -- if you've got NoScript running (or anything else that could block JavaScript), can you please try again, this time allowing JavaScript?
Thanks!
David / comments
Hi,
This can also occur if you've disabled JavaScript for the DLM Dashboard site -- if you've got NoScript running (or anything else that could block JavaScript), can you please try again, this tim...
You’re right, I should have given you more detail – apologies!
Here are the minimum permissions required for DLM Dashboard to work: -- Permissions you need on SQL Server to add that SQL Server to DLM Dashboard
USE master
CREATE LOGIN dlmDashboard WITH PASSWORD = N'ChangeMe!'
GRANT VIEW ANY DEFINITION TO dlmDashboard
GO
USE RedGate
CREATE USER dlmDashboard FOR LOGIN dlmDashboard
GRANT SELECT ON SQLLighthouse.DDL_Events TO dlmDashboard
GO
USE master
CREATE USER dlmDashboard FOR LOGIN dlmDashboard
GRANT EXECUTE ON dbo.RG_SQLLighthouse_ReadEvents TO dlmDashboard
GO
-- Permissions you need on a database in SQL Server to add that database to DLM Dashboard
USE databaseName
CREATE USER dlmDashboard FOR LOGIN dlmDashboard
GRANT SELECT ON sys.sql_expression_dependencies TO dlmDashboard
GO
In addition to that, there are two optional permissions which you can grant if you need to - be careful with these! -- ONLY if you have encrypted objects
EXEC sp_addsrvrolemember 'dlmDashboard', 'sysadmin'
GO
-- ONLY if you want DLM Dashboard to install the server-wide trigger
USE master
GRANT CONTROL SERVER TO dlmDashboard
GO
I hope that helps! / comments
You’re right, I should have given you more detail – apologies!
Here are the minimum permissions required for DLM Dashboard to work:-- Permissions you need on SQL Server to add that SQL Server t...
Thanks for bringing this to our attention. I've been able to reproduce the issue here, and I've done a quick investigation into how we might fix it.
I've added supporting memory optimised tables to our backlog. However, given that it's a lot of work, and given that you are so far the only user that's asked for it, and also given that there are a lot of things on the backlog, I think that it's going to be a while before we work on it [image] / comments
Thanks for bringing this to our attention. I've been able to reproduce the issue here, and I've done a quick investigation into how we might fix it.
I've added supporting memory optimised tables t...
This blog post should hopefully answer your questions: http://blog.red-gate.com/ship-dlm-dashboard-beta/
Please let me know if you need any more information [image] / comments
This blog post should hopefully answer your questions: http://blog.red-gate.com/ship-dlm-dashboard-beta/
Please let me know if you need any more information
I'm David -- a software developer on the DLM Dashboard team.
This issue can occur if the user account you enter in the DLM Dashboard interface doesn't have sufficient permissions to check that the objects are installed correctly. Can you please try again with an account with more permissions. Thanks [image] / comments
I'm David -- a software developer on the DLM Dashboard team.
This issue can occur if the user account you enter in the DLM Dashboard interface doesn't have sufficient permissions to check that the ...
We've fixed this bug in today's release (0.0.3.463). It will now only enable the clean build option for builds that use our runner, leaving all other builds untouched. You can download the fixed build from: http://downloads.red-gate.com/EAP/openMe/openMe.zip
Let us know if you have any further problems,
David / comments
We've fixed this bug in today's release (0.0.3.463). It will now only enable the clean build option for builds that use our runner, leaving all other builds untouched. You can download the fixed ...
If you mean renaming the database on SQL server, then the best way is:
1. make sure that both the commit tab and the get latest tab are empty by committing all your outstanding changes and gettting all of your teammates
2. on the setup tab, right-click on the URL where it's linked to and click copy
3. on the setup tab, unlink the database from source control
4. rename the database
5. on the setup tab, link it to the same location (you can paste the URL that you copied above)
6. visit the commit tab and wait for the spinny to finish (you should see the spinny say "Accepting updates from source control" which is where it determines that your database is already fully up-to-date with no changes to commit or get, and we sort out our internal data structures to reflect this)
At this point you should be done. Let me know if you have any problems. / comments
If you mean renaming the database on SQL server, then the best way is:
1. make sure that both the commit tab and the get latest tab are empty by committing all your outstanding changes and gettting...
Our internal builds are currently using a daily build of SharpSvn that is built again SVN 1.7. It's looking pretty good at the moment (there's 1 outstanding known issue that we need to fix), so it's highly likely that the next Early Access release of 3.0 will have it (unfortunately it didn't make the Early Access release that went out earlier today). / comments
Our internal builds are currently using a daily build of SharpSvn that is built again SVN 1.7. It's looking pretty good at the moment (there's 1 outstanding known issue that we need to fix), so it...