I am writing a web application that uses a Teradata database as the primary data source. While Teradata is great as a data warehouse and managing Terabytes of information it doesn't do as well when update or inserting. I was thinking of using a local SQL2005 MDF file to hold a few reference tables and an audit table to collect usage information and exception database to capture any errors.
There could be a few thousand users of the web application but no more than a couple hundred at a time.
I just trying to get some opinions on these technique. I am open to all comments and suggestions.
Thank You
Hi John,
If you're using the SQL Server as the auditing database and exception tracking, I think it will be fine.
Although there will be hundreds of connections to the main app, the exception will not be much and audit data size will not be huge then. Just connect the audit and exception handling module to your SQL Server database, and it will be OK.
HTH. If this does not answer you question, please feel free to mark it as Not Answered and post your reply. Thanks!
|||Kevin
Thank you. I'm wondering if it is acceptable practice to run SQL Server 2005 express rather than installing a full SQL Server 2005 on the Advanced Server for doing the Audit tracking and exception reporting. The MDF file should never reach the 4GB limit of Express. Thank you again for your answer.
No comments:
Post a Comment