Ok, this is more of a general solicitation of opinions and in the world of SQL, programmers generally support and like what they use. I'm not as interested in responses around which is better.
I am looking for feedback (read, talk me out of it) on mixing MS SQL and MY SQL in a single application.
Background: we're cheap, we have an ERP/accounting system that runs MS SQL server express as its back end, the accounting system costs alot of money and has and will always use MS as its back end. The accounting data and web app data are pretty integrated. All that background to say, 2 gigs of accounting data and a business operating around it, so moving everything to MYSQL just isn't possible.
My situation: At the current pace, I am fine on the accounting functionality part of our system and won't bump into the express 10 gig limit. The problem? We're now adding more and more functionality into the web app. Functionality that is driving content. That rate of data growth is picking up speed. Alpha Anywhere will push it hard... I'll have some 10 field based service techs using tablets and iPhones for service reports and all kinds of field support of our equipment.
I started getting the feeling I was making code decisions based on my worry about the backend DB size.
So, that brings me to a decision. Regardless, by next year or at the latest the year after, I'll smack into the 10 gig limit on express.
My crazy notion has been: what about mixing MySql with my current DB? Where certain data is never shared with the accounting system (tables that aren't used in any way by the accounting system), put those tables in MySql?
Am I just asking for problems and have lost my senses or is this reasonable?
Is there Merit to this thinking or is it better to start mentally preparing that in the next year or so my wallet is going to get molested by Microsoft for 7k in server costs and sail past the 10 gigs?
I am looking for feedback (read, talk me out of it) on mixing MS SQL and MY SQL in a single application.
Background: we're cheap, we have an ERP/accounting system that runs MS SQL server express as its back end, the accounting system costs alot of money and has and will always use MS as its back end. The accounting data and web app data are pretty integrated. All that background to say, 2 gigs of accounting data and a business operating around it, so moving everything to MYSQL just isn't possible.
My situation: At the current pace, I am fine on the accounting functionality part of our system and won't bump into the express 10 gig limit. The problem? We're now adding more and more functionality into the web app. Functionality that is driving content. That rate of data growth is picking up speed. Alpha Anywhere will push it hard... I'll have some 10 field based service techs using tablets and iPhones for service reports and all kinds of field support of our equipment.
I started getting the feeling I was making code decisions based on my worry about the backend DB size.
So, that brings me to a decision. Regardless, by next year or at the latest the year after, I'll smack into the 10 gig limit on express.
My crazy notion has been: what about mixing MySql with my current DB? Where certain data is never shared with the accounting system (tables that aren't used in any way by the accounting system), put those tables in MySql?
Am I just asking for problems and have lost my senses or is this reasonable?
Is there Merit to this thinking or is it better to start mentally preparing that in the next year or so my wallet is going to get molested by Microsoft for 7k in server costs and sail past the 10 gigs?
Comment