Although constraint names are of no consequence to a 'working'
database, they sometimes pose a problem when managing
databases.
So we try to keep control over het names of constraints.
Now we are changing the name of a table.
Should we alter al the constraintnames so that
the tablename in the constraintname reflects the
actual table, or should we leave the 'original' tablename.
Any thoughts about that ?
Is there an easy way to manage constraintnames, if the
database is implemented at several customers sites ?
Thanks for you attention,
ben brugmanAccording to the documentation, you should be able to rename a constraint us
ing sp_rename.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ben brugman" <ben@.niethier.nl> wrote in message news:eCo2wR%23pFHA.3160@.TK2MSFTNGP14.phx.gb
l...
> Although constraint names are of no consequence to a 'working'
> database, they sometimes pose a problem when managing
> databases.
> So we try to keep control over het names of constraints.
> Now we are changing the name of a table.
> Should we alter al the constraintnames so that
> the tablename in the constraintname reflects the
> actual table, or should we leave the 'original' tablename.
> Any thoughts about that ?
> Is there an easy way to manage constraintnames, if the
> database is implemented at several customers sites ?
> Thanks for you attention,
> ben brugman
>
Friday, February 10, 2012
Changing constraintnames.
Labels:
changing,
consequence,
constraint,
constraintnames,
database,
managingdatabases,
microsoft,
mysql,
names,
oracle,
pose,
server,
sql,
working
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment