Comments
Sort by recent activity
I'm afraid the only workaround is to completely sync the schemas using SQL Compare. If there are more tables in one database than the other, you'll encounter this error from the command line. / comments
I'm afraid the only workaround is to completely sync the schemas using SQL Compare. If there are more tables in one database than the other, you'll encounter this error from the command line.
Thanks for your reply, I can see what you mean now.
Unfortunately, the default_schema setting is a user property that is automatically ignored by SQL Source Control. SQL Source control uses our SQL Compare engine to compare the differences between the live database and what's stored in Source Control. It's a default option in SQL Compare to ignore the 'user properties' and SQL source control uses the default SQL Compare options. We have an open feature request to allow the user to configure the SQL Compare engine options, which you might like to vote for here
Currently the only workarounds I can think of are:
1) Delete user1 from DB2 and then 'get' the complete user from source control.
2) Use SQL Compare to deploy the user from Source Control to the database, and turn off the option: 'ignore' > 'user properties'
I hope this helps explain.
Let me know if you need any more information. / comments
Thanks for your reply, I can see what you mean now.
Unfortunately, the default_schema setting is a user property that is automatically ignored by SQL Source Control. SQL Source control uses our SQL...
Thanks for your post.
The default schema should be scripted for the database level users. For example, if you create: CREATE USER [test] FOR LOGIN [test] WITH DEFAULT_SCHEMA=[test_schema]
This will be added to the repository.
How are you creating the user? / comments
Thanks for your post.
The default schema should be scripted for the database level users. For example, if you create:CREATE USER [test] FOR LOGIN [test] WITH DEFAULT_SCHEMA=[tes...
Thanks for your post.
I'm not sure if this is a bug or a feature request, but I see your point. In this situation there is no need to unbind the schema and drop the constraint.
There might be a scenarios where a simple alter table statement would be dangerous, or it might be that the performance implications were not thoroughly considered. I've logged this for our developers to look at under the internal tracking code SC-5055.
Thanks for taking the time to let us know about this. / comments
Thanks for your post.
I'm not sure if this is a bug or a feature request, but I see your point. In this situation there is no need to unbind the schema and drop the constraint.
There might be a sce...
Does this only happen with Word docs, or do you get the same issue with HTML documentation too? / comments
Does this only happen with Word docs, or do you get the same issue with HTML documentation too?
Thanks for your post.
I'm afraid we don't have a fix for this bug yet. The only workaround I can suggest is to only document one database at a time.
Our internal bug tracking code for this issue is SDOC-1402. / comments
Thanks for your post.
I'm afraid we don't have a fix for this bug yet. The only workaround I can suggest is to only document one database at a time.
Our internal bug tracking code for this issue is...
Thanks for your post.
We don't have any method for importing/exporting settings in the current version. I believe it would be a tricky thing to do as each link needs to be linked to the source control system in a specific way, and it would be difficult to tell the source control system that the link has moved to a new location.
We have an open feature request that you might like to vote for: http://redgate.uservoice.com/forums/390 ... ?ref=title
Before you reinstall, I would recommend copying the linked path from the setup tab for each of your databases (right-click > copy). This should save you some time when you relink after you reinstall.
I hope this helps. / comments
Thanks for your post.
We don't have any method for importing/exporting settings in the current version. I believe it would be a tricky thing to do as each link needs to be linked to the source cont...
I'm afraid that's correct. You cannot import SQL Refactor config files into SQL Prompt 5.
The layout functionality was almost completely rewritten for SQL Prompt, so the SQL refactor settings unfortunately cannot be imported. / comments
I'm afraid that's correct. You cannot import SQL Refactor config files into SQL Prompt 5.
The layout functionality was almost completely rewritten for SQL Prompt, so the SQL refactor settings unfor...
Thanks for your post.
SQL Data Compare doesn't attempt to calculate the disk space requirements to execute the script on your database, as factors such as compression and the location of the data files would also need to be considered.
We have some advice that will help you to understand the disk space requirements necessary for a comparison and to create the synchronization script here. SQL Data Compare can create some large temporary files if you're comparing a lot of data.
I hope this helps. / comments
Thanks for your post.
SQL Data Compare doesn't attempt to calculate the disk space requirements to execute the script on your database, as factors such as compression and the location of the data f...
Thanks for your reply.
It's a little confusing, but SQL Data compare will use the default mapping if no /include /exclude switches are used. The default mapping is to map everything it can, so basically anything that has a matching PK, unique index or unique constraint will automatically be added to the project. / comments
Thanks for your reply.
It's a little confusing, but SQL Data compare will use the default mapping if no /include /exclude switches are used. The default mapping is to map everything it can, so basi...