I just
read that SP2 is not compatible with SQL Sever 2000.
Our company just bought a Dell PowerEdge 2600 server with 2003 Small Business Server with SQL 2000 (I
believe it is SQL 2000). What would you guys suggest I do? Do I
indefinitely not apply the new service pack? At some point is Microsoft going to release a patch or must I upgrade? We bought the 2003 SBS, because we cannot afford the full blown
licensing for Server 2003 and SQL.
I hope this post comes out right there is not preview utility to check my posts.
-VBJB
-
Microsoft has warned its customer base that SQL Server 2000, Microsoft CRM 1.2 and a few other Microsoft applications are not currently compatible with SP2.
-
Windows XP SP2 is intended for the clients (desktops and laptops) on your network at your workplace. Yes, Small Biz Server has SQL 2000, buying a Dell was a big mistake so don’t go blaming Microsoft for all the problems you WILL be having.
-
Yes, buying a Dell was a big mistake... Where's that "I'm rolling my eyes" emoticon?
My understanding of the issue is that SQL2K will not work on an XPSP2 desktop. As such, the fact that you have SQL2K installed on your server shouldn't matter.
CRM's another issue entirely, and a fix is apparently coming up in September.
-
Thanks for the joyful news <grin>. So the clients should have no problem updating the server?
ahh! Jeremy W answered it before my post.
Thanks -
Now that you got my interests….Since you guys are decidedly against a Dell server what servers do you prefer?
Also what about MSDE SP3 wil that work on a client with SP2? -
Have a look at this FAQ concerning SQLServer 2000 and XP SP2:
http://www.microsoft.com/sql/techinfo/administration/2000/security/winxpsp2faq.asp
-
I build Servers with better motherboards and memory then was ever seen on a Dell. Support your locial System Builder (or email me).
Small Business Server is a great value for a small business, have you looked into SharePoint?
-
eagle wrote:
.... have you looked into SharePoint?
I read about it in the manual....Now I am an expert, Have any questions?
Realistically, I know very little about it, any suggestion on using it? -
I maintain nearly 500 Dell servers single-handedly. The hardware is very good. Out of the last 100 servers we ordered only 5 had issues, and all were fixed in 4 hours (since we spin the servers for a week, none of these were in production).
I love Dell servers. I also love Dell's rails
Whether or not eagle can build "better" servers than Dell I'm not really going to get into. Can he consistently beat the price, and can he guarantee that he'll be onsite with parts in 4 hours?
And, will he still be doing this in 5 years?
I agree, support your local companies, but also do what's right for your business. If that's working with a local company: cool. If it's working with Dell: also cool. -
I know you guys are going to think this is a stupid question. Anyway here goes.....How do you guys know I am responding to these posts....Wait give me a minute to explain! I am using Synop's Sauce Reader for consuming RSS feeds. Once I visit a feed it works like Outlook the heading is no longer bold. Even if I watch this posting by adding it to Sauce Reader it does not come up bold if someone responded. I have to physically browse this feed to see if anything has been added. Are you guys doing the same thing or not.
Alright now you can poke fun.
-
Make sure you check this out:
You cannot configure Windows Firewall settings or Security Center settings on a Windows XP Service Pack 2-based client computer that is in a Windows Small Business Server 2003-based network
And, as posted above, SQL Server and MSDE run fine with SP2 (I have been running it ok). If you need other clients to access your SQL Server/MSDE, then you have to open ports in the XP firewall; that's the only issue.
As for the CRM issue (which I doubt you will have, since CRM is not supported on SBS), there is a fix:
An update is available to correct problems of Microsoft Business Solutions CRM working on Microsoft Windows XP Service Pack 2
There are (and will be more, I'm sure) a number of articles from publications/authors that usually trash Microsoft trying to poke holes in this service pack. Take what they read, look it up and research it. From these articles, you can see that the "issues" the article points out were fixed long before the article even appeared. -
Let's see if I can un-hijack this thread...

First, correct me if I'm wrong, but isn't SBS 2003 based on Windows Server 2003? If so, you can't install XP SP2 on that OS, so what are you worried about? Or, are you wondering about the effects that mharr mentions with your XP workstations?
Second, according to the TechInfo page someone linked to above, SP2 does the following to SQL Server:
* If you're running a version prior to SQL Server SP3a, network access to the database is disabled. You must upgrade to SP3a.
* If you're running SP3a, then network access will be enabled, but the default Windows Firewall configuration will block the various ports that remote clients would connect on. You would need to open the ports that your clients use to connect. -
Its called Windows XP Service Pack 2 for a reason. It for Windows XP. You cannot install it on Windows Server 2000 or Windows Server 2003. If you don't use Windows XP then don't worry about Service Pack 2.
I have SQL Server 2000 Standard running on Windows XP Service Pack 2. It all runs great. I love the enhancements in Service Pack 2 and I've been using it since the first day SP2 Release Candidate 2 was released to the public.
p.s. Go Strongbad!
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.