Bug

• 
  Hi Sangha,
  
  I was aware of this behaviour and can't quite make my mind up if it is/should be a bug or is the correct behaviour, I can see that it some cases it can be seen as a bug however in other cases (where the drop is temporary and someone intends to recreate the database) I don't think it is a bug. Do you have any strong arguments for getting rid of the activity history which I have not thought of? If so I would be interested in hearing them.
  
  Many thanks,
  
  - James

  James Moore January 09, 2007 04:40

  - 0 +
• 
  Hi James,
  I think if the drop is temporary then the database can be recreated using the restore(Browse for files) feature in SQL Backup. In the example that I had given if the dropped database "db1" is restored using a previous full backup in SQL Backup and the new database is also given the name "db1" then only Activity history should be linked with the new database.
  
  Otherwise you will get the following error whenever you try to do a restore : -

  SQL Server error
  Server: Msg 3013
  RESTORE DATABASE is terminating abnormally.
  Server: Msg 3154
  The backup set holds a backup of a database other than the existing 'db1' database.
  SQL Backup exit code: 1100
  SQL error code: 3154
  

  sangha January 09, 2007 05:47

  - 0 +
• 
  If the activity history is not for the given database the user should be able to delete/clear the activity history for that database.

  sangha January 11, 2007 01:05

  - 0 +

Add comment

Please sign in to leave a comment.