Comments
Sort by recent activity
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...
This forum is for Redgate product questions, not Oracle products. / comments
This forum is for Redgate product questions, not Oracle products.
This isn't a general Oracle question forum. This is a set of forums for Redgate related questions. I'm not sure which Oracle product you are using, but perhaps this will help you: https://docs.oracle.com/cd/E18727_01/doc.121/e13108/T381249T505753.htm / comments
This isn't a general Oracle question forum. This is a set of forums for Redgate related questions. I'm not sure which Oracle product you are using, but perhaps this will help you: https://docs.orac...
What's the workspace error? I would start here, perhaps post a note on SO (https://stackoverflow.com/questions/1267967/how-can-i-bulk-rename-files-using-powershell) or MSDN forums. That's a separate issue from prepping.
Once you get this, for the SOC (SQL Source Control), you'll have issues with the comparison (I think), because the text format of the code may look different to the SOC/Compare engine. What I'd do here is probably use a working folder config first, to get your code from the db into flat files. Then copy those manually to a local working folder for commit back to TFS and get a "clean" copy of the view of the code that SOC uses. I suspect you need to do this. / comments
What's the workspace error? I would start here, perhaps post a note on SO (https://stackoverflow.com/questions/1267967/how-can-i-bulk-rename-files-using-powershell) or MSDN forums. That's a separat...