Showing posts with label everybody. Show all posts
Showing posts with label everybody. Show all posts

Sunday, March 25, 2012

Do I need to change hardware when migrating from SQL 2000 to SQL 2005?

Hi Everybody!!!!

Do I need to consider investing in new and more powerful hardware when migrating from SQL 2000 (or any other previous version) to SQL 2005?

I have a friend / client who migrated from SQL 2000 to SQL 2005 sp 1. The performance of the server got really bad, and now he's trying to fix the problem by any means necesary.

I think it would be very understandable if investing in hardware would be recommended, as we all have seen that there are so many new platforms to use and integrate to (.NET framework, XML, soap, ADO.NET, etc, etc,) and keeping the old platforms as compatible as always (ADODB, ODBC, etc.)

Any feedback is greatelly appreciated!!!!

Tarh Ik

I would recommend having a fresh, new server with Windows Server 2003 R2 SP2 and then installing SQL Server 2005 SP2 on it. Then, you can either detach/attach or restore from a backup to migrate from SQL Server 2000. This is much less risky than upgrading in place from 2000 to 2005 and will perform better than installing a named instance on the same server where SQL 2000 is running.

As far as hardware goes, obviously, new, faster hardware is better if you have the budget for it. Hardware prices continue to get lower all the time, and nobody has ever complained about a database server being too fast.

Sunday, March 11, 2012

DLookup -> Timeout

Hello everybody...
I've got a little problem using DLookups in VB (Access) with MS Sql 7.0.
I'm using it to get some data while looping trough a recordset (while not rs.eof ... dlookup ... wend) - the problem is - always on the 81'st recordset I get a timeout ... i wait a couple of seconds and then the code gets halted, press play again and it works... does anybody know a solution to this problem? should i do a rs.open instead of a dlookup?

Thanks for helpin'!

Greetz - Marcextension of upper thread...
I've tried with an rs.open also, same problem after 80 records...
It seems like a max-login restriction in the sql server or something...

Anyone any Idea?

thx