I'll answer as many of these as I can from my own experience.
1. Is there any reason not to go 64 bit?
--- According to MSDN, there are no plans on making VPP 9 a 64bit software so it won't take advantage of the 64bit kernel. If this is the primary task of this server, I would stay 32bit. If you upgrade down the road, plan the hardware lifecycle to upgrade with it. (Referenced here: http://msdn.microsoft.com/
2. Any problem with 32 bit apps on 64 bit server (Visual Foxpro 9, etc.)
--- There's a good Microsoft KB article that may answer some of your questions about compatability: http://support.microsoft.c
3. Will SQL 2008 really be out around 8/08? Should we wait/buy SA?
As of today, the date is still set for 8/08.
4. Anything I'm not thinking of? Integration into 2000/2003 server domain, backup software etc?
--- I can't foresee any issues with integration into the server domain. As long as you have a good grasp of managing 2k and 2k3 domains, you'll be fine. See question #6's answer for Backup.
5. For purposes of high availability (not automatic failover, just up to date data copy), . . . .
--- From my undersrtanding of the Microsoft's licensing on SQL server, this is not allowed. Another license would be needed.
6. To steer off the 64 bit question, . . .
I have had great success for offsite backup, through FTP, for live SQL databases with a program called "Backup for Workgroups". Great piece of software and I use it at about 20 sites:
http://backupforworkgroups
Main Topics
Browse All Topics
by: sbagireddiPosted on 2008-05-30 at 10:41:59ID: 21679838
1. Is there any reason not to go 64 bit?
Not really, if you can afford it.
2. Any problem with 32 bit apps on 64 bit server (Visual Foxpro 9, etc.)
No, only that they will not be able to use the performance improvement that 64 bit provides.
3. Will SQL 2008 really be out around 8/08? Should we wait/buy SA?
I would suggest using SQL 2005, specially with Microsoft, you need to wait a year or
so after the real release, so that all the bugs are ironed out.
4. Anything I'm not thinking of? Integration into 2000/2003 server domain, backup software etc?
Again depends on your custom needs, but we have all our SQL servers on windows 2003 server, and they work.SQL server 2005 has all the backup tools built in.
5. For purposes of high availability (not automatic failover, just up to date data copy), if, say, I set up another 64 bit windows server
for a file server etc, would I then be allowed, under my MS SQL license, to install additional copy to the other server & mirror the databases
to use in case of failure on the primary? Is this the best way to ensure I have up to date database copy, or should I be looking at Backup Execs continuous protection, or both?
No, you will need to buy another license
6. To steer off the 64 bit question, what is the best solution for having an up to date offsite copy of my databases in case of disaster?
I have hardware vpns to my home, remote offices etc. Perhaps a question for another forum. I haven't had time to research the new Backup Execs features.
There is log shipping, replication, mirroring - but they all are for specific needs.
You will need to read SQL server 2005 Books Online and accpordingly go with the best fit for your needs.