Comments
Sort by recent activity
Hi Roman, I'm really sorry that you're encountering such a degradation of performance. Do you know which version of ReadyRoll you were using before? Can you please change the logging setting in the logging.config files by setting it to the below value: <level value="DEBUG" /> These files are at these locations: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\SqlChangeAutomation\logging.config C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions\001rr241.rgs\logging.config (001rr241.rgs will be different in your case). Please note that the folder locations might be different depending on the version of VS that you are using. The log files should help to pinpoint the exact operation that takes most of the time. After you replicate the issue please change it from `DEBUG` to `FATAL`, to make sure that logging itself is not the culprit. / comments
Hi Roman,I'm really sorry that you're encountering such a degradation of performance.Do you know which version of ReadyRoll you were using before?Can you please change the logging setting in the lo...
@davejhahn, thank you for your report, it is a bug indeed. We'll fix in the next release of SQL Change Automation Visual Studio extension. / comments
@davejhahn, thank you for your report, it is a bug indeed. We'll fix in the next release of SQL Change Automation Visual Studio extension.
Hello Eric, I do confirm that LocalDB 2017 is supported by SQL Change Automation projects and doesn't require any additional configuration. However, there is a known issue regarding LocalDB itself. It should be enough just to delete the instance by running: SqlLocalDB.exe delete ReadyRollShadowFor a more detailed guidance, see https://www.red-gate.com/sca/localdb-instance-troubleshooting . Please also note, that in case you encounter an error similar to:CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'C:\Users\usernameDatabaseName.mdf'you just need to update the LocalDB with the Cumulative Update >= 6. For more details see https://dba.stackexchange.com/a/191748/161450 . I also recommend updating the legacy ReadyRoll VSTS pipeline to a recent one that uses SQL Change Automation PowerShell. Also, I'm pretty sure that you've done this already, but for the future reference, it's recommended to target a proper database version in a sqlproj file. You can do this either using the project properties page or by directly editing the sqlproj file and setting the below value (in this case for SQL Server 2017):<DSP>Microsoft.Data.Tools.Schema.Sql.Sql140DatabaseSchemaProvider</DSP> / comments
Hello Eric,I do confirm that LocalDB 2017 is supported by SQL Change Automation projects and doesn't require any additional configuration.However, there is a known issue regarding LocalDB itself. I...
Hi Nick, Thank you for reporting this issue. We'll release a fix for this in the ver. 2.0.33 soon. For now, you should be able to register DLM Automation by using the Register-DlmSerialNumber cmdlet: https://documentation.red-gate.com/dlma2/cmdlet-reference/register-dlmserialnumber Apologies for the inconveniences caused. Greg / comments
Hi Nick,Thank you for reporting this issue. We'll release a fix for this in the ver. 2.0.33 soon.For now, you should be able to register DLM Automation by using the Register-DlmSerialNumber cmdlet:...