Depends on what FTP client your are using, Windows XP FTP (command line) supports wildcards in the file name, see XP Help for FTP subcommands, you can use the glob...

Check out the KB article on this:

http://support.microsoft.com/default.aspx?scid=kb;en-us;317746

Andy

I implemented a SQL Server Agent job to do these FTP Push tasks from NJ to CA without DTS. I found that the FTP Put will max out the T-1 between...

ODBC and OLEDB use SQL Server features that need to be kept in sync with the MDAC version the 3rd party application is using. So check the 3rd party application...

I posted a script that I used to debug an application for deadlocking. This script is currently waiting for approval, so when it is available you can get it here:

You might also look at SET TEXTSIZE in BOL, to work beyond the 8000 limit for a varchar.

Andy

Comparing a text field will be problematic once it gets too large, check out this new script for a easy way to determine if the text fields are an exact checksum match:

There is no ODBC option for the SQL Server ODBC driver to connect to a file. Sounds like you are confusing Access and SQL Server.

SQL Server is a server side...

If you are using SQL Mail, then:

Login as the new domain account and create a new Outlook profile.

Run EM:

Assign SQL Mail this new profile.

SQL Agent properties:

If you are using the domain...

Check out this script:

http://www.sqlservercentral.com/scripts/contributions/764.asp

I use it every week and it works for me.

Andy

Try this:

SELECT TOP 10 u.Serial, r.Model, u.Release, d.EventDate

FROM Release r

 LEFT JOIN Production_Unit u ON u.Release = r.Release

 LEFT JOIN Production_Detail d ON u.Serial = d.Serial

  and d.EventID = 'PO' And d.EventPF...

SELECT CONVERT(varchar,CAST(123456.9901 AS money),1)

Andy

One thing to check is the Windows 2000 MDAC version, XP service packs update MDAC, and since Windows 2000 doesn't you may have to deploy a MDAC update.

Another that may...

Go to BOL, Shrinking the Transaction Log:

mk:@MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_da2_1uzr.htm

Change your DBCC statement to:

DBCC SHRINKDATABASE (tempdb, 10) WITH NO_INFOMSGS

Andy

You could create another Job scheduled a few minutes after the hour to perform a CmdExec MOVE ... operation. The few minutes should be greater than the worst case log...