Post reply

SQL Server -- under the covers

  • February 8, 2010 at 11:19 am

    #141093

    As a DBA I accept all kinds of things. For example, a field declared as varchar (100) will generally use less space than one defined as char(100). Assuming, of course, the data comes in a variety of lengths. This is what I was taught. But are there any tools -- outside of Microsoft -- that would let me verify this fact? There is something deeply unsatisfying to me about accepting facts without verification.

    If a .NET developer has a data-related issue, they can single-step in their code to the offending line and view the data in hexadecimal to get the lowdown. While I am not comparing these two cases I am pointing out that developers have a much richer toolset to play with and it seemingly provides greater insight into their area of expertise.

    I could go on and on about Sql tools not providing the insight I need when things go wrong (ever had a trans log issue?) but you get the idea. How do you deal with this issue?

    TIA,

    barkigndog

  • February 8, 2010 at 12:07 pm

    #1115715

    Barkingdog (2/8/2010)[hrFor example, a field declared as varchar (100) will generally use less space than one defined as char(100). Assuming, of course, the data comes in a variety of lengths. This is what I was taught. But are there any tools -- outside of Microsoft -- that would let me verify this fact?

    Sure, absolutely trivial to prove. sp_spaceused (to view the size of a table, assuming you have two tables, one with a char column, one with a varchar column and the same no of rows) right down to DBCC PAGE (to view the raw database page)

    (ever had a trans log issue?)

    I assume you mean log full? 2000 was a pain with those, with the improved system views in 2005 it's a lot easier. A combination of sys.databases and DBCC OPENTRAN usually narrows things down sufficiently.

    Yes, we have fewer tools than devs do, however I usually find that the problem is that people don't know where to find the built-in tools that we do have.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • February 8, 2010 at 7:21 pm

    #1115891

    Good point!

    Barkingdog

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

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