Re: New to SQL server

dude what about when you need to split your backend into multiple files
because you get a single table that is approaching 1gb?

ROFL

and for the record.. this:

CREATE TABLE OrgChart (
employeeID INTEGER NOT NULL UNIQUE,
manager_employeeID INTEGER
REFERENCES OrgChart (employeeID)
ON DELETE SET NULL
ON UPDATE CASCADE);

wouldn't work in SQL Server since I don't have a table named OrgChart

how about this.. Right-Click CREATE SCRIPT for all your MDB tables and
queries LoL

Eat a *** lamer; Jet is a DISEASE.
ADP killed you dipshits off a long time ago.

-Aaron



onedaywhen wrote:
On Nov 29, 4:15 pm, "aaron.ke...@xxxxxxxxx" <aaron.ke...@xxxxxxxxx>
wrote:
i disagree with this:

Engine-level referential integrity and datavalidation. Microsoft
Jet has built-in support for primary and foreign keys,
database-specific rules, and cascading updates and deletes.

RI is not practical in MDB in any way shape or form.

I think DRI is better implemented in Jet 4.0 than SQL Server.

Try the following in SQL Server 2005 (or change SET NULL to NO ACTION -
how apt <g> - for SQL Server 2000), which works fine in Jet 4.0:

CREATE TABLE OrgChart (
employeeID INTEGER NOT NULL UNIQUE,
manager_employeeID INTEGER
REFERENCES OrgChart (employeeID)
ON DELETE SET NULL
ON UPDATE CASCADE);

SQL Server chokes with the error, "Introducing FOREIGN KEY constraint
'self_referencing_fk' on table 'OrgChart' may cause cycles or multiple
cascade paths..." Erm, no, it will not: apparently SQL Server can't
count to two <vbg>! This still applies to SQL Server 2005 - what's
that, nine years after it was implemented in Jet?

Jamie.

--

.

Loading