User profile for ToddHarry

Just a quick update: Since I didn't receive any community feedback, nor response from Red Gate to my submissions using the in-app error reporting, our team started experimenting to figure out how to work around this issue. We found we could recreate the issue 100% of the time any time the source environment for the compare had a normal user-defined table (dbo.{whatever}) that has a column with a Foreign Key referencing the stream_id" column of a FileTable. Here's how we worked around it: Normally when we push code, we use three scripts: a SQL Compare-produced 2nd script for producing the "meat" portion ("Deployment") of our code pushes, sandwiched between two additional scripts we use for data transformation (a "PreDeployment" script we run first, and a "PostDeployment" script we run third, ala SSDT-style.) So, we dropped the Foreign Key in our Source database, so SQL Compare could be used to generate the 2nd script (no FK, no error). And then we added the FK back in the Post-Deploy. The thought is, when we go to push code between server A and B next time, the FK will be there in both tables, and so SQL Compare won't stumble on it when trying to calculate the dependencies to produce the deploy script. Note that we were able to recreate this regardless of whether or not we had "Deploy all dependencies (recommended)" checked in the Deployment wizard. Hope this helps someone.... we don't often have FK's to FileTable columns (this is a first for us, in a project with 100's of tables and views, and several 100's of stored procs), so I don't see us having to remember this workaround for long, or use it often... but I do hope that this issue gets resolved in the next release of SQL Compare or two so we don't have to work around the issue. [image] Post back if anyone has any questions or concerns. Thanks. Todd M. Harry / comments

Just a quick update: Since I didn't receive any community feedback, nor response from Red Gate to my submissions using the in-app error reporting, our team started experimenting to figure out how t...

0 votes

Error deploying "Unexpectedly Failed to locate the field..."

Morning all: I'm running into an error with SQL Compare trying to deploy a stored procedure change from one DB to another. In trying to move proc "A" from server "A" to server "B", I get an error a...

1 follower 1 comment 0 votes

SQL Compare: Ignore Comment/Whitespace codependent

Redgate: I think I found a bug when I compare a View between two databases, and the only difference in them is the comments, SQL Compare shows the View in the "identical objects" group even when th...

1 follower 1 comment 0 votes

How can we help you today?

ToddHarry

Activity overview