no, you Need to use SQL Server Management Studio

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Shrinking the database won't affect the content of the database. A database isn't always filling the space it has claimed with content. Shrinking will release that currently unused space back to the disk.

If you empty the eventlog table, now there is unused space which is still part of the database.

That sounds better than it is, perhaps. It won't particularly improve the performance of the database to do this. Sometimes it even has the reverse effect in that now if a database needs more space, it has to grow itself before it can write content. If the space was left in the database, it can simply write. Thus, a practice of constantly shrinking databases to keep them as small as possible is not recommended.

That doesn't mean that an occasional shrink action is a bad thing, however.

But setting a database to auto-shrink is bad, and daily or weekly schedule shrink task is not what I would recommend, either.

---

pmgerholdt

there are a number of aspects affecting performance, usually caching is the biggest one. Combining files CAN improve load time due to reducing the number of elements to be downloaded - but this effect gets inverted, if every page has its own set of resource files, which need to be downloaded every page load instead of re-using most of the ones used on every page. IMHO you need to test the effect for a new user by adding measured load time of a typical set of pages with or without combined files.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN