User profile for ElliotRodriguez

Thanks for the clarification. That is interesting regarding the transaction limitation and role creation. We love the tool, we love the support we get too - but the object dependency issues we run into make it difficult sometimes. We appreciate the input. / comments

Thanks for the clarification. That is interesting regarding the transaction limitation and role creation. We love the tool, we love the support we get too - but the object dependency issues we run ...

0 votes

And now SQL Compare fails because the deployment script is STILL trying to execute the migration scripts on the database! And of course they fail because the script references objects that don't exist, which I can't get because the migration scripts are run FIRST. / comments

And now SQL Compare fails because the deployment script is STILL trying to execute the migration scripts on the database! And of course they fail because the script references objects that don't ex...

0 votes

I am using SQL Compare instead, and side note - I still do not understand why, if SQL Compare fails a deployment, Roles and Users are not part of a rolled back transaction. I received an error deploying from SQL Compare, because DTC was not running, and after I toggled it on and ran the same deployment script, I got another error complaining of a User that was already created. How can a failure not roll back the entire database to the same state it was in before the failure? This has been a long standing issue and I really wish it were addressed (or at least explained). / comments

I am using SQL Compare instead, and side note - I still do not understand why, if SQL Compare fails a deployment, Roles and Users are not part of a rolled back transaction. I received an error depl...

0 votes

Migration Script Failures

I intend to file a ticket for this, but I wonder if anyone has found a solution in the interim. I have a new database that I am connecting to SQL Source Control (dedicated database). The source con...

2 followers 5 comments 0 votes

Ignore option for database/server in synonyms not working

I am pulling new synonyms in from one source to another via SQL Source Control. We are not using Compare at this stage as its a promotion from DEV to our local TEST database. Although I have "Datab...

1 follower 1 comment 0 votes

I have submitted another support request for this issue. / comments

I have submitted another support request for this issue.

0 votes

So in implementing this a few things have become apparent. For one, the synonym must be named identically among all systems. For example, my local dev database would have a synonym (lets call it 'DBSynonym' which would point to the full local path to another separate database on the same local dev server (so it points to, say, 'elliotrodriguez.MyDatabase.MySchema.MyObject). CREATE DBSynonym FOR elliotrodriguez.MyDatabase.MySchema.MyObject This is fine, but I then have to instruct other developers to create their own local synonyms of the same name that point to their own local instances: CREATE DBSynonym FOR someotherdevdatabase.MyDatabase.MySchema.MyObject Then we have to tell SQL SC to ignore this using filters and thats where things fall apart. In the past I have complained about filter performance on our SQL Server 2008 R2 instances. They have seldom worked with SVN and have generally been a pain. For example, users can create a filter, but modifying it afterwards is completely ineffective and we end up having to unlink and relink the database from source control because even when we try to fix what is obviously broken, the filter never seems to update. Instead it always seems to exclude all objects for whatever reason. The same happened to us again using Mercurial. I tried to ignore the synonym using a filter, and the filter also managed to exclude the objects I modified that included the synonym (even though I explicitly selected just the synonym). And even after removing the filter rules, we could not access the modified objects until I unlinked and relinked. I can reproduce this reliably and have attached a video. We have had ongoing filter issues that have resulted in many tickets submitted, but we have never managed to get them working. Assuming the workflow I described is correct for this kind of situation, what do we have to do to get the filters working correctly? http://screencast.com/t/xL3X8U0P / comments

So in implementing this a few things have become apparent. For one, the synonym must be named identically among all systems. For example, my local dev database would have a synonym (lets call it 'D...

0 votes

Thanks Andrew - that is a great idea. / comments

Thanks Andrew - that is a great idea.

0 votes

Disabling comparisons for fully qualified database names

We have an environment where developers put development and test databases on a single server. We have a number of ways that development and test databases are set up right now. For example, if we ...

2 followers 5 comments 0 votes

I have a ticket submitted for this, but it appears that the portion of the script that creates the user is outside the transaction scope defined by Compare when it generates the script. / comments

I have a ticket submitted for this, but it appears that the portion of the script that creates the user is outside the transaction scope defined by Compare when it generates the script.

0 votes

How can we help you today?

ElliotRodriguez

Activity overview