Comments
Sort by recent activity
When I attempt to open Tab History, this is the error I'm getting: '{DependencyProperty.UnsetValue}' is not a valid value for property 'OpacityMask'. SSMS: Microsoft SQL Server Management Studio 11.0.5058.0 / comments
When I attempt to open Tab History, this is the error I'm getting:'{DependencyProperty.UnsetValue}' is not a valid value for property 'OpacityMask'.SSMS: Microsoft SQL Server Management Studio 11.0...
CraigEddy said:
When I attempt to open Tab History, this is the error I'm getting: '{DependencyProperty.UnsetValue}' is not a valid value for property 'OpacityMask'.
SSMS: Microsoft SQL Server Management Studio 11.0.5058.0
This is fixed in 9.5.23.12091. Thanks! / comments
CraigEddy said:
When I attempt to open Tab History, this is the error I'm getting:'{DependencyProperty.UnsetValue}' is not a valid value for property 'OpacityMask'.
SSMS: Microsoft SQL Server...
@Tianjiao_Li I was able to get the Web folder deleted by first un-installing IIS Express, then deleting the folder, and then using the installer again. I'll probably pursue using IIS soon, when I find time to get it configured on that machine. Thanks for your help. Craig / comments
@Tianjiao_Li I was able to get the Web folder deleted by first un-installing IIS Express, then deleting the folder, and then using the installer again.I'll probably pursue using IIS soon, when I fi...
Tianjiao: I'm getting a similar error with SQLMonitorWeb_8.0.17.16240.exe but now it's about the C:\Program Files\Red Gate\SQL Monitor\Web\Website\Scripts folder. I uninstalled the SQL Monitor Web Services and tried the installer with the same result. / comments
Tianjiao: I'm getting a similar error with SQLMonitorWeb_8.0.17.16240.exe but now it's about the C:\Program Files\Red Gate\SQL Monitor\Web\Website\Scripts folder. I uninstalled the SQL Monitor Web ...
Yes, that worked like a champ! Thank you! / comments
Yes, that worked like a champ! Thank you!
Wow! I think version 2.0.23 has fixed this. Thanks! [image] / comments
Wow! I think version 2.0.23 has fixed this. Thanks!
The BAK files were indeed being generated daily, but always overwrite the contents of that folder and named, for example, "FIARPE.BAK" (we actually have three databases which we image/clone and all three exhibited the issue we're seeing). The images were created with the date suffixes in the image names.
The FIARPE_20171221.BAK instance was my hope that if we just renamed the source BAK file then we wouldn't see this problem.
We definitely confirmed that if we create an image from a particular BAK file, clone it to a server, and check its data that the data was not coming from the source BAK file. However, if we restored that same BAK file directly to a server, the data was indeed current.
Thanks, I'll send an email to support. / comments
The BAK files were indeed being generated daily, but always overwrite the contents of that folder and named, for example, "FIARPE.BAK" (we actually have three databases which we image/clone and all...
You could use the Powershell script above, augmented to write the data into the table of your choice in your SQL Server instance. Just a thought... / comments
You could use the Powershell script above, augmented to write the data into the table of your choice in your SQL Server instance. Just a thought...
We are also giving up on using SQL Source Control migration scripts.
Constantly running into issues with the scripts taking forever to construct in SQL Compare, if they get generated at all.
The most common inexplicable error is something about "2 conflicts prevent checkout" while generating a deployment script in SQL Compare.
We have made a heavy investment in time trying to troubleshoot issues with these scripts, all in the hope of one day automating our database deployments. But with so much manual intervention required in order to just get the scripts and their associated files to even be processed by SQL Compare, automation seems impossible.
Thanks,
Craig Eddy / comments
We are also giving up on using SQL Source Control migration scripts.
Constantly running into issues with the scripts taking forever to construct in SQL Compare, if they get generated at all.
The mo...