Problems moving from ACCESS to MS SQL

[LaSalamandra]

have a dedicated web server with Win2000 and CF MX Server.
I always used ACCESS databases. Now, I bought a space under a MS SQL
Server and I'm moving all my databases there.

Today I moved my most trafficated ACCESS database under the MS SQL
Server through Enterprise Manager. The conversion went OK. Then I
changed the informations on my Cold Fusion Administrator to use the
new MS SQL database and my web site that used that database became
incredibly slow.

I did CFSTAT on my server and saw that a lot of requests were queued
and terminated for time-out. I restored the .mdb database and now it's
all ok again ...

Do you have an idea of what could it be the problem ?

The database I moved is a little one: about 4 megabyte and just 6
tables. Under ACCESS works really fine.

Thank you in advance

[Trevor Best]

LaSalamandra wrote:

have a dedicated web server with Win2000 and CF MX Server.
I always used ACCESS databases. Now, I bought a space under a MS SQL
Server and I'm moving all my databases there.

Today I moved my most trafficated ACCESS database under the MS SQL
Server through Enterprise Manager. The conversion went OK. Then I
changed the informations on my Cold Fusion Administrator to use the
new MS SQL database and my web site that used that database became
incredibly slow.

I did CFSTAT on my server and saw that a lot of requests were queued
and terminated for time-out. I restored the .mdb database and now it's
all ok again ...

Do you have an idea of what could it be the problem ?

The database I moved is a little one: about 4 megabyte and just 6
tables. Under ACCESS works really fine.

Thank you in advance

Did all indices and primary keys find their way onto the server?
--
But why is the Rum gone?

[LaSalamandra]

Trevor Best <nospam@localho st> wrote in message news:<40******* *************** @auth.uk.news.e asynet.net>...

Did all indices and primary keys find their way onto the server?

No, but I corrected it manually and the problem remain ...

[Steve Jorgensen]

On 5 Mar 2004 02:09:22 -0800, sc******@tin.it (LaSalamandra) wrote:

Trevor Best <nospam@localho st> wrote in message news:<40******* *************** @auth.uk.news.e asynet.net>...

Did all indices and primary keys find their way onto the server?

No, but I corrected it manually and the problem remain ...

I've seen problems where the SQL Server driver first tries to use DNS to
resolve the server's name to an IP address, but the only DNS servers
configured were for Internet access and did not know about the internal
machines. In this case, the driver tries the default DNS server, times out,
tries the backup DNS server, times out, then tries SMB to get the name and
succeeds. This will only be a problem with pre-Windows 2000 servers since
Windows 2000 servers provide DNS by default.

If this is your problem, you can solve it most easily by adding the server's
name and IP address to the HOSTS file on the Web server machine.

[LaSalamandra]

Steve Jorgensen <no****@nospam. nospam> wrote in message news:<7u******* *************** **********@4ax. com>...

If this is your problem, you can solve it most easily by adding the server's
name and IP address to the HOSTS file on the Web server machine.

No ... I already put the simply IP, it doesn't work. I really don't understand ...