Comments
Sort by recent activity
The history comes from your VCS. Once you restore from LIVE, I assume that your VCS will be ahead of the dev database, so you'd want to pull changes from the VCS and apply to the restored db.
All history would still be the same in the VCS at this point as applying changes doesn't change anything in the VCS. / comments
The history comes from your VCS. Once you restore from LIVE, I assume that your VCS will be ahead of the dev database, so you'd want to pull changes from the VCS and apply to the restored db.
All h...
This is correct. A known issue that we don't support compressed native backups. We support SQL Backup compressed backups: https://documentation.red-gate.com/display/SDC12/Working+with+backups / comments
This is correct. A known issue that we don't support compressed native backups. We support SQL Backup compressed backups: https://documentation.red-gate.com/display/SDC12/Working+with+backups
The free ReveUnininstaller should help: https://www.revouninstaller.com/revo_uninstaller_free_download.html / comments
The free ReveUnininstaller should help: https://www.revouninstaller.com/revo_uninstaller_free_download.html
I think you have an issue in your SQLCompare command. I see
/sfx:`"F:\ ...
but then I see
txt`""
My guess if you've mismatched your single and double quotes here. You have single double, but then single double again, when I think it should end with double single quote. / comments
I think you have an issue in your SQLCompare command. I see
/sfx:`"F:\ ...
but then I see
txt`""
My guess if you've mismatched your single and double quotes here. You have single double, but then s...
Actually, you can get previous SSMS versions here: https://docs.microsoft.com/en-us/sql/ssms/sql-server-management-studio-changelog-ssms#previous-ssms-releases / comments
Actually, you can get previous SSMS versions here: https://docs.microsoft.com/en-us/sql/ssms/sql-server-management-studio-changelog-ssms#previous-ssms-releases
The add-in lists SSMS 16 as the requirement. SQL 2012 includes an older version of SSMS. You can download SSMS 16 for free, but I don't see a current link. The current version is SSMS 17, but Code Guard doesn't work with this. / comments
The add-in lists SSMS 16 as the requirement. SQL 2012 includes an older version of SSMS. You can download SSMS 16 for free, but I don't see a current link. The current version is SSMS 17, but Code ...
The use case for clone is to quickly spin up new copies of a database. We haven't embraced the idea of a point in time clone that needs to be preserved.
If QA needs data for an extended period, our method would be to create a new image from that clone and use that. If you are worried about DR for QA data, as they make changes, then we aren't really set up to do that at this time.
Clone are meant to be short term in our use case. Create a clone, do something, drop it and restart. Or get multiple clones that can quickly be used to allow separate work in different environments. These aren't mean to be long term items that have a need for DR.
We do have the ability to automate a backup and a new image with PoSh, which can allow you to capture changes at a point in time for future clones, but if you intend for this to be a long term environment for QA, I'm not sure Clone is the right product.
Do you have needs for other copies? I'm wondering where your image is being used outside of QA. / comments
The use case for clone is to quickly spin up new copies of a database. We haven't embraced the idea of a point in time clone that needs to be preserved.
If QA needs data for an extended period, our...
In that case, it's likely you need another image for QA periodically, if you think you'd need multiple clones. However, I assume the 4 QA environments will deviate and get different changes/data alterations over time. In that case, Clone doesn't necessarily help you here.
Is there a way to "age" out the data quickly? Maybe that's a way to deploy a new clone and update it over time. If not, I'd think that you might be better off with a native db backup/restore for QA. / comments
In that case, it's likely you need another image for QA periodically, if you think you'd need multiple clones. However, I assume the 4 QA environments will deviate and get different changes/data al...
I don't think this is possible, but why would you want the diff disk of the clone? We don't have a way to apply this to another cloned image. Is there some use case I misunderstand here? / comments
I don't think this is possible, but why would you want the diff disk of the clone? We don't have a way to apply this to another cloned image. Is there some use case I misunderstand here?
The error shown is a SQL error. What is the table definition you have? You should have a PK on this, which possibly conflicts with the insert statements you have.
You'll need to examine the code for your table data in the /data folder. These should be insert statements, and it's possible that you have a conflict.
Does your build work with a new, empty database or an existing one? It's possible there's an error there. / comments
The error shown is a SQL error. What is the table definition you have? You should have a PK on this, which possibly conflicts with the insert statements you have.
You'll need to examine the code fo...