52 results found
-
1 vote
-
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 -
hashbyte
if computed column contains a 'hashbytes' function call, the hashbytes will be surrounded by [], like [hashbytes] which causes an error. this bug exists since version 1.1. why did fix that!
3 votes -
Better importing of existing repositories
Thanks for the link!
I've done something similar to this before, but it takes a lot of time and you have to be very diligent. I'm not sure I'm going to go with this route, but just in case someone else is thinking about it, here is the general idea:
The idea is similar to the link above. You add your db to SQL Source Control (SSC), which creates a new repository/folder, then inspect the folder/file structure it created. You then take your preexisting repository and rename each file to match the same structure as the one created by SSC.…
2 votes -
Do NOT show SQL Source Control tab when starting SSMS
SQL Source Control tab should NOT be the DEFAULT on SSMS startup, Object Explorer Details should be the tab selected.
6 votesIf you close the SQL Source Control tab, then it will NOT show up the next time you start SSMS.
-
Allow Setup at the INSTANCE Level
Please consider allowing, in a single action, the addition of ALL (or a selection of) databases in a server to the same base VSS location. This would require you to create new projects under the root for each DB and simply auto-commit the changes. Currently, Initial setup on servers with dozens of DBs is quite daunting.
4 votes -
Adjust tab order on "Link to Source Control" Screen
The source control folder field currently tabs upward to the question mark next to "Type or paste the URL.....". It seems that it should tab to entry 1 under "development model"
1 vote -
source control folder structure should reflect that in ssms. in particular for indexes
source control folder structure should reflect that in ssms. in particular for indexes
1 vote -
Unable to load a project file after installation
After installation, I was no longer able to load a project file within SSMS. I also was unable to create new projects. My fix was to reinstall SQL Server 2008 R2.
1 vote -
Allow linking to system databases
I don't think this suggestion is here already, apologies if it is! I would like to be able to link system databases (esp master) to source control as my company has a number of shared procs here. The ability to optionally exclude the normal system procs when extracting would be really useful.
12 votes -
choose subfolders in subversion
When adding a database to source control, all kinds of subfolders as created(data,assemblies,...) but these folder are not finegrained enough. for instance we do it by schema first then we use the same kind of subfolders.
So if we have a Import and Base schema, then in subversion we have the procedure/functions folder under Import and under Base.It would be nice to be able to choose the folders themselves and also where to put a function and so on.. this gives more flexibility.
3 votes -
TFS integration should allow you to select which workspace to use
TFS integrations really needs you to specify which workspace you are working with. This does wrong right from the start - when I try to link a database to TFS, it asks for the source URI and data folder, but it will only accept data folders already checked in, not that I have created in my workspace.
6 votes
- Don't see your idea?