![[Deleted User]](https://assets.zendesk.com/hc/assets/default_avatar.png){kind=avatar}
Activity overview
Latest activity by [Deleted User]
Hi Rick,
If I understand correctly, this error is probably happening because the assembly has been excluded. Then you would get this error if an object that depends on that assembly (such as a stored procedure or user-defined function) was being applied to the database without the underlying assembly. / comments
Hi Rick,
If I understand correctly, this error is probably happening because the assembly has been excluded. Then you would get this error if an object that depends on that assembly (such as a stor...
Hello,
Sorry this is not straightforward, and depends on what is being compared. If it's a live datasource, this should not happen as SQL Server does not allow two objects of any type with the same name. In that case, possibly the database is corrupt.
With scripts folders, you can use MS-DOS findstr (findstr /S /I /C:"object name" *.*) The reason this happens is usually CI-related - either someone has put a scripts folder as a subfolder of a scripts folder, put "migrations" scripts inside the scripts folder, or specified two VCS roots containing scripts, which then combine into the same folder. / comments
Hello,
Sorry this is not straightforward, and depends on what is being compared. If it's a live datasource, this should not happen as SQL Server does not allow two objects of any type with the same...
Thanks for following up! It is easy to get caught out when moving projects to a build server. I'm glad it's sorted out. / comments
Thanks for following up! It is easy to get caught out when moving projects to a build server. I'm glad it's sorted out.
I could not reproduce your issue in SQL Compare version 10.7. Creating the database as below and then mapping SCHEMAA to SCHEMAB and vice-versa creates a comparison where SCHEMAA.Table1 is compared to SCHEMAB.Table1 and vice-versa.
The only thing I noticed is that if the tables are different for a reason other than the table name, the SQL view highlights the name as a difference. So for example the code below creates a system-generated primary key and that is the reason they show up in the different objects list of the results. If you then use the option to ignore the names on constraints, then the tables are shown as equal.
It's the SQL view windows that are broken, but this does not affect the actual result.
If this is your issue, please let me know.
CREATE SCHEMA SchemaA AUTHORIZATION dbo;
GO
CREATE SCHEMA SchemaB AUTHORIZATION dbo;
GO
CREATE TABLE SchemaA.Table1(
ID int PRIMARY KEY,
DATA nvarchar(50)
)
GO
CREATE TABLE SchemaB.Table1(
ID int PRIMARY KEY,
DATA nvarchar(50)
)
GO
/ comments
I could not reproduce your issue in SQL Compare version 10.7. Creating the database as below and then mapping SCHEMAA to SCHEMAB and vice-versa creates a comparison where SCHEMAA.Table1 is compared...
Hi Luke,
We were never able to isolate the root cause. What one customer suggested (although the same error appeared in a different product) was to copy the extracted files to a "trusted" folder (ie on the desktop) and run it from there.
If you run the installer and click the icon in the titlebar, you can select "show temporary files". Copy the entire folder to the desktop and double-click the .msi file inside. Hopefully that works. / comments
Hi Luke,
We were never able to isolate the root cause. What one customer suggested (although the same error appeared in a different product) was to copy the extracted files to a "trusted" folder (i...
There should be an X in the upper-right-hand corner. If there isn't, let me know the topic title and I'll do it.
If you think the solution could be useful to someone else, you can leave it there! / comments
There should be an X in the upper-right-hand corner. If there isn't, let me know the topic title and I'll do it.
If you think the solution could be useful to someone else, you can leave it there!
Hello,
SQL Monitor does not disable the 1204 trace flag if you suppress the alerts for deadlocks, but you can disable the trace flag by reconfiguring SQL Monitor:
First, locate the configuration file on the machine where the SQL Monitor Base Monitor service is hosted.
Location: C:\ProgramData\Red Gate\SQL Monitor 3
File Name: RedGate.Response.Engine.Alerting.Base.Service.exe.settings.config
Make a copy of this file and name it something useful like RedGate.Response.Engine.Alerting.Base.Service.exe.settings.config_old
This will act as a backup of the configuration file so that your changes can be reversed.
Download and run the SQL Monitor Configuration Editor ftp://support.red-gate.com/patches/SQL_ ... Editor.zip
You will be prompted to "Load a configuration file". Find the .config detailed in step 1.
You will be presented with a list of all the configuration options available. These relate to each item in the polling schedule. Any check box which is un-checked automatically uses the default. Simply locate in the list "[Cluster].[SqlServer].[DeadlockTraceFlag]" and select "Disabled" from the drop down menu which appears.
Once complete, click "Save Changes" and restart the SQL Monitor Base Monitor service. If you have any unexpected results then please delete your edited configuration file and rename the copy (then also restart the service).
/ comments
Hello,
SQL Monitor does not disable the 1204 trace flag if you suppress the alerts for deadlocks, but you can disable the trace flag by reconfiguring SQL Monitor:
First, locate the configuration f...
The /include:StaticData argument takes the tables it will modify from the RedGateDatabaseInfo.xml file. If you compare form a static script, you can try first modifying that file and putting the tables whose data you want to sync in the DataFileSet element. / comments
The /include:StaticData argument takes the tables it will modify from the RedGateDatabaseInfo.xml file. If you compare form a static script, you can try first modifying that file and putting the ta...