244 results found
-
Create scripts folder ignoring fill factor
File->Create scripts folder should script index fill factor. When the created folder is compared against a DB I can optionally include/exclude the fill factor as I need
6 votes -
powershell cmdlets for SQL Compare
It would be nice to have clean powershell cmdlets (like SCA) for SQL Compare rather than having to use the old-school command line and arguments.
2 votes -
Software updates not appearing when Help, Check for updates is used
Currently using version 14.1.7.14336. clicking on Help, Check for updates. I get you are running the latest version. But there has been 3 updates released since. The current update is 14.1.10.14805 released 01/27/20.
Trying to see why this happening. How long does it take for the software to see these updates.2 votes -
Option to Ignore Temporal/History Table
It would be handy to have an option to ignore Temporal/History table configuration when comparing two like databases where one has had some tables configured as temporal with a history table. This would be helpful to isolate any other changes outside of the temporal/history configuration.
20 votes -
1 vote
-
It would be helpful to provide the capability to examine two objects within the same database.
I've worked over many years with multiple teams and I observe the same phenomenon. The proliferation of OLD, _BAK, _20191123, _ETC objects as developers try out new things for all sorts database artifacts; Tables, Views, Sprocs, etc. I would find it immensely helpful to compare two such artifacts, TABLE and TABLEOLD (for example) to see what has been changed.
4 votes -
Search within objects
Compare already has a search filter, however it would be great if you could also search within the objects and not just by the object names.
8 votes -
More efficient scripting for non-varchar/nvarchar extended properties
At the moment, extended properties that are varchar or nvarchar are scripted out by SQL Compare as literals ('value' or N'value'). Unfortunately every other data type is scripted out over three lines (plus a GO), declaring an @xp variable of the appropriate data type, SELECTing (not SETting) its value, and finally adding the property.
With heavy use of extended properties, or even mild use of non-(n)varchar properties, change scripts (and object scripts in SQL Source Control) can become huge pretty quickly. This causes various issues, not least of which is readability during peer review/PR approval.
I'd like to see this…
3 votes -
Option to "Ignore index named like nci_wi_%
Please add an option to "Ignore index named like nciwi%
These index are added by SQL Server (starting with Azure SQL DB), as part of optimizing the workload on a database.
They make it impossible to compare two databases, as too many "false" differences exists.
28 votes -
Script subfolder exclusion
When using script as a comparison source allow the ability to exclude one or more of the subfolders.
4 votes -
Prevent ProjectGuid changes in RedGateDatabaseInfo.xml (conflict with SQL Source Control)
We use both SQL Compare and SQL Source Control to track schema changes. When you update scripts using SQL Compare, it sets the ProjectGuid property in the RedGateDatabaseInfo.xml file. When you check in changes using SQL Source Control, it removes the ProjectGuid from the file. This creates extra work because source control indicates there are differences or conflicts when this is the only change. It would be helpful if the two tools functioned the same.
2 votes -
Add a possibility to update all installed Redgate tools
I have installed the SQL Toolbelt and I would like to update all its components in one shot. Currently, It is possible only by downloading the setup of Toolbelt from Redgate site and "re-installing" the products.
When I go to Help->Check Updates for particular component, let's say SQL Compare, only this component can be updated. And mostly I have to close All my SQL Server Management Studio (SSMS) session and Visual Studio (VS) Sessions for the
update, which is time-consuming, but I guess makes sense.But after this, I start again all my SSMS and VS sessions and When I…
3 votes -
Install update ribbon obscures the 'to and from' database machine name
With a deadline looming I needed to do a comparison, but I could not see the 'to and from' database machine name until I installed the update. It was hidden underneath the ribbon.
2 votes -
CSV should use entirely empty value (no "") for null
Current behaviour: the CSV file represents null as the 8-character string “<NULL>” . e.g. If I have a table with an integer primary key column id, a varchar column a, and a varchar column b, and the table has one newly-inserted row (1, NULL, “asdf”), the CSV file would look like this:
o “Type”,”idk”,”as”,”at”,”bs”,”b_t”
o “In1”,”1”,”<NULL>”,””,”asdf”,””Desired behaviour: allow the CSV file to represent null as a completely empty entry. E.g. the CSV file would look like this:
o “Type”,”idk”,”as”,”at”,”bs”,”b_t”
o “In1”,”1” ,, ””,”asdf”,””Suggested options:
1) Command line switch toggling between…
10 votes -
Save Group By Value in Sql Compare
Save the state of the Group By drop down so that we don't have to change it with each managed project.
3 votes -
Autofill fields for "Create new snapshot" using the other database selected
The source for create new snapshot defaults to database. Automatically populate Server, Authentication, Database and New Snapshot name using the Database information on the other side of the compare window.
Customizable name tags for the new snapshot name would be perfect: [SERVER][DATABASE][DATETIME].snp
6 votes -
Create a snapshot of target database before deployment
I usually create a snapshot of the target database before each deployment so I can compare again later to see the changes or generate a reversal script on selected objects. Please add the option to the Deployment wizard alongside "Back up target before deployment"
3 votes -
Be more robust in the face of Transport Errors
Data Compare almost always fails because of frequent (but short) network outages. If we could specify a long timeout, that would solve this problem.
6 votes -
Column Filters
In the results grid, give the ability to filter the results instead of having to sort, great example is the schema column, let us filter by schema instead of having to sort and then scroll to find the schema we want to look at.
1 vote -
Add an option to the behavior section to include SORT_IN_TEMPDB = ON on all of the CREATE INDEX statements.
For those of us working with data warehouses, using SORTINTEMPDB is the default behavior we need.
9 votes
- Don't see your idea?