Duplicate Definition Error

A SQL Server Management Studio add-in to source control your database in Subversion or Team Foundation Server.

Moderators: Chris Auckland, David Atkinson, sherr, PhilScrace, andy.campbell.smith

Red Gate Source Control duplicating CREATE TRIGGER

Postby rick@syncbak » Fri Jan 17, 2014 4:20 pm

I'm experiencing the same problem today. I tried to link and synch source control & got the infamous "A duplicate definition was found for trigger..." error. I went into the existing source control file, found the duplicate, removed it, & checked in. I then committed outstanding changes, & the duplicate reappeared, obviously fabricated by Red Gate Source Control. So I manually removed the dupe again.

Please fix this Red Gate!


SQL Source Control 3.5.4.332
SQL Server 2012
SSMS 11.0.3128.0
MDAC 6.3.9600.16384
Microsoft MSXML 3.0 6.0
.NET Framework 4.0.30319.34003
Windows 8.1 Pro (6.3.9600)
rick@syncbak
 
Posts: 2
Joined: Fri Jan 17, 2014 4:12 pm

Ditto - again today

Postby jsreynolds1 » Thu Mar 06, 2014 3:33 pm

I just started getting these same errors as well based on constraints.
jsreynolds1
 
Posts: 13
Joined: Fri Jun 14, 2013 9:03 pm

Postby andy.campbell.smith » Thu Mar 13, 2014 3:15 pm

Can you drop us an email at support@red-gate.com and quote the ticket number #14507? We'd be interested into looking into this problem in more detail to see if we can sort it out - thanks!
Andy Campbell Smith

Red Gate Technical Support Engineer
andy.campbell.smith
 
Posts: 173
Joined: Thu Oct 20, 2011 11:19 am
Location: Red Gate Software

Postby nhustak » Wed Apr 02, 2014 12:40 pm

Filed a support request - this problem really needs to get fixed. Been going on way too long.

A duplicate definition was found for the trigger [dbo].[trg_users_IDU]. Ensure that case sensitivity options are set correctly and all object creation scripts are valid. If the problem persists, contact our support.
nhustak
 
Posts: 40
Joined: Tue May 09, 2006 8:06 pm

Postby pk_davidson » Tue Aug 19, 2014 8:57 pm

Well, here I am on version 3.7.0.2 and this is still happening to me.

It is now only occurring on my test server and fortunately not on production but still it's so very annoying.

What's even more annoying, I deleted the triggers from the database completely. I suspect (HOPE) this is an error from an old issue that was never cleaned up?

I'm hoping one more dive into workingbases and I never see this again?
pk_davidson
 
Posts: 9
Joined: Tue Nov 06, 2012 5:39 pm

Previous

Return to SQL Source Control 3

Who is online

Users browsing this forum: No registered users and 0 guests