Database-related API questions

Discussion in 'Control Panel API' started by afterdeathc, Oct 27, 2008.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. afterdeathc

    afterdeathc WillG

    Hi,

    I have 3 database-related API questions:

    1) When I call Sql2005CreateBackup(), it is placing the *.bak into the web's root folder-- not the/_database sub-folder. Yet I read somewhere this was "fixed". So perhaps I'm doing something wrong? In other words, is there anoption tomake it automatically place the *.bak in the /_database sub-folder instead? ...and if so, how?

    2) I'm a bit confused about the API's ability to create zipped database backups. Is that feature available yet? And if so, can someone please point me to the documentation and/or a code example?

    3) Emre's Database Backup Tool Sample Application (http://desertrose.net/downloads/DiscountAspSqlBackup_Source.zip) references a method called Sql2005CreateBackupAsync(), and an event called Sql2005CreateBackupCompleted. But neither currently seem to be availableto me inhttps://api.discountasp.net/1.0/customerapi.asmx. Am I missing something?

    Any help would be greatly appreciated!

    Thanks,

    -Will-
     
  2. Will,

    1. When you run the backup tool inside your control panel it will put the SQL backup file inside your _database folder. It will no longer put it in the root directory.

    2. I'm pretty sure the SQL backup API is only to create backup in .bak backups. The compress format feature was created after the API program was created. To the best of my knowledge the API was not updated to include the .zip format.

    3. You are not going to be able to use the 'Sql2005CreateBackupAsync' method because it requires SA rights.

    rcp
    DiscountASP.NET
    www.DiscountASP.NET
     
  3. afterdeathc

    afterdeathc WillG

    FYI... The issue I was experiencing for #1 (.bak being placed in the root instead of the _database folder) was recently resolved. I think the fix had something to do with the new API version, as it suddenly began working after 3/9/09 as expected. Go figure :)
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page