officeroamer
Programmer
I was hired last year rewrite the companies 7 year old software. The company produces custom (built to each patient) product. I know they have systems in a few countries and have a great international business.
When I was hired my primary goal was to tear apart the old software and learn the algorithms that it used.
Once I learned the algorithms I worked with the different departments to see how they used the system and what updates that were needed.
In February we got a blade system in and I started testing the new software I wrote with the new scanners that they developed.
In April they upgraded some of there larger clients to the new scanners and saw a 30% increase in sales, fewer software issues, fewer “fit” issues, and the customer service representatives love working with the software.
In June the company got in 800 scanners and fast tracked upgrading there current clients. 400 of the units were going to be saved to try to move us into a different market, but they upgraded around 750 clients.
At the end of June the new system started lagging and we added a third blade into the cluster. At this point the system was handing about 40% more orders than it was planed to handle at that time.
In the next few weeks the will receive a shipment of 500 units of hardware that they plan on using to upgrade most of there international clients. From what the rummer is they have 2,500 more units on order and they will be coming in over the next 6 months.
It's rather obvious to me that the SQL back bone will not be able to handle the expected loads in the next 3 months. The IT manager has spent most of his budget on the new scanners and trying to phase out the old ones so he can get ride of the old system. I tried talking to him about the SQL servers and the amount of data they can handle, but he says they can handle the load.
At what point is it right to go over my bosses head?
Who do you go to (owner, president, or someone else)?
I know I'm not the smartest with SQL is there a way to get an idea on how much more the servers can handle?
When I was hired my primary goal was to tear apart the old software and learn the algorithms that it used.
Once I learned the algorithms I worked with the different departments to see how they used the system and what updates that were needed.
In February we got a blade system in and I started testing the new software I wrote with the new scanners that they developed.
In April they upgraded some of there larger clients to the new scanners and saw a 30% increase in sales, fewer software issues, fewer “fit” issues, and the customer service representatives love working with the software.
In June the company got in 800 scanners and fast tracked upgrading there current clients. 400 of the units were going to be saved to try to move us into a different market, but they upgraded around 750 clients.
At the end of June the new system started lagging and we added a third blade into the cluster. At this point the system was handing about 40% more orders than it was planed to handle at that time.
In the next few weeks the will receive a shipment of 500 units of hardware that they plan on using to upgrade most of there international clients. From what the rummer is they have 2,500 more units on order and they will be coming in over the next 6 months.
It's rather obvious to me that the SQL back bone will not be able to handle the expected loads in the next 3 months. The IT manager has spent most of his budget on the new scanners and trying to phase out the old ones so he can get ride of the old system. I tried talking to him about the SQL servers and the amount of data they can handle, but he says they can handle the load.
At what point is it right to go over my bosses head?
Who do you go to (owner, president, or someone else)?
I know I'm not the smartest with SQL is there a way to get an idea on how much more the servers can handle?