I am running SQL 7.0 sp 4 it houses a database my clients use to do
financial and materials management. The database and the applications
that use the database are all purchased products.

After I upgraded the DB and all the clients were upgraded the users
where upset because certain uploads to the system were taking too long
to load. We contacted the vendor who was not much help. This journal
file is a csv file. On the old version of the software and SQL 6.5 the
journal file load would take approximately 5 minutes to load. I assume
this is using some form of BCP, after the software upgrade and running
on SQL 7.0 the journal file load would take about 2 hours. Software
support had no idea what was causing this problem.

The server was using TCP/IP as its communication library. On a whim I
aliased named pipes and set the client to use named pipes. It was at
this time I found out that the client application was still 16 bit as I
had to use 16 bit tools to set the client to named pipes. After setting
client to use named pipes and named pipes aliased on the server the
journal load went back to 5 minutes.

I am not sure if this is a problem with the 16 bit interface to windows
or what I just thought it would be some info to share.


John
MS Sql Server LazyDBA home page