Brent Helms
Carlot.com
Return-Path: <[EMAIL PROTECTED]> Fri Apr 29 16:15:08 2005
Received: from smtp.imailbox.com [207.168.61.195] by mail31.safesecureweb.com with SMTP;
Fri, 29 Apr 2005 16:15:08 -0400
Received: from nospam.imailbox.com (unverified [207.168.61.211]) by imailbox.com
(Rockliffe SMTPRA 5.2.5) with SMTP id <[EMAIL PROTECTED]> for <[email protected]>;
Fri, 29 Apr 2005 15:23:48 -0500
Received: from mx10.imailbox.com ([207.168.61.213])
by nospam.imailbox.com (8.12.11/8.12.11) with ESMTP id j3TKHmYV020423
for <[email protected]>; Fri, 29 Apr 2005 15:17:48 -0500
Received: from medworking.com (mail.medworking.com [64.5.36.39])
by mx10.imailbox.com (Postfix) with ESMTP id 632F93D2
for <[email protected]>; Fri, 29 Apr 2005 18:47:05 -0500 (CDT)
Received: from planform2 [71.96.91.241] by medworking.com with ESMTP
(SMTPD32-8.15) id A32F480060; Fri, 29 Apr 2005 15:03:59 -0500
From: "Daniel Elmore" <[EMAIL PROTECTED]>
To: <[email protected]>
Subject: SPAM-LOW: RE: Transact SQL Question
Date: Fri, 29 Apr 2005 15:17:35 -0500
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_016D_01C54CCE.92F3EAC0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <[EMAIL PROTECTED]>
X-imailbox.com-MailScanner-Information: http://www.imailbox.com/support.cfm for more info...
X-imailbox.com-MailScanner: Found to be clean
X-MailScanner-From: [EMAIL PROTECTED]
Reply-To: [email protected]
Sender: [EMAIL PROTECTED]
X-SmarterMail-Spam: BAYESIAN FILTERING, SPF_None
X-Rcpt-To: <[EMAIL PROTECTED]>
Your wanting to create these foreign key constraits without checking the current keys in the table against their primary keys? If so, you need to use the WITH NOCHECK flag. However this is _not_ a recommend practice. If you later do an update to one of those rows, the constrait will fire and the update will fail.
- Daniel Elmore
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Brent Helms
Sent: Friday, April 29, 2005 3:00 PM
To: [email protected]
Subject: Transact SQL Question
I am having a tough time finding out how to manually write out the TSQL to generate a junction table that contains the following integrity constraint: "Check Existing Data On Connection".
This is what I have so far:
CREATE TABLE sec_ApplicationModuleAccess
(
ApplicationID INT NOT NULL,
ApplicationModuleID INT NOT NULL
CONSTRAINT sec_ApplicationModuleAccess_fk FOREIGN KEY (ApplicationID)
REFERENCES sec_Applications (ApplicationID),
CONSTRAINT sec_ApplicationModuleAccess_fk2 FOREIGN KEY (ApplicationModuleID)
REFERENCES sec_ApplicationModules (ApplicationModuleID),
CONSTRAINT sec_ApplicationModuleAccess_pk PRIMARY KEY CLUSTERED(ApplicationID,ApplicationModuleID)
)
The problem is: It does not set "Check Existing Data On Connection" to true (or checked). It does set "enforce relationship for replication, inserts, and updates to true.
Any ideas what the missing link is?
Regards,
Brent Helms
Carlot.com
