September 5, 2004 at 7:46 pm
Anybody here used this API before?
But the sample is only the client side programing
(including simple,osimple,mthread,mprocess,snapshot etc.).
so my question is :
Where is the server side? Does the SQL Server Agent do everything?
If so,what's the use of those server side functions??? Is it useless??
Where could we use them??
Thanks for reply,^v^.
September 5, 2004 at 8:01 pm
You need not concern yourself with the server side. On the Overview page, note the phrase:
The server side interface is described for informational purposes only. This interface is used exclusively by the SQL Server process.
Have you tried building the samples and running them? You might get a better understanding then. You might also want to have a brief read of our article here, to see how we used the VDI.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
September 5, 2004 at 8:45 pm
Thanks for your reply
Another question:
Could I do schedule backup to a remote computer using VDI?
How can I do it?
September 6, 2004 at 2:35 am
That's entirely up to you to implement on the client side. SQL Server will just provide you the backup data in the form of memory buffers. You decide what you want to do with it e.g. compress it, encrypt it, ftp it, write it out to file etc. If you write a command line application, it simply becomes a matter of you implementing some command-line parameters that you can call.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply