We are attempting to upgrade our Solomon (current version is 6.00.2272 (6.0
SP1) of Solomon Professional) to Dynamics SL 7.0. This upgrade will also
include moving Solomon databases to sql 2005. Our sql 2005 server is Windows
Server 2003 Standard Edition (SP2) 64 bit.
The server Dynamics will be installed on (moving it to a new server) is
Windows Server 2008 Standard Edition (SP2) 34 bit.
The documentation states that this 64 bit sql server is supported. When I
attempt to upgrade the databases (after moving backup copies from our sql
2000 to our sql 2005 server and restoring) the database update just hangs.
Is there an issue with using 64 bit sql server that anyone is aware of?
Thanks,
Kevin
*This post is locked for comments
I had the same issue of the update hanging. I finally determined that my client had not given me adequate permissions in SQL. Changing to full SQL permissions allowed the update to run successfully and it only took 20 minutes.
You should be able to move the 32 db to a 64 bit server without any issues. We just moved all of our db's to a 64 bit server late last year and they are working fine.
I thought that might be it, so let it run overnight but still was hung in morning. I was running a profiler trace on the sql server to see what was happening, but when it seems to hang, didn't see any more activity against the sql server. So I tried the same database on a 32 bit sql server 2005 (installed on my pc actually), and it ran successfully in roughly 1/2 hour. Which is when I decided to post on here. Not sure, guess I'll try again and give it more time to run, but it's hard to imagine that much of a difference between a 32 bit and 64 bit. Any other ideas or suggestions would be very appreciated.
I'm thinking now of doing the database update against the database on my local 32 bit sql server, then when that's all done, then move it over to our 64 bit sql 2005. I don't know if that's a smart thing to do or not though.
Thanks again
It is actually common for that screen to go into a not responding state while it is working. Depending on the size of your database and the hardware this could take many hours to complete.
Thanks for the quick reply. That log file comes up empty. The database update process never actually completes, it just hangs and eventually the Database Mainenance screen reports as 'not responding' and I have to kill it.
We are using SL 6.5 SP2 on a 64 bit SQL Server running SQL Server 2005. I believe the upgrade creates a log file. I think it is dbbuild.log. Does this show anything?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156