Error Number 3726
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: can not drop table ....Error: 3726 SQL Server > Getting started with SQL Server Question 0 Sign in to vote TITLE: Microsoft SQL Server Management Studio ------------------------------ Drop failed for Table 'dbo.table1'. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.0.4000.0+((Katmai_PCU_Main).100916-1939+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Drop+Table&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) ------------------------------ Could not drop object 'dbo.table1' because it is referenced by a FOREIGN KEY constraint. (Microsoft SQL Server, Error: 3726) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.00.4000&EvtSrc=MSSQLServer&EvtID=3726&LinkId=20476 ------------------------------ BUTTONS: OK ------------------------------Harry Friday, September 09, 2011 9:02 PM Reply | Quote Answers 1 Sign in to vote Hi Try code below to check Constraint: SELECT OBJECT_NAME(OBJECT_ID) AS Name_of_Constraint, SCHEMA_NAME(schema_id) AS SchemaName, OBJECT_NAME(parent_object_id) AS TableNameX, type_desc AS ConstraintType FROM sys.objects WHERE type_desc LIKE '%CONSTRAINT' and OBJECT_NAME(parent_object_id)='yourTable' To DROP: ALTERTABLE yourTable
DROPCONSTRAINT
I Use? SQL Saturday #62 - Tampa, FL 2011 2010 - The Grateful DBA Year in Review Archives Archives Select Month October 2015 (1) March 2012 (1) February 2011 (1) January 2011 (1) December 2010 (2) November 2010 (4) October 2010 (2) August 2010 (1) July 2010 (1) April 2010 (2) March 2010 (2) February 2010 (3) January 2010 (2) December 2009 (3) November 2009 (2) Categories Backups (2) Beatles (1) Best Practices (2) Branding (1) DMV's (1) Full Text Indexing (1) Funny Stuff (2) Grateful Dead (2) Index Tuning (3) Life (3) Musings (2) https://social.msdn.microsoft.com/Forums/sqlserver/en-US/cccfa48b-a294-4d1b-83f9-e92c4e9622f1/can-not-drop-table-error-3726?forum=sqlgetstarted Office (1) Performance Tuning (1) Replication (2) Speaking (4) SSMS (5) T-SQL (6) Transaction Log (1) My Favorite SQL Blogs Benchmark IT Brent Ozar Carpe Datum In Recovery… Jeremiah Peschka SQL Authority - Pinal Dave SQL Awsomesauce SQL Fool SQL Rockstar SQLAgentMan The Midnight DBA The SQL Update Statement IDs Twitter: "GratefulDBA" Yahoo: "Ooogaleee1" Meta Log in Entries RSS Comments RSS WordPress.org SQL Server Replication Error http://troygallant.com/?p=81 3726 December 3rd, 2009 by The Grateful DBA Ok, I know "SQL Server Replication Error 3726" isn't the most imaginative of headlines for a blog article. What little I know about SEO tells me that titles carry more weight when the search engines do their crawls. So, I had to make the decision that this particular title may not actually bring sexy back. I can live with that. Error 3726: "Could not drop object ‘myTable' because it is referenced by a FOREIGN KEY constraint." This is thrown predominantly upon the initial setup of a replication publication. When the snapshot agent is run, one of the first things that is done is the engine verifying whether the articles already exist at the subscriber. If so, one has a choice of either dropping the article entirely (schema included), just deleting the data (closer to a TRUNCATE than a delete because I'm fairly sure it's not logged), filter based on predetermined criteria, or simply doing nothing. Whichever of the options you choose; if an article you wish to publish has a foreign key constraint that ties it to an object on the publisher that is not published as we
DriverDoc WinSweeper SupersonicPC FileViewPro About Support Contact Errors Troubleshooting › Runtime Errors › Microsoft Corporation › Microsoft Access › Error 3726 How To Fix Microsoft http://www.solvusoft.com/en/errors/runtime-errors/microsoft-corporation/microsoft-access/3726-microsoft-access-error-3726/ Access Error 3726 Error Number: Error 3726 Error Name:Microsoft Access Error 3726 Error Description: Invalid SQL syntax - expected token: NULL. Developer:Microsoft Corporation Software:Microsoft Access Applies to:Windows XP, Vista, 7, 8 Download NowWinThruster 2015 - Scan your PC for computer errors. Compatible with Windows 10, 8, 7, Vista, XP and 2000 Symptoms error number of Error 3726 "Error 3726" appears and crashes the active program window. Your PC frequently crashes with Error 3726 when running the same program. “Microsoft Access Error 3726” is displayed. Windows runs sluggishly and responds slowly to mouse or keyboard input. Your computer periodically “freezes” for a few seconds at a time. error number 3726 These 3726 error messages can appear during program installation, while a Microsoft Corporation-related software program (eg. Microsoft Access) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your 3726 error occurs is a critical piece of information in troubleshooting the problem. Causes of Error 3726 Corrupt download or incomplete installation of Microsoft Access software. Corruption in Windows registry from a recent Microsoft Access-related software change (install or uninstall). Virus or malware infection that has corrupted Windows system files or Microsoft Access-related program files. Another program maliciously or mistakenly deleted Microsoft Access-related files. Runtime Errors such as “Error 3726” can be caused by a variety of factors, so it is important that you troubleshoot each of the possible causes to prevent it from recurring. Runtime Errors Knowledgebase Article ID: 126385 Article Author: Jay Geater Last Updated: 20-08-2016 Popularity: star rating