User profile for CraigEddy

Beautiful!! That solved the issue. Thanks so much for the quick reply! FYI, the TFS Build definition we are using is one we've been using for a year now without any (well, many [image] ) problems. We recently upgraded to SQL Source Control 5 partly to use the new migration scripts model but didn't realize we should change our TFS Build tasks. Other customers of yours may experience similar issues. Thanks again, Craig / comments

Beautiful!! That solved the issue. Thanks so much for the quick reply! FYI, the TFS Build definition we are using is one we've been using for a year now without any (well, many ) problems. We rece...

0 votes

We have many, many repeated table names arranged into different schemas. Each of these tables has an audit trigger named <schema>.Log<table> These are all producing "A duplicate definition was found for [].[Log<table>]." Note that the schema name is indeed an empty string in the error message, and I suspect that's the bug. [image] I have submitted the error through the application. Version 3.7.2.201 / comments

We have many, many repeated table names arranged into different schemas. Each of these tables has an audit trigger named <schema>.Log<table> These are all producing "A duplicate definition was foun...

0 votes

Thanks, Evan! I was also able to confirm that it works in the UI, just hadn't had the opportunity to update the thread yet. All the best, Craig / comments

Thanks, Evan! I was also able to confirm that it works in the UI, just hadn't had the opportunity to update the thread yet. All the best, Craig

0 votes

Thanks, Evan. If you're looking for beta testers for 11.0 (and hopefully it will be in our support contract!), just let me know. Craig / comments

Thanks, Evan. If you're looking for beta testers for 11.0 (and hopefully it will be in our support contract!), just let me know. Craig

0 votes

Chris Auckland wrote: I'm afraid this is a bug with the current version. The DropAndCreateInsteadOfAlter option doesn't seem to be observed from the command line when using source control data sources. I've logged this as bug SC-6317. I'm not sure of an exact timeframe for the fix, but I would guess it's likely to be around July. I couldn't find a workaround for this, apart from using the user interface where the option seems to behave correctly. I ran into this issue as well. It is causing us no end of grief at the moment. / comments

Chris Auckland wrote: I'm afraid this is a bug with the current version. The DropAndCreateInsteadOfAlter option doesn't seem to be observed from the command line when using source control data s...

0 votes

So I have encountered this issue again. I am using "Version 3.2.0.27 - March 13th, 2013" whose release notes specifically mention that this issue was fixed. However, I encountered it again when I edited a table that has a trigger: inserting a column into the middle of the column list. It seems to have to do with the affected tables also being in a migration script. I ended up having to delete the triggers AND the migration script before I could successfully sync my database to source control. / comments

So I have encountered this issue again. I am using "Version 3.2.0.27 - March 13th, 2013" whose release notes specifically mention that this issue was fixed. However, I encountered it again when I e...

0 votes

Didn't exactly work for me because the migration script seemed to have gotten "disconnected" from the object: when another user did a get-latest on the table it didn't pull the migration script, and the table's schema change failed. The migration script included SQL INSERT statements to properly populate the temporary table created with the new NOT NULL columns I added. I guess because of the manual edit I performed on the .SQL file for the table (in TFS). Bummer. / comments

Didn't exactly work for me because the migration script seemed to have gotten "disconnected" from the object: when another user did a get-latest on the table it didn't pull the migration script, an...

0 votes

adriancearnau wrote: I think I can replicate this problem easily. Every time I reorder the columns in a table with triggers and then commit a migration script with the modifications, the table definition SQL file gets modified and includes the same triggers twice. If there are also trigger modifications caught in the migration script, the table definition file ends up containing both the previous and the current trigger definitions. This is quite a nasty regression, I haven't had this problem in previous versions of SQL Source Control. Any idea where I could report this bug properly? By the way, thanks a lot for the Ctrl+Shift tip, didn't know I can access the working base folder like that, always had to rummage through AppData before. Exact same problem here. Table with a trigger, added two fields, modified the trigger, and used a migration script to encapsulate the changes. The issue isn't a SQL script error, it's an error in the processor that's creating the script. I suspect it's actually a SQL Compare issue... / comments

adriancearnau wrote: I think I can replicate this problem easily. Every time I reorder the columns in a table with triggers and then commit a migration script with the modifications, the table d...

0 votes

Here is what I did to get my environment back to a usable state: 1) After committing the change (mine was via a migration script), I went into the WorkingBases folder, found the modified table file (sort by date is easiest), made it not Read-only, edited the file to remove the extra trigger definition. Save the file. 2) Manually check out and perform the same edit on the file in actual TFS Tables folder. Check in this change. 3) In SQL Source Control, un-link my database. Ignore any errors that occur ("folder is not empty"). Close SSMS. 4) Re-open SSMS and link the database again. / comments

Here is what I did to get my environment back to a usable state: 1) After committing the change (mine was via a migration script), I went into the WorkingBases folder, found the modified table file...

0 votes

This seems related to an issue I'm having with restoring from a database which is essentially a copy of the database I used to perform the initial commit, but which doesn't have any SQL Source Cont...

0 votes

How can we help you today?

CraigEddy

Comments