|
Home > Archive > microsoft.public.cert.mcdba > March 2004 > index name conventions
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
index name conventions
|
|
|
| What are most common naming conventions for indexes:
-Clustered/non clustered, unique
etc
| |
| Ray Higdon 2004-03-09, 9:25 pm |
| I assume you are looking for index naming recommendations. I would create
them good enough to know what they are without having to look them up. Some
examples:
Clustered index on an IDENT column
CL_column_idx
Composite nonclustered index on column1 and column2
NC_COl1_COL2_IDX
and so on, table names are much more important as you will probably (or at
least should try not to) have to call indexes specifically by name.
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
---
"Moes" <anonymous@discussions.microsoft.com> wrote in message
news:98e001c405e1$89516590$a40
1280a@phx.gbl...
> What are most common naming conventions for indexes:
> -Clustered/non clustered, unique
>
> etc
| |
| Kael V. Dowdy 2004-03-11, 3:25 pm |
| "Ray Higdon" <sqlhigdon@nospam.yahoo.com> wrote in message news:<upWao1jBEHA.2476@TK2MSFTNGP12.phx.gbl>...[color=blue]
> I assume you are looking for index naming recommendations. I would create
> them good enough to know what they are without having to look them up. Some
> examples:
>
> Clustered index on an IDENT column
> CL_column_idx
>
> Composite nonclustered index on column1 and column2
> NC_COl1_COL2_IDX
>
> and so on, table names are much more important as you will probably (or at
> least should try not to) have to call indexes specifically by name.
>
> HTH
>
> --
> Ray Higdon MCSE, MCDBA, CCNA
> ---
> "Moes" <anonymous@discussions.microsoft.com> wrote in message
> news:98e001c405e1$89516590$a40
1280a@phx.gbl...
There are various guidelines and you may find some de facto standards
out there for that type of thing. Regardless of what you use, feel
free to define your own internal corporatet standard: keep it
consistent, simple, self-describing, and have all the developers
follow the rules.
Kael
|
|
|
|
|