Hi all,

For those using SQL as the DB for storing WW session and log data, is it better to use a DB dedicated to just the WWC tables or add the WWC tables to the application database?

TIA

Probably a good idea to add it to the SQL database (or a separate SQL database even). This way if you scale to multiple machines later, the data is in a central location. With DBF files you'd have to share the files over the network (slow and maintenance issues).

+++ Rick ---

Our application DB is SQL. At the moment the only DBFs are a handful of lookup tables and we'll be pushing those into SQL. So my question is should I put wwsession in the application DB or create a dedicated DB just for the WW tables?

If you maintain the tables and clear them out regularly then I'd probably put them into the same database. But if you let them go or you plan on archiving the data then using a sperate DB in SQL might be better to isolate the size away from your application data. These tables can get quite large and they'll inhibit the backup process and movement of the actual data.

+++ Rick ---

Thanks, Rick. That was my instinct but figured it was a good idea to check with the collective wisdom.