Comments
Sort by recent activity
The BAK files were indeed being generated daily, but always overwrite the contents of that folder and named, for example, "FIARPE.BAK" (we actually have three databases which we image/clone and all three exhibited the issue we're seeing). The images were created with the date suffixes in the image names.
The FIARPE_20171221.BAK instance was my hope that if we just renamed the source BAK file then we wouldn't see this problem.
We definitely confirmed that if we create an image from a particular BAK file, clone it to a server, and check its data that the data was not coming from the source BAK file. However, if we restored that same BAK file directly to a server, the data was indeed current.
Thanks, I'll send an email to support. / comments
The BAK files were indeed being generated daily, but always overwrite the contents of that folder and named, for example, "FIARPE.BAK" (we actually have three databases which we image/clone and all...
You could use the Powershell script above, augmented to write the data into the table of your choice in your SQL Server instance. Just a thought... / comments
You could use the Powershell script above, augmented to write the data into the table of your choice in your SQL Server instance. Just a thought...
We are also giving up on using SQL Source Control migration scripts.
Constantly running into issues with the scripts taking forever to construct in SQL Compare, if they get generated at all.
The most common inexplicable error is something about "2 conflicts prevent checkout" while generating a deployment script in SQL Compare.
We have made a heavy investment in time trying to troubleshoot issues with these scripts, all in the hope of one day automating our database deployments. But with so much manual intervention required in order to just get the scripts and their associated files to even be processed by SQL Compare, automation seems impossible.
Thanks,
Craig Eddy / comments
We are also giving up on using SQL Source Control migration scripts.
Constantly running into issues with the scripts taking forever to construct in SQL Compare, if they get generated at all.
The mo...
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...
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...
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
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
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...
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...