- I have a SQL server database
- I have more than 200 tables in the database
- I have one table that contains information on every row in all the tables. So this table will have millions of rows (Let us name it Bigtable)
- Any data modification (insert, update, delete) on any row in any table in the database will make the same operation on the relevant row in the Bigtable, so we have a lot of data modifications in this table,
- Any query on any table will join Bigtable to get relevant data from the Bigtable. (so there will be a lot of joins to Bigtable

MY QUESTION: is there a problem with such a design; What about performance, indexes ??

My daily maintenance job fails due to the below error from last 20 days regularly

Executing the query “BACKUP DATABASE [shipment] TO DISK = N’D:\backup\shipment.bak’ WITH NOFORMAT, NOINIT, NAME = N’shipment’, SKIP, REWIND, NOUNLOAD, STATS = 10
” failed with the following error: “Write on “D:\backup\shipment.bak” failed: 112(error not found)
BACKUP DATABASE is terminating abnormally.
10 percent processed.
20 percent processed.
30 percent processed.
40 percent processed.
50 percent processed.”. Possible failure reasons: Problems with the query, “ResultSet” property not set correctly, parameters not set correctly, or connection not established correctly.

very recently i have changed the recovery mode from Full to simple and truncated the log file and i changed back the recovery mode to Full.
Does this affect the db.?

The maintenance plan was set to take the back up of full db.
How to sort this issue.
Sql 2005 on sp2.

Any ideas will help me.

Thanks