• Hi there Jeff.

    Very interesting story you have there. It wasn't that long, or my levels of interest went sky high when i started to read it.

    The need to buy new hardware is not because of the SQL Server performance per se. In fact, currently that's pretty good and people can do their job pretty fast.

    The problem of SQL Server is a by-product of the need to install new and better hardware to accomodate all the IT infrastructure (server and service wise) the company has and will have in the coming year.

    Then it comes my personal touch. I just love virtualization. I think it's a great way to use your hardware to the fullest and reduce ownership costs, but then it comes my real world approach that tells me that although virtualization is great it has some drawbacks that may jeopordize user experience and the whole project. Those drawbacks, to me and at this point, is IO usage. That's why i'm concerned about SQL Server performance under a virtualized environment. Because SQL Server is the life blood of the company. Our ERP is filled with functions, processes, operation and management maps. Everything that's related to the company's operation (logistics, production, HR, accounting and/or management) is litterally done on the ERP.

    To sum all up, i worried about SQL Server because i want to place (just until the company releases more funds to my department) every single service we run under the same bonet, if you know what i mean. That's why I state the need for more firepower. 🙂

    SQL wise, i myself have been dealing with it for the past 3 years. Maybe we could talk about query code design. I really need to know if i'm doing it by the book.

    Thanks a lot for your input. Really helpfull and insightfull.

    Regards.

    ____________________________________________________________

    If you can't do things right at the first time, don't try skydiving. I won't.