One way to speed up SQL Server 2005 is to upgrade the underlying operating system to Windows 2008. Why? My top three reasons would be:
However be aware you might need some hot fixes so check these articles before you try it as SQL Server 2005 may not install cleanly on the new OS:
Update for Windows Server 2008 for Itanium-based Systems (KB950636)
Update for Windows Server 2008 x64 Edition (KB950636)
Update for Windows Server 2008 (KB950636)
PingBack from http://windows2008security.com/windows-server-security/windows-server-2008-and-sql-server-2005/
Thanks for your helpful blogs. I have a related question, still aiming to run SQL Server 2005 under Win 2008 server. Suppose I want to run the Win 2008 Standard Server as a VM (using Xen virtual host) under SUSE Linux 10.1 (or the latest version)- either the SLED Desktop (or SUSE Ent.Server). Assuming the hardware is an Intel X86 dual-core machine with at least 4Gb RAM, will this be practical, assuming the Win 2008 is a lean version with few services. Novell is claiming to support running a Win VISTA VM or Win 2008 Server VM under Xen. My reason for asking this is, that Hypervisor is not out and I need to test something soon using a Win 2008 Virtrual Machine. Thanks in advance, Stan
Not sure I understand your question so drop me an e-mail
we are migrating our ERP which uses database running on SQL server 2005.
Currently the ERP is located on external server where we access it remotely.
Now we want to put the ERP and its database accessible over LAN.
We have set-up our LAN on Windows server 2008 and on that server we have installed SQL server 2005 standard.
The problem is that when running the ERP from within the server (either physically or through remote access) everything seems to be working perfectly.
When i am trying to operate from a client the ERP halts. Then i test the .udl file and seems there is no connection to the SQL server (it gives an "SQL server not found or Access denied..."...
The same .udl accessed from within the server (physically or remotely) works fine...
Does it gives you any clue what may i be doing wrong???
Many thanks in advance for any informatiion or help you may provide...
My chief suspect is Winodws Server 2008 firewall. you need to open up port 1433 (assuming this is the port you are using for SQL Server).