SQL Server Performance

Very Stubborn Developers

Discussion in 'General Developer Questions' started by Raulie, Jan 15, 2004.

  1. Raulie New Member

    I am working with some very stubborn developers. They insist they the database use Integer datatypes instead of bit for boolean values, one even said "why change it a number is a number" I brought up the point that we should use Bit since it saves storeage space, also They havent justified why we are going to use decimal instead of currency datatypes we are not going to need deep precision so why use it I think it will just generate more problems in the future i.e Overflow errors. Now for string datatypes they want to use char instead of varchar for columns that dont require a fixed size. I have already given them my suggestions but they dont want to make the changes, the project is almost ready to rollout, how can I pursuade some very stubborn developers?
  2. Luis Martin Moderator

    If you can find the way to convince developers, please let me know.

    You are right in all.


    Luis Martin

    ...Thus mathematics may be defined as the subject in which we never know what we are talking about, nor whether what we are saying is true.
    Bertrand Russell
  3. Twan New Member


    I guess the only thing I can think of is to make it clear to the developers (and their bosses) that you cannot be held responsible for poor database performance and increased cost of maintenance if the database is not designed properly in the first place.

    Making correct design decisions now is a much lower cost option than implementing them after going live.

    You could compare it to building a house. If you choose to build on quicksand then the end result is likely to be less than appealing...

    having said that, the only which would really concern me is the use of char rather than varchar. The others I wouldn't be too concerned about, unless you have lots of columns and/or lots of rows OR if there is a likelyhood that you will breach the currency min/max values

    Cheers
    Twan
  4. Negative New Member

    I can see them wanting to use integers instead bits and decimals instead of money datatypes if they are planning on transitioning this database to another platform sometime in the future, however the char/varchar argument makes absolutely no sense whatsoever unless they are wanting to move it to a mainframe or something. I don't really run into these problems as much in my shop, as the developers have, for the most part, learned SQL Server along with me (I am originally a developer), and I shared most of the knowledge I gained over that time with them.

    There have been a few unruly developers, most of whom are of the breed that believe that they are the best thing since sliced bread and know better than some stupid DBA, even though they have never used SQL Server before. After a few instances of me going back through and fixing problem databases however, people have started to get the idea that they should give serious consideration to my recommendations. Now if I could just silence the stupid claims that any problem they have is obviously SQL Server's fault, and Oracle, DB2, or MySQL (laugh) could do it better, I would be happy.
  5. Twan New Member

    &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br />Now if I could just silence the stupid claims that any problem they have is obviously SQL Server's fault, and Oracle, DB2, or MySQL (laugh) could do it better, I would be happy.<br />&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br /><br />asking for the impossible there I think <img src='/community/emoticons/emotion-5.gif' alt=';-)' /><br /><br />Cheers<br />Twan
  6. Raulie New Member

    I dont see the app moving to a different platform. But guess what, I just saw the new version of the script in source control and it was all changed, I guess they couldnt take critizism lightly, so they waited a day or two.

Share This Page