Comments
Sort by recent activity
I am altering tables that contain existing data that I would like to keep. Migration scripts are required for that I believe.
I am currently creating a custom migration script by using a SQL Compare script as a starting point; it doesn't complain about my sequences.
In fact SQL Compare seems perfectly happy with my sequences - it can sync changes to the sequences, the objects that depend on them or the custom type being used in the sequences fine.
It's only SQL Source Control that gets itself all worked up [image] [/code] / comments
I am altering tables that contain existing data that I would like to keep. Migration scripts are required for that I believe.
I am currently creating a custom migration script by using a SQL Compar...
Thanks for confirming the issue.
I guess I'll just ask my employer to cancel my SQL Toolbelt license in the "immediate term" shall I? [image] / comments
Thanks for confirming the issue.
I guess I'll just ask my employer to cancel my SQL Toolbelt license in the "immediate term" shall I?
Just a note that I am being forced to check in my sequences if I want to create a migration script, which then subsequently breaks sql source control completely.
So I cannot use the migration scripts feature at all, which is more serious. Previously I could add sequences to my filter and ignore them for source control, which was a sensible workaround. / comments
Just a note that I am being forced to check in my sequences if I want to create a migration script, which then subsequently breaks sql source control completely.
So I cannot use the migration scrip...
I can confirm that the issue (in both cases) seems to be the fact that the sequence has a custom type and not a built-in type.
Even though this is perfectly valid in SQL Server 2012, it is probably not supported by SQL Source Control?
This works:
CREATE SEQUENCE [dbo].[seq_EnvID] AS bigint
This doesn't:
CREATE SEQUENCE [dbo].[seq_EnvID] AS identifier
Can someone confirm this? And if it is an issue, is it something that will be fixed in the near future?
Thanks
Riko / comments
I can confirm that the issue (in both cases) seems to be the fact that the sequence has a custom type and not a built-in type.
Even though this is perfectly valid in SQL Server 2012, it is probably...
It is also worth noting that I was getting a "The given key was not present in the dictionary." error when linking my database to source control in shared database mode (but not in dedicated database mode).
This only happens after I add the sequences to source control. The error goes away again if I remove the sequences from source control, they are simply shown as "new objects" not yet checked in.
Please can you fix SQL Source Control for sequences? I am currently evaluating the product and cannot use it if it doesn't support sequences properly... after all it is almost 18 months since the SQL Server 2012 RTM... / comments
It is also worth noting that I was getting a "The given key was not present in the dictionary." error when linking my database to source control in shared database mode (but not in dedicated databa...