250 results found
-
Include tables in "use drop and create instead of alter" comparison behavior
Provide additional option to "use drop and create instead of alter" so that tables can be reconstructed blindly
32 votes -
Add BACPAC to SQL Compare (and SQL Data Compare)
At the moment you can compare Database, Backup, Snapshot and Source Control.
Please add a BACPAC file as well.
A BACPAC is an artifact that encapsulates the database schema as well as the data stored in the database. The BACPAC is a Windows file with a .bacpac extension. Similar to the DACPAC, the BACPAC file format is open – the schema contents of the BACPAC are identical to that of the DACPAC. The data is stored in JSON format.
How to: Import and Export a Database (Windows Azure SQL Database)
http://msdn.microsoft.com/en-us/library/windowsazure/hh335292.aspxImport a BACPAC File to Create a New User…
88 votes -
Compare (and migrate) Database Diagrams
I'd love to see a function in SQL Compare to compare and migrate Database Diagrams. Especially between servers, but certainly on the same server.
We use them all the time to work on the structure of the of our databases and I'd love to be able to see the same diagram when I'm working in Prod and Test as I do in Dev without having to bring the changes across manually.
The code (for the easy case) is pretty simple.
UPDATE MyDB.dbo.sysdiagrams
SET definition = (
SELECT definition
from MyOtherDB.dbo.sysdiagrams
WHERE name = MyDB')
WHERE name = 'MyDB'17 votes -
Provide the ability to specify object permissions within custom filter rules
Currently (v 13), there is an all-or-none project option to include or exclude object permissions across all database objects. It would be fabulous to push that option down into custom filter rules so inclusions/exclusions can happen more granularly, at an object-level. Use case: the majority of our tables use generic permissions but a small subset of tables use ActiveDrictory groups that differ by environment so we have to manage them as a special case. I'd love to be able to specify something like this as a filter rule: 'generate object permissions for all tables except tables that begin with <blah>'.
4 votes -
I have found that User Defined Data Types are not scripted after stored procedures that use that data type.
I have found that User Defined Data Types are not scripted after stored procedures that use that data type.
3 votes -
Add option to ignore target only objects
When comparing two databases it would be nice to have the ability to have objects that only exist in the target be ignored. It is somewhat dangerous to have an option that would cause objects to be dropped and it would be good to be able to not have that show.
4 votes -
Compare against Database Projects
It would be great to see SQL Compare support Visual Studio Database Projects (.sqlproj).
Current if you choose Source Control | Scripts, you can point to the project folder, but then SQL Compare gets confused because it loads in extra .sql files (eg. the 'create database'.sql that gets put in the build output 'bin' folder).
Selecting the 'Tables' sub-folder works more reliably (if just comparing tables!), but then pushing changes down to the files results in schema that no longer compiles because the SSDT tools require 'GO' separators between each DDL statement.
5 votes -
Comparing TFS Changesets
When comparing a TFS Changeset in SQL Compare it will show all schema changes that are different between the Changeset and the destination, but within a TFS Changeset, there is metadata within the Changeset to indicate which specific database objects are being changed within the Changeset. It would be a huge timesaver to allow SQL Compare to be able to only select the database objects that are actually being impacted by the Changeset by default. The situation I have is this:
Developer 1 - Adds a table to database A and checks in the change to the development database, but…
6 votes -
Display last change dates in top database strip
Display last change dates of repository for databases under SQL Source Control.
And display also last schema change date from database.
4 votes -
My projects - compare all projects
Add an additional "Compare all" button to compare all projects in the actual "Look in" folder. Show a simple is equal/different indicator on each project for the results.
Consider using VS-style solution files or kind of meta-scp.
This is somewhat similar to https://redgate.uservoice.com/forums/141379-sql-compare/suggestions/13517250-auto-compare-after-oping-a-project-mass-compare
6 votes -
Drop
Add an option to DO NOT DROP missing fields in the target, this way I'm just adding missing fields from the source.
16 votes -
Unecessary table rebuild
The tool will try to rebuild the whole table even when the only thing needed is the addition of one column. If you need it, I can send an image of the comparison results. To work around it, I search for rebuilds within the generated script and substitute them by the needed command, specially if the table is a very large one.
1 vote -
Option to select individual dependencies (or affected objects) when migrating changes with the deployment Wizard.
Currently the Deployment Wizard only allows for all dependencies to be specified, or not. If I know a specific dependency to be problematic (will fail the overall deployment if selected) my only options are to not deploy dependencies (not good) or to generate a migration script and step through it a bit at a time or remove references for the dependencies I need to skip, which can be cumbersome when dealing with many changes. It would be nice to be able to choose all dependencies (current option), specify not to deploy dependencies (currently an option), or incrementally check on or…
74 votes -
When tables have different number of indexes the compare will show differences when in reality the indexes are the same, just not aligned.
A table on server 1 has 2 indexes. The same table on server 2 has 4 indexes. Depending on the order that the script generates the DDL the compare might show all 4 indexes as different/new where it should show 2 as the same and 2 new.
89 votes -
38 votes
-
Filter Improvements
I use SQL Compare very rarely. Most of the time I use it to find the differences between two databases with different structure version. And therefore I need to see in a blink of an eye what dml triggers are missing or outdated or whatever. Currently there is no possibility to filter for table objects like dml triggers.
It would be very nice if there is an option to restrict the view depending on sub elements like Index, Column, Collation, Trigger.
Maybe it would be enough if the seach bar at the top would also search the SQL view of…7 votes -
Allow comparing objects of all types with different names, not just tables.
It would be nice to be able to use RGSC to compare such objects by re-mapping. A recent change allows doing this, but with tables only. All other objects would be a helpful touch.
This could be useful for several scenarios, including demonstrating a proposed change to a current version. We also sometimes end up with different test versions of objects that differ slightly with less than helpful comments. (b/c all our devs' code is self documenting!)45 votes -
BUG: Filter Rules do not apply to triggers.
We're using MS Data Sync Services which makes heavy use of versioned tables and triggers to populate these tables. The objects are named x.x.x.xTableName (example 1.0.0.13Table and 1.0.0.13Tabledeletetrigger. The triggers to populate these objects are placed on the base table (TableName, not x.x.x.xTableName).
To create deployment scripts, I utilize filter rules to remove table names, stored procedures, UDDTs, etc. used by Data Sync Services. However, the DSS triggers placed upon the base table are still scripted out; they are not filtered out as I would expect.
P.S. For those thinking of using Data Sync…
4 votes -
filter
In SQL Compare make it remember the filter you last choose.
I set up my filters and saved them to a file. Then picked that file in the filter drop down.
The next time I bring up SQL Compare, I have to pick the filter again from the drop down. SQL Compare should remember the last one I used. Or give me the option to remember it like The Project Options allow you to save as My Defaults.
8 votes -
Option to script indexes and triggers into their own sub-folders
Project level option to script indexes and triggers into their own sub-folders. This allow for a more granular check-in and makes text diffs more clear.
37 votes
- Don't see your idea?