Best Practices / Considerations

  • Need to pick the minds of gurus here.

    What are the considerations / what determines that application A will go to SQL Server X while application B will go to SQL Server Y?

    Should there be a separation? What are the considerations involved for the separation?

    Thanks

    Noob

  • One thing I'd look at is integration points.

    If application A is using data from any application sitting on server Y, perhaps its database is best stored on server Y.


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    My thought question: Have you ever been told that your query runs too fast?

    My advice:
    INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
    The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

    Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
    Since random numbers are too important to be left to chance, let's generate some![/url]
    Learn to understand recursive CTEs by example.[/url]
    [url url=http://www.sqlservercentral.com/articles/St

  • Assuming you're monitoring your servers, you know that server X is under some stress for CPU and this new app looks like it might have lots of recompiles, so it goes on Server Y. You need to know what your servers are doing and what the apps are going to do. This involves monitoring the servers and testing the applications. Then use the numbers in hand to make decisions. Further, Server X is Enterprise and Server Y is not. Does your application need Enterprise only options? If so, it's going on Server X, if not, Server Y.

    "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

  • I always look at the technical aspects of the server where I plan to put the database, maybe one server has better hardware than another. If I know the performance metrics behind everything it helps to delve out space on the server that can handle the load.

  • Some of the considerations need to also be business rules. In addition to the business rules (like some security separation for instance), one needs to consider Vendor interference and how much you are willing to have vendor a intermingle with vendor b.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

Viewing 5 posts - 1 through 4 (of 4 total)

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