• Repost - originally posted 1-06-2012

Poor object naming


The following is an example of a poorly named table from a major backup software vendor. This caused failures with the regular maintenance which was being run.

That table was called Media_Views.UpdateMaxCleaningCount.

Notice the period in the table name.

SQL Servers full object naming convention is servername.databasename.schemaname.objectname.

In this case the table actually had a period in the table name so it became a five part naming structure, which caused errors.

There are lots of resources for SQL Server naming conventions and best practices, most of them state not to have periods in object names.

Other poor object naming that we have come across include:

  • a table named ‘View’

  • a database named ‘Convert’

You should also avoid using reserved words when creating your database and objects within a database.


3 views0 comments

Recent Posts

See All

Standardise database sizes and automation

The default setting for the initial sizing of data and log files (and their autogrowth) is not adequate. I like to make sure that we set standard sizes for our data and log files - plus standard sizes

Migrating SSIS packages to AWS

We are currently migrating a large amount of SSIS packages (SQL Server 2008R2) to SQL Server 2016 at AWS. It has been a learning exercise to get these packages running. What we have learnt (so far) is

Autoclose and autoshrink - set them to off

By running a simple check of your database settings (use helpdb or query sys.databases) you may find databases that are set to autoclose and/or autoshrink. If so, you should change these settings as p