> In my line of bussiness it is not possible to help every client on this
> issue (several thousand users) What I need to achieve is transferring
> backup to the server by using SQL Server to do it and restoring it with
> SQL Server. A solution for SQL 2005 would be perfect (it is not
> necessary to solve this in SQL Server 2000). Using Named pipes is not
> an option because it is no longer supported in SQL2005
Named Pipes are supported in SQL 2005.
What exactly is your problem? Do clients do their backups to files on their
local disk? If yes, you could use scheduled jobs with SSIS packages or
simply with command promt commands for copying files.
--
Dejan Sarka
http://www.solidqualitylearning.com/blogs/