Okay, here my previous replies:
"I think this is a little off topic, but to answer your questions:
How you distribute your databases and logs onto LUNs is really up to you, as long as they are ALL on LUNs. Ofcourse it all depends on business requirements, licenses, level of complexity, etc. There is great and elleborate documentation about this subject on NOW, along with a lot of (sometimes conflicting) Best Practices. I don't have the numbers at hand, but I suggest you try the search module on NOW. These documents should give you a really good idea on how to set things up properly.
At the very minimum, you should have:
- LUN 1 for all the systemdb's and system transactionlogs
- LUN 2 for all your user db's and transaction logs
- LUN 3 for SnapInfo data.
Tempdb is recreated at each reboot, that's true, but if you don't change the location of the tempdb, it will be created on a local drive every time."
"First of all: dumb the Northwind database ASAP! 🙂 It's a demo database that serves no purpose other then that and forms a huge security issue to your SQL server(s).
having said that, as Northwind is a demo database, it's by definition a user database and cannot be placed on the same LUN as system dabatases. That's what the wizard was telling you.
Not sure about the other messages you get, but I do know SMSQL definitely doesn't need your db-files and translog-files to be on separate LUNs. Are you sure you selected all the files, associated with master? Don't forget about full text indexes and such."