How to transfer backup from client to server machine (MSSQL, SQL Server)

MSSQL, Microsoft SQL Server:
I succeeded in transferring a backup file from the SQL Server machine
to the client using OPENROWSET.
I used this way because it is not (always easy) possible to restore a
file residing on the client machine on a SQL Server.
One has to share drives on the client machine for remote SQL Server
access or better granting access on the SQL Server machine for the
client.
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
Hi
"Oz" wrote:

> MSSQL, Microsoft SQL Server:
> I succeeded in transferring a backup file from the SQL Server machine
> to the client using OPENROWSET.
I am not sure why you are doing this, if you are actually talking about a
database backup. I assume this is a CSV or XML file? If so why not use the
BULK INSERT command? This will take a UNC name for the file if necessary.

> I used this way because it is not (always easy) possible to restore a
> file residing on the client machine on a SQL Server.
> One has to share drives on the client machine for remote SQL Server
> access or better granting access on the SQL Server machine for the
> client.
> 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.
Have you looked at SSIS and loading the file using FTP either through a
package or User Interface (e.g
http://classicasp.aspfaq.com/general/how-do-i-ftp-files-from-asp.html ) onto
the SQL Server or somewhere which can be seen by the SQL Server and then
loading it from a package?

> 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
>
John