September 27, 2006 at 10:03 am
I have an Asp.Net 2.0 application with a Sql Server 2k backend, both installed on a Win 2k box. I'm now installing my app on a new Win 2003 x64 server to see how my app will improve in terms of speed.
Now what I would like to know is how I should approach the Sql Server database part. Am I able to install Sql Express 2005 64bit and still have the ability to compile all my stored procedure and table triggers ? Would I be able to test out Replication (i.e. publisher and subscriber) ?
If the answer is no, maybe I should download the 180-day trial version of 2005. Perhaps that's the best approach to get started, but I would like to read some of your opinions.
Thank you,
Bob Mazzo
New York
September 28, 2006 at 10:47 am
SQL Express does not come in a 64-bit flavor. It only comes in a 32-bit flavor. It is also limited to 1GB of RAM for usage.... so this means Express is not a good fit for an x64 box. SQL Express is also not a Publisher for Replication.
The 180-day trial version of Enterprise Edition may be your best bet for testing.
There is no real "trick" to going to 64-bit in terms of recompile as far as sprocs are concerned. They are just another DB object. The 32-bit and 64-bit disk layout is exactly the same. You can attach/detach/attach/detach between the two platforms with no problem.
If you want to test the behavior of your application, try the SQL Server Upgrade Assistant (which also use Upgrade Advisor too). You can capture a workload trace from your system and replay it against a test box. It is a free download - link from http://www.microsoft.com/sql under the Upgrade section or you can download it directly from http://www.scalabilityexperts.com.
Hope this helps!
September 28, 2006 at 2:53 pm
Thanks. I'll go with the trial version.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply