YeOldeStonecat
[H]F Junkie
- Joined
- Jul 19, 2004
- Messages
- 11,330
So had a preliminary meeting yesterday at one of my golf club/summer camp resort clients....a small club out on an island.
They've been running on Club Connect, which was a popular club management software. They're looking to add a new module to it which will interface with a new website that they'll be getting, customers of theirs can log into the main website...go through a portal, and view statements, and sign up for various events, schedules, etc.
This part has modest requirements, just some flavor of SQL, SQL Express is even supported. The servers needs to have .NET Frame 3.5, OK, no problem. IIS 6, OK..no problem. Static public IP, no problem...they can upgrade to that. So I'm thinking.."Cool...finally time to get SBS in there...SBS08 Premium will cover all that!"..and introduce some additional cool features to their 2x site organization. The minimum requirements list states Server 2003 and Server 2008.
And then they tell me that they'll be upgrading the accounting component of this product next year, to the new super version called ClubSelect. Now this accounting backend runs on Access..and old version. So the ClubSystems guys e-mails me the server requirements for the new ClubSelect package.
Server 2003, 32 bit only.
and SQL Standard 2005 only.
WTF, to comply with both of these products, I'm stuck using SBS03 Premium? Dang.
I'm half thinking about getting SBS 08 Premium....which up until this summer still comes bundled with SQL 2005 and a separate Server 2008 license. ESXi. Install 32 bit...but still be stuck with no vendor support for server 08. Ugh.
Gah, I'm just not wanting to roll out a brand new server with an 03 product on it...I have no upgrade path down the road.
Anyways, WTF with a software companies products being so different in requirements.
They've been running on Club Connect, which was a popular club management software. They're looking to add a new module to it which will interface with a new website that they'll be getting, customers of theirs can log into the main website...go through a portal, and view statements, and sign up for various events, schedules, etc.
This part has modest requirements, just some flavor of SQL, SQL Express is even supported. The servers needs to have .NET Frame 3.5, OK, no problem. IIS 6, OK..no problem. Static public IP, no problem...they can upgrade to that. So I'm thinking.."Cool...finally time to get SBS in there...SBS08 Premium will cover all that!"..and introduce some additional cool features to their 2x site organization. The minimum requirements list states Server 2003 and Server 2008.
And then they tell me that they'll be upgrading the accounting component of this product next year, to the new super version called ClubSelect. Now this accounting backend runs on Access..and old version. So the ClubSystems guys e-mails me the server requirements for the new ClubSelect package.
Server 2003, 32 bit only.
WTF, to comply with both of these products, I'm stuck using SBS03 Premium? Dang.
I'm half thinking about getting SBS 08 Premium....which up until this summer still comes bundled with SQL 2005 and a separate Server 2008 license. ESXi. Install 32 bit...but still be stuck with no vendor support for server 08. Ugh.
Gah, I'm just not wanting to roll out a brand new server with an 03 product on it...I have no upgrade path down the road.
Anyways, WTF with a software companies products being so different in requirements.