Activity overview
Latest activity by pcousins
Default Comparison Options and Filter rules
For all our DBs under source control we set the Comparison options to 'Ignore Users' permissions and role memberships', and the filter rules to exclude users. This is because we have different user...
Played around with one database to remove explicit user permissions on objects, but that hasn't helped. To make matters worse, the 2 databases that were tracking correctly in DLM Dashboard have now drifted to an unrecognised schema in production - even though it's the same deployment in 2 test environments which are recognised schemas from TFS. / comments
Played around with one database to remove explicit user permissions on objects, but that hasn't helped.To make matters worse, the 2 databases that were tracking correctly in DLM Dashboard have now ...
DLM Dashboard not recognising Schema from TFS
So I have 4 databases. Each of these are in TFS, and built and deployed via Redgate SQL Change Automation. I have a task group created in TFS to do the build, which also publishes the package to th...
This issue is still ongoing, but now SQL Source Code Control errors with 'Failed to locate the partition function [pfYearly] for the [psYearly] partition scheme. / comments
This issue is still ongoing, but now SQL Source Code Control errors with 'Failed to locate the partition function [pfYearly] for the [psYearly] partition scheme.
I'm looking at this too, but the data isn't stored in a logical way in the Redgate database. / comments
I'm looking at this too, but the data isn't stored in a logical way in the Redgate database.
I'm looking for something similar - a weekly report on top 10 long running queries (actually high CPU and High I/O queries would also be useful), including username and query plan / comments
I'm looking for something similar - a weekly report on top 10 long running queries (actually high CPU and High I/O queries would also be useful), including username and query plan
Here's the script for the partition function: CREATE PARTITION FUNCTION [pfYearly](DATETIME2(0)) AS RANGE RIGHT FOR VALUES (N'2016-01-01T00:00:00.000', N'2017-01-01T00:00:00.000', N'2018-01-01T00:00:00.000', N'2019-01-01T00:00:00.000', N'2020-01-01T00:00:00.000', N'2021-01-01T00:00:00.000', N'2022-01-01T00:00:00.000') / comments
Here's the script for the partition function:CREATE PARTITION FUNCTION [pfYearly](DATETIME2(0)) AS RANGE RIGHT FOR VALUES (N'2016-01-01T00:00:00.000', N'2017-01-01T00:00:00.000', N'2018-01-01T00:00...
SSC claims partition function is different...but it's not.
SQL Source Control is claiming that my partition function is not the same has that in TFS. However, if I try and check in the 'changes' I get 'CheckIn returned with ChangeSet ID=0, nothing to Check...