• RonKyle (8/1/2013)


    RonKyle (7/31/2013)

    --------------------------------------------------------------------------------

    Most would probably say it's overkill, but I prefix my OLTP databases with db, my staging areas with sa, and my OLAP database with dw. The names are otherwise short and clear.

    Why? What do you get out of it that a clear name doesn't give you?

    It allows reuse of the same name. All of the OLTPs have a corresponding staging area only for them. After the initial processes they are sent to centralized staging area so the data can be conformed across all incoming data. That final staging area and the OLAP data warehouse database also have the same same. So if I have two OLAP databases called CARS and FINANCE and my company name is KYLE, you would see the following database names.

    dbCARS, whose staging area is saCARS. The sa is a further indication that the database is NOT querable (per Kimball). dbFINANCE has saFINANCE. Both sa s feed into saKYLE, which conforms the data and in some cases puts data in 3NF where necessary. Finally the data feeds into dwKYLE.

    The dbs are not on the same server as the sa and dws but I think it makes it easier to see the flow, and on the OLAP server groups the databases nicely. I do have a dbETL on that server, which stores all the information about the ETL processes. As it has a db prefix, it is a querable OLTP database.

    I'll be honest, I'm confused. I mean if it works for you, great. But why not FinanceStaging or Cars (for the readable/OLTP) or KyleDataWarehouse. Those can be the same as what you have, but two things are done, the sorting is by the name of the database, not by type, and it's clear. Very little training is necessary to let people know what each thing does and you don't have to worry about accidently connecting to dwKYLE when you wanted dbKYLE since the second letter gets a little lost in there... Again, not trying to throw rocks or start a fight. I'm just a HUGE fan of clear and simple language in order to reduce friction and overhead so I advocate for it.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning