Post reply

Application Standards.

  • May 24, 2007 at 3:45 pm

    #62658

    Can anyone please let me know of any links that describes about application standards for database objects when they are created? For ex when tables, views, indexes, constraints or st.procs are created. I am trying to get a document ready and any inputs /ideas will be greatly appreciated.

    TIA

  • May 24, 2007 at 11:30 pm

    #708854

    I can only tell you what I use and this is from a DBA point of view - please see check-points below. About when to create objects, I'm affraid there must be an internal standard created based on the business needs/project milestones. SQL 2000 does not have the built-in functionality to keep track of the DDL modifications, you need to create your own procedures (for eg fncts, sps). With sql 2005 it's much easier = DDL database triggers.

    Transact-SQL Checklist

    Does the Transact-SQL code return more data than needed?

    Are cursors being used when they don't need to be?

    Are UNION and UNION SELECT properly used?

    Is SELECT DISTINCT being used properly?

    Is the WHERE clause sargable?

    Are temp tables being used when they don't need to be?

    Are hints being properly used in queries?

    Are views unnecessarily being used?

    Are stored procedures being used whenever possible?

    Inside stored procedures, is SET NOCOUNT ON being used?

    Do any of your stored procedures start with sp_?

    Are all stored procedures owned by DBO, and referred to in the form of databaseowner.objectname?

    Are you using constraints or triggers for referential integrity?

    Are transactions being kept as short as possible?

    Application Checklist

    Is the application using stored procedures, strings of Transact-SQL code, or using an object model, like ADO, to communicate with SQL Server?

    What method is the application using to communicate with SQL Server: DB-LIB, DAO, RDO, ADO, .NET?

    Is the application using ODBC or OLE DB to communication with SQL Server?

    Is the application taking advantage of connection pooling?

    Is the application properly opening, reusing, and closing connections?

    Is the Transact-SQL code being sent to SQL Server optimized for SQL Server, or is it generic SQL?

    Does the application return more data from SQL Server than it needs?

    Does the application keep transactions open when the user is modifying data?

  • May 25, 2007 at 8:58 am

    #708996

    Search naming standards on this site and you'll find a few references as well for helping with that.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply