I have a development machine that I am setting up.... It is ready to go.

- Windows 7
- IIS 7.5
- DNN 5.6.1
- SQL Server Express 2008 R2
- Visual Studio 2008 SP1
- Chris Hammonds Module Template

Everything is installed and working just fine....

What is best practice/method for manipulating the SQL Server Tables etc...

I have read on the DNN forums many cases of frustrated users trying to access via SSMS. I know I can attach the database, but it throws errors back to the website once the file is attached? SSMS can cause all type of errors without changing the Database Connection strings, etc....

How do professional developers handle this crucial piece of the puzzle?

My short and simple answer is that, for the most part, you can happily keep your hands off of your database. The only time you'll absolutely need to get in there is if/when you've damaged something and can't fix it with the administrative tools that are built into DotNetNuke. If you concentrate on that UI, you'll be fine ... 99.99% of the time.

In my case, I actually need to do some database development at the same time on this database - so I will need a firm resolution to this.

I guess I am in the .01%

What kind of development will you be doing inside of your DotNetNuke database?