• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 216
  • Last Modified:

MS SQL 2005 on MS Windows Small Business Server 2003? Will it work?

Software installation seems to have caused a lot of problems with other programs. Our IT guy installed MS SQL Server 2005 on our version of MS Windows Small Business Server 2003. Now our email acts quirky, some email shows up late (1-3 months later) some software tries to reinstall itself when you try to run it. Our spam software (SpamBully) goes nuts and totally unlaods itself on some machines, ask to be registered multilpe times, does not retain the learning of email addresses for one day to the next.

We have been told that we need to upgrade our server to MS Windows Server 2005. My boss says that this sould not be happening. I also have been told that SQL 2005 should never have been loaded on our MS SB 2003.

Can anyone help before I lose it?
1 Solution
These are 2 total different problems.
Removing SQL 2005 is not going to solve it.
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Well, first, there is no Windows Server 2005.

Second, SQL 2005 will work just fine on an SBS and is, in fact, included in the Premium Version of SBS 2003 R2.  (The Workgroup Edition of SQL 2005).

If the IT guy installed a Standard version of SQL 2005 there are two problems:

1.  You overpaid for the licenses and/or may not be properly licensed because the SBS CALs don't cover that version.
2.  It most likely wasn't installed in a manner that took into account the nature of SBS and could easily be causing problems as you are experiencing.

The upgrade from SBS 2003 Standard SP1 to SBS 2003 Premium R2 runs about $1,000.00 ($299 for the upgrade from SP1/SP2 to R2 --- SKU T72-01415 and $699 for the upgrade from STANDARD to PREMIUM -- SKU T75-01256).

Premium version also includes ISA Server and R2 gives you WSUS as well.

The key factor in all of this though is to be sure that your server's hardware is sufficient.  You should have a MINIMUM of 2GB of RAM, Fast Hard Drives with plenty of room, and processor(s) that are designed to work on an SBS.


Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I might suggest that if it's your responsibility to manage this server that you get a better handle on where to find information and especially to get some training.  

The Hub of the SBS Community is a good place to start:  

This way you aren't relying on "I also have been told" to guide your decisions.

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

Jeff is completely correct,

To install SQL 2005 on SBS 2003, you need to follow the information on the Premium technology CD, it tells you step by step how to install it the right way.
maxdent01Author Commented:
First, I wanted to explain my reason for asking the question.
1)      The MS SQL 2005 was installed by the people that sold us our accounting package without notifying our IT as he was requested to do before he did anything.
2)      Our IT people are the one that said we could not put MS SQL 2005 on our MS SBS 2003.
Our system:
Terabyte Server
Supermicro CSE 743T-R760/B, 760W N+1 HSR
Superrnicro X6DHT-G, Dual Xeon, 2x GbE
3.OGHz Intel Xeon 800MGz W/ 1MB Cache
512MB DDR333 ECC Registered Memory
500GB Seagate Sata-II 7200RPM HDD
3Ware 9550SX-4LP, 4-Port Sata-II Raid (0,1,5)
Integrated Dual Intel 10/100/1000GbE
MS Windows 2003 SBS Standard SPacic

We have been having problems with our system ever since the MS SQL 2005 was installed. He thinks the MS SQL 2005 on the MS SBS 2003 is the problem and we need to update to MS Windows Server 2003 R2.
3)      My job is to be the liaison between our IT people and our staff. My questions are strictly trying to find out why things dont work like they are suppose to and also get me brownie points with my boss, if he thinks I might know something about the problems. My goal is not to try to run our network just know more about it. I schedule outages (work that needs to be done by the IT) or work that needs to be done (requests from our staff) on our system. My real job is the CAD Manager and Sr. Design Technician.

I will answer the replies one at a time. Although every time somebody's program, CPU, mouse or printer is not working I am called.
Vico1: That is what I thought also. The server software should be up dated.
TechSoEasy: (I am accepting your answer, by far the best)
a) Our IT person had said MS Windows Server 2003 with Microsoft Virtual Server 2005 R2. I just misunderstood him.
b) The IT person did not install the MS SQL 2005, which seems to be the crux of the problem.
c) I like the idea of the upgrade to SBS 2003 Premium R2, sounds a lot cheaper.
d) All of our software and hardware is less than 4 months old. That is why my boss is furious about putting more money in the system. Look at the list above, I think our hardware is sufficient for the task.
e)      I appreciate the info on the SBS Community. I need to know as much as possible about our system. Even it is to know we are not being told something wrong or in this case two sides that are very different.
NoSit: You are right

Thanks for the help,

Hardware looks fine only the ram could and I would say should be doubled at a minimum to handle exchange & SQL, I would recomend 2gb, the price of RAM is nothing.

Also if your IT guy said that SBS cant take SQL I would look for another IT guy. Dont mean to sound rude, but they should know that.
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I agree that you need to increase the amount of RAM on the Server.  That is most likely the primary cause of any problems you are seeing.  An SBS with SQL Server installed should have a minimum of 2GB RAM.  If SBS is running as a Virtual Machine on top of Virtual Server 2005 then you probably just need to allocate more memory to it.


Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now