Comments
Sort by recent activity
That's correct. a FULL backup of the source database. / comments
That's correct. a FULL backup of the source database.
Thanks for your post.
SQL Backup log shipping jobs are created as SQL Agent jobs in SQL Server. If you want to delete the exiting jobs, then the only way to do it is through the SQL Agent.
If you are happy with the existing log shipping configuration, then you could restart the process by reseeding rather than starting again from scratch.
See the link below for instructions: http://www.red-gate.com/supportcenter/C ... wledgebase\SQL_Backup\KB200901000347.htm&p=SQL%20Backup
I hope this helps. / comments
Thanks for your post.
SQL Backup log shipping jobs are created as SQL Agent jobs in SQL Server. If you want to delete the exiting jobs, then the only way to do it is through the SQL Agent.
If you a...
I forgot to update this post with the outcome of the issue.
The problem was that having a large number of queries open in SSMS can cause memory issues. Balancing the open queries using multiple SSMS instances is one workaround, but SQL Source control will only work from the first instance.
Supporting multiple instances of SSMS isn't currently on the roadmap, but you can vote for the feature here: http://redgate.uservoice.com/forums/390 ... ?ref=title
In the mean time, you could have multiple instances of SSMS open, but just make sure you do all your source control tasks through the first instance.
I hope this helps anybody experiencing this issue. / comments
I forgot to update this post with the outcome of the issue.
The problem was that having a large number of queries open in SSMS can cause memory issues. Balancing the open queries using multiple SSM...
1) The ignore identity doesn't seem to work
2) There is no way (as far as i can tell) to ignore ROWGUID columns
see http://www.red-gate.com/messageboard/vi ... hp?t=11539
3) Constraints are dropped for tables but not recreated
Do you have an example of this? Any constraints that need to be dropped should be added again. We can open a support ticket for this if you would like to work on it privately.
4) There is no option for using ALTER TABLE commands instead of dropping and recreating the table (BIG problem)
SQL Compare will try to ALTER when it can, but there are certain situations where it will need to rebuild. Here is a KB article that discusses the reasons.
5) When scripting synchronization, there should be an option to script tables and their dependencies seperately because otherwise you get all kinds of errors on views trying to add columns that don't exist yet.
SQL Compare will build the script in dependency order and even try to break circular dependencies. However, there are circular dependencies that it can't break which might result in an invalid script. If you would like to investigate the dependency issue you're having, we can open a support ticket for you.
I hope this helps. / comments
1) The ignore identity doesn't seem to work
2) There is no way (as far as i can tell) to ignore ROWGUID columns
see http://www.red-gate.com/messageboard/vi ... hp?t=11539
3) Constraints are d...
Thanks for your enquiry.
Unfortunately there isn't a way to ignore specific columns in the current version of SQL Compare. This includes any identity columns or rowguid columns. If you compare a table, all columns will be included in the comparison.
We have a feature request in place to allow a greater deal of control, basically allowing you to treat a column as an object in its own right. This will also be the same for permissions, triggers, indexes etc. The feature number for this is SC-2447 and I have added you as another vote for the feature.
The option to ignore identity seed and increment values is just to allow you to not synchronize the difference in the configuration of the identity column. For example, if you have a IDENTITY (1,1) in Db1 and IDENTITY (3,8) in Db2, this option would ignore this difference. However, if the table is synchronized for another reason, these settings will be synchronized too.
I hope this helps. / comments
Thanks for your enquiry.
Unfortunately there isn't a way to ignore specific columns in the current version of SQL Compare. This includes any identity columns or rowguid columns. If you compare a ta...
Thanks for your post.
You haven't missed a feature, the report facility only shows you backup history. It's a good suggestion to add restore data to this report, so I've logged a feature request for it (SB-4562).
Currently, the best way to view the restore history will be to view the activity history within the GUI. / comments
Thanks for your post.
You haven't missed a feature, the report facility only shows you backup history. It's a good suggestion to add restore data to this report, so I've logged a feature request fo...
Thanks for your post.
I'm afraid there aren't any grouping options like that in the current release.
It seems like a good suggestion, so I have logged it as a feature request for a future version (DT-587).
Sorry I can't be of more help. / comments
Thanks for your post.
I'm afraid there aren't any grouping options like that in the current release.
It seems like a good suggestion, so I have logged it as a feature request for a future version (...
Thanks for your reply, I'll look into this.
Can you let me know the data type of the column, and what version of SQL Server? / comments
Thanks for your reply, I'll look into this.
Can you let me know the data type of the column, and what version of SQL Server?
We investigated this through a private support ticket.
It turned out to be an issue where the precision of the float data was being displayed differently in different parts of the UI. It didn't seem to impact on the synchronization.
A bug has now been logged for this: SDC-1137 / comments
We investigated this through a private support ticket.
It turned out to be an issue where the precision of the float data was being displayed differently in different parts of the UI. It didn't see...
Thanks for your post.
The row differences pane will round up values of very high precision, but it shouldn't affect the value when you synchronize. I believe the rounding is just there to make it more readable in the UI.
Is this causing any problems for you during the synchronization i.e. is it changing the values to be incorrect? Or is the problem that the rounded results are misleading in the UI? / comments
Thanks for your post.
The row differences pane will round up values of very high precision, but it shouldn't affect the value when you synchronize. I believe the rounding is just there to make it m...