Never mind...I was not thinking, just delete it.
Douglas Brown
Email: [EMAIL PROTECTED]
- Original Message -
From: "Bud" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Saturday, June 29, 2002 4:54 PM
Subject: OT: SQL Server Indexes
> Hi all. I've noticed when upsizing an
Bud,
It depends on if the category_id is a field that is searched alot. If that is
the case, you might as well leave that index as it will help performance. If
not, then deleting it will harm nothing...
Douglas Brown
Email: [EMAIL PROTECTED]
- Original Message -
From: "Bud" <[EMAIL P
Yes. Duplicate indexes are not needed.
> -Original Message-
> From: Bud [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, June 29, 2002 5:55 PM
> To: CF-Talk
> Subject: OT: SQL Server Indexes
>
>
> Hi all. I've noticed when upsizing an Access database, I'll get
> duplicate indexes on the p
ge-
From: DeVoil, Nick [mailto:[EMAIL PROTECTED]]
Sent: 02 February 2001 11:21
To: CF-Talk
Subject: RE: SQL Server Indexes and System Objects
> But I only want to INDEX one - that's not altering the system (if it's not
a
clustered index)
Philip,
Although the system catalogs can be
> Although the system catalogs can be referred to in SQL
> statements as if they were normal tables, they aren't
> necessarily stored or managed in the same way as normal
> tables internally by the DBMS. So a command like CREATE
> INDEX quite possibly wouldn't work even if it was allowed.
Damn, I
> But I only want to INDEX one - that's not altering the system (if it's not
a
clustered index)
Philip,
Although the system catalogs can be referred to in SQL
statements as if they were normal tables, they aren't
necessarily stored or managed in the same way as normal
tables internally by the DB
> from the BoL:
> Note
> System tables should not be altered directly by any user. For example,
> do not attempt to modify system tables with DELETE, UPDATE, or
> INSERT statements, or user-defined triggers.
But I only want to INDEX one - that's not altering the system (if it's not a
clustered in
Thanks Paul - at least I know to give up now!
I just figured it would be nice to do change control on the database
definitions, because obviously things can get nasty if they get out of sync with
your production server.
Heard anything that might help in that regard?
David Cummins
Paul Hastings
> Obviously its potentially dangerous - but I don't like the MS policy of
taking
> your toys away because somebody else wasn't playing nice with them.
well these change from version to version & building apps based
on them is going to get your butt kicked sooner or later, also some
of these cata
Obviously its potentially dangerous - but I don't like the MS policy of taking
your toys away because somebody else wasn't playing nice with them.
So as far as you're aware, its not possible? Not even to add triggers etc?
David Cummins
Paul Hastings wrote:
>
> > I too have wondered how one can
> I too have wondered how one can alter system tables - what I wanted to do
was
> add a trigger to the system tables to audit changes to the database
structure...
> however I was not able to, even though I was using the sa login.
monkeying about with your system tables is a disaster waiting to
ha
I too have wondered how one can alter system tables - what I wanted to do was
add a trigger to the system tables to audit changes to the database structure...
however I was not able to, even though I was using the sa login.
David Cummins
Philip Arnold - ASP wrote:
>
> This might be a dumb quest
12 matches
Mail list logo
