588 results found
-
Force "Get Latest" even when tool thinks there are no changes.
Our test environment is set up such that the servers and databases all have the same name as production. This causes SQL Source Control to think I'm connected to ServerA when I am really connected to ServerB. Thus, the "Get Latest" tab shows "No new changes in source control" even though there are changes I wish to get. The "Commit Changes" tab still shows changes so the tool knows there are differences, but won't show any "Get Latest" items. This happens in both the "Dedicated" and "Shared" setups. I must unlink the database and relink it in order for it…
20 votes -
Support Filetables with Fulltext-Index!
I Need it so badly. Having a Error in every view of the GUI because of it
1 vote -
1 vote
-
Set default options for comparison
Allow use to set default comparison options e.g. <AddDatabaseUseStatement> rather than have to do it for every individual database linked.
5 votes -
Removing column does not generate update in static data
If a table is setup for static data, and you remove one or more columns from that table, the static data is not updated in the working directory when "Saving changes".
7 votes -
Deploy to database without preserving data
am trying to deploy changes to tables from one database to another as part of development. SQL Compare insists on creating temporary tables in the target database, putting the data in them, and then trying to insert the data back into the new tables (which now have different types/names for columns).
I cannot find an option to turn off the preservation of existing data.
I want to deploy my schema changes while discarding any existing data if present. (It is called SCHEMA compare after all)I don't understand why there isn't an option to ignore data currently in target tables…
3 votes -
Indexed view definitions don't compare with latest version properly
When comparing view definitions from local objects to latest source control version (perforce in our case), SQL Source control doesn't properly read the data compression options from the source control version. So we'll get a difference, showing "WITH (DATA_COMPRESSION = PAGE)" highlighted orange on the left....however the source control file also has this clause, it's just not being read properly. If I check in the file, it will refresh and the same object will still show a difference with source control, even though it's not.
4 votes -
Filter and Comparison Options should *always* show on top if not in sync.
It's far too difficult to find the Filter and Comparison Options items if there are lots of things that might be filtered out or excluded via options. These items should always show on top regardless of the UI sort order because they are so important to synchronize first.
7 votes -
Partition scheme Bug?
We have a partition scheme setup using a function
CREATE PARTITION SCHEME [partitionSchemeSystemId]
AS PARTITION [partitionFunctionSystemId]
TO ([PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY])when SourceControl has populated SVN it has added an extra partition to the scheme
Sourcecontrol sees these as being the same between the DB used to populate SVN but when we link a new instance of the database to sourcecontrol it identifies a conflict
4 votes -
It would be great to see the changes before they are commited to the source control
This would be a comparision between the local version of the files (e.g. loaded from the database) with the latest release on the version control system.
1 vote -
Allow include Identity option at table level instead of Database level.
In many databases there few tables with static values which are mapped with enums in the code. For such tables, Include Identity columns option is required. However, for few tables, we may not require to maintain the same primary key value in the source and target DB. Please do the needful
29 votes -
some extended property or search item or project option to “link” static data tables ONLY – this would be a huge time saver.
We have thousands of tables (some with millions of rows) with only 90-100 static data tables.
At the moment, I have to edit the project; untick all then tick 90-100 manually which is very time consuming.
If there was some extended property or search item or project option to “link” static data tables ONLY – this would be a huge time saver.
Thanks for your response.
Regards
11 votes -
"Select object in Object Explorer" in Commit (like SQL Search)
"Select object in Object Explorer" in Commit (like SQL Search), makes it a lot easyer to continue working on things, that is not yet commitet.
13 votes -
5 votes
-
fingerprint reader login
I would like to login on any SQL Source Control system using the fingerprint reader.
6 votes -
SQL errors when constructing temporary database should show failing script
On creating a new migration script (Migrations V2) and switching to the "Commit changes" tab, an error in an unrelated object (e.g. stored procedure referring to a non-existent column) causes SQL Source Control to fail with "An error occurred while creating a temporary database". The complete error message shows a stack dump, originating with the error in the script which has been run to create objects in the temporary database.
It would be much more helpful if SQL Source Control recognised that an error has occurred in the script and make the script available for viewing, similar to the way…
1 vote -
6 votes
-
Prevent user from committing other user's changes
One of the problems with a shared db model, where all developers work against the same database, is that everyone's changes are listed on the Commit List and any user can commit any other user's changes. It would be nice if an administrator setting could be set that would only allow users to commit their own changes There should be someway to prevent other users from committing your changes.
79 votes
Kendra
responded
An update for users on the status of this suggestion:
An ‘object locking’ feature was added to SQL Source Control following the creation of this item which can helps users working in a shared database environment not write over each other’s changes.
This may help prevent accidental commits in some cases, as there is a “Locking” tab which allows users to see which other users are working on specific items.
Locked items are still eligible to be committed, however, and there are cases where users will want to commit an item — perhaps to a specific branch in source control which is not ready to deploy — even if the item in the database is locked.
We have found at Redgate that the easiest way to enable alignment with distributed source control systems such as Git is to empower users to use dedicated development databases rather than shared databases. Tools…
-
Option to force check for invalid objects before committing
If invalid objects get committed to source control, often others cannot Get Latest until the object is corrected and re-committed. Having an option to check for invalid objects before allowing a commit to proceed would prevent invalid objects from getting into source control in the first place.
23 votes -
Allow user to disable dependant object refreshing
When getting latest SQL Source control always tries to refresh dependent objects. We have a scenario where we know we have broken objects (large database cleanup) and get latest fails because it tries to refresh those objects.
Add an option where users can skip that step. It currently generates code like below:
IF @@TRANCOUNT=0 BEGIN INSERT INTO #tmpErrors (Error) SELECT 1 BEGIN TRANSACTION END
GO
PRINT N'Refreshing [dbo].[vSomeView]'
GO
EXEC sprefreshview N'[dbo].[v_SomeView]'
GO5 votes
- Don't see your idea?