Get your DBA to create you a login on the SQL server and pass that information in your database connection string (sorry don't know C# so I couldn't give you...

A SAN is definately a good thing (in my experience), however I would be inclined to agree with you that it's overkill for your environment.

You don't mention if you are...

The mdac version that ships with Windows 2000 is 2.5, which is unable to dynamically determine the sql port (it does not connect to udp1434 to get this information), so...

Don't bother with the xp_startmail, xp_sendmail will also start the mail session.

Try logging on to the server using the sql service account, then go into outlook, check the profile is...

What is the error that you receive?

Another thought would be to use SQL Server Agent to run the pacakge.

Try updating the MDAC version on the windows 2000 machines to 2.8.

I have all that, with it dynamically setting the source and destination.

The problem is that the source tables are all different and they don't have the column names as the...

I can honestly say that I have never read Inside SQL Server so I can't really comment as to scan density being a reliable measurement of fragmentation for tables spanning...

Try using MSDAORA instead of MSDASQL.

Also, what's the query you are trying to run?

Something like this?

CREATE PROCEDURE ADD_LOGINS @USER VARCHAR(20), @PWD VARCHAR(20)

AS

if not exists (select * from [dca-siebdb].master.dbo.syslogins where loginname = @USER)

BEGIN

 declare

 @logindb nvarchar(132),

 @loginlang nvarchar(132) select @logindb = N'workgrps',

 @loginlang = N'us_english'

  if...

How about changing the search to a proc and just passing in the parameter?

Get your network bods to check for incoming connection attempts, there could be a virus on another machine, a trojan or a script kiddie.

As the job will run continuously (as the sp will never stop running unless it fails) setting the notification option on job failure will alert you if you get any...

You could set the stored proc to loop and use a WAITFOR DELAY 00:00:05 before the loop completes. Then call the proc every time SQL starts.