Currently would like to migrate my server from Win 2000 running SQL 2000 to
Win 2003 and SQL 2005. We do have 2 inhouse program and ACCPAC (accounting)
pack accessing the SQL database. According to my 3rd party software house
that changing to SQL 2005 the performance is slower ...

SQL Server Spec
SQL 2000, 8.00.2187 SP4 standard edition
windows 2003 SP1
sqlserver driver 2000.86.1830.00

I have a Windows Service middleware application that depends on SQL
Server. We are migrating from an existing Windows 2000 server/
SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
boot time and more often than not, the middleware application fails to

Oops, I accidentally put this in the wrong newsgroup the first time.  I
think this is a better location. Sorry for the double-post.
I occasionally need to create or alter a view that references a linked
server, where the linked server is not currently online (or my Internet

I seem to be getting conflicting error messages from sp_addlinkedserver.
Here is the problem:
 Exec master.dbo.sp_addlinkedserver @Server=N'SrvAlias',
@Datasrc=N'ServerName\InstanceName',@srvproduct=N'SQL Server'

Recently, an application has been migrated from Powerbuilder 9.0 to
Powerbuilder 10.5 Build 6662.   This application uses an .INI file
located in the Windows folder.  The connection to the database, which
has also been migrated from SQL 2000 to SQL 2005 is as follows:

I have created .net windows service for running an exe. Exe is running
fine. It is used for inserting xml data in sql server database.
My service mode is automatic. Whenevr i start my computer it is
throwing me an error below :-

I have an application server which receives several thousand events per
second. And it needs to store that data in an SQL server running on a
separate server connected thru network to the application server. I would
like to know the fastest and the efficient way to store the data ...

I've got this error when i tried to connect sql server from biztalk on
another domain:
provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server

We just get a connection.txt file from another organization that should be
useful for my company.
I am new to SQL connection and would like to seek your advice on what does
it mean.