- can you connect to your access db using the 64-bit odbc ?

%SystemRoot%\system32\odbcad32.exe

- can you connect to your access db using the 32-bit odbc ?

C:\WINDOWS\SysWOW64\odbcad32.exe

btw I also noticed the copy...

- are you connected as sysadmin / dbo / tablecreator ?

- which schema did you specify ?

Because also some (??) production applications were suffering this unavailability, I faileover the instance and everithing worked back just fine !.

After reboot of the node ( because all instances of...

you can also use ##-temptables (#-temptb = local temp tb, ##-temptb = global temp tb).

You can create normal tables in tempdb, but I wouldn't advise to use it because when...

if you are using the GUI, you have an option to install a new instance (so not upgrating the existing instance of sql2000)

maybe just some CPR

split the updatequery in chunks so it does not lockout the whole of the table (unless you realy need the...

after you've added the roll to all existing user-db, also add it to model database.

that database is used (copied) to create every new db !

If you're going to populate the tables , do you use table hints (tablock) ?

This may avoid all the rowlevel locking overhead you're suffering.

Offcourse, you need to be the only active...

Is this a dedicated SQLServer server ?

If not, check out the amount of ram used by other applications. (With your settings, they shouldn't consume more than 1Gb ! )

Because you've...

a timeout is a client-side setting.

it is something the client decides and handles !

run sql-profiler during your rebuild.

Maybe it shows conflicts or ongoing queries of applications (wich you didn't expect to take that long)

if your server has less then 4 Gb ram, AWE is overhead.

Use the /3gb switch and that should do just fine as long as you stay under 3gb for each...

we've all started as "just a lowly developer" ... it take a hunter to know a hunter

probably your tempdb needs to be bigger...

also start traces 1204 and 3605 for all sessions (and add -T1204 and -T3605 to the startup parameters of your sqlserver)

They provide deadlockinfo in your sqlserver-log-files.

- Setting deadlock_priority to low...

- check the datatypes of the parameters provided by your application.

You'll be able to avoid index-scans, if you use the correct datatype (as defined for the column of you table).

-...