Bad performance and incorrectly included items on Get Latest
sognibene
Posts: 11
Hello,
I have SQL Source Control 3.4.2.61 running against TFS 2010 and SQL Server 2012 SP1 with the latest CU installed. My SQL Server is local on my workstation (quad core, 14GB RAM) and TFS is on the network.
I am trying to get the latest "Filter" from source control. When I select only the filter and click "Get latest", the SQL Source Control "Retrieving changes from source control" hangs and uses 100% cpu for several minutes.
I then get a "Warnings" dialog that includes among other things a High warning that a deployment script with no name ("") will be used, and then it says it will drop a user and three schemas.
Why would this happen when I am just trying to get the updated filter?
Thanks.
Severity: High
Title: Some of the changes you selected are covered by the migration script ""
This will be used to generate the deployment script.
Severity: Low
Object: ReportViewer
Title: Dropping a user is a potentially dangerous operation. Dependencies for the ReportViewer user are not selected automatically. If you are sure you want to drop this user please select the objects that belong to this user manually.
Severity: Low
Object: [I removed the name here]
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the [I removed the name here] schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: [I removed the name here]
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the [I removed the name here] schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: SQLCop
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the SQLCop schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: [I removed the name here]
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the [I removed the name here] schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: tSQLt
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the tSQLt schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
I have SQL Source Control 3.4.2.61 running against TFS 2010 and SQL Server 2012 SP1 with the latest CU installed. My SQL Server is local on my workstation (quad core, 14GB RAM) and TFS is on the network.
I am trying to get the latest "Filter" from source control. When I select only the filter and click "Get latest", the SQL Source Control "Retrieving changes from source control" hangs and uses 100% cpu for several minutes.
I then get a "Warnings" dialog that includes among other things a High warning that a deployment script with no name ("") will be used, and then it says it will drop a user and three schemas.
Why would this happen when I am just trying to get the updated filter?
Thanks.
Severity: High
Title: Some of the changes you selected are covered by the migration script ""
This will be used to generate the deployment script.
Severity: Low
Object: ReportViewer
Title: Dropping a user is a potentially dangerous operation. Dependencies for the ReportViewer user are not selected automatically. If you are sure you want to drop this user please select the objects that belong to this user manually.
Severity: Low
Object: [I removed the name here]
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the [I removed the name here] schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: [I removed the name here]
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the [I removed the name here] schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: SQLCop
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the SQLCop schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: [I removed the name here]
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the [I removed the name here] schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: tSQLt
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the tSQLt schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Comments
Failing this, unlink your database and relink it without setting the migrations folder and try the get latest again.
Migration scripts are used when you want to customize the behavior of SQL Compare's comparison and sychronization engine.
David Atkinson
Red Gate
Product Manager
Redgate Software
I hadn't patched SQL compare in a while so I am going to restore a new copy of my database and try again. If I can reproduce the problem is there a log file I can send in that might be helpful?
We've opened up a ticket for you and will be in contact shortly. In the meantime, you can find the log files for SQL Source control here: YOURDRIVE:\Users\YOURUSERPROFILE\AppData\Local\Red Gate\Logs\SQL Source Control 3
Thanks,
Evan
Product Support
(866) 627-8107