I don't know your application, but perhaps something was resubmitted or yo u are missing information and don't know it.

I would check the application and see if there is a...

Logins don't have database roles, only users.

This information is easily stored in security system catalog views.

http://msdn.microsoft.com/en-us/library/ms188786.aspx

http://msdn.microsoft.com/en-us/library/ms190331.aspx

It completely depends. Patterns of access, how much are we talking about (rows and columns), and more.

This isn't necessarily something I'd worry about too early in design. It would help...

Data from one table usually sticks in the same filegroup, not sure about the same file.

Late responding, but SQL Express should work fine.

Not only that, the passphrase will need to be in code, or be entered by people. How many people can keep a shared passphrase secret?

If you think about it, not...

You can grant the CREATE PROCEDURE permission to a role and the developers could do that. They wouldn't be able to create necessarily under the owner of DBO, but you...

There are a variety of ways to do this (cursor, while), etc. Depends on what you need to do, but Sp_msforeachtable works.

Do you mean IP addresses?

If you are moving SANs, I'm not sure that it should matter for the IPs. I would suggest you attach the servers to the new SAN...

Your parenthesis don't match, You have an extra open one, and you need to either remove it or determine where you're missing the closing one.

The CTE is part of the statement. Duplicate the CTE in both statements.

You can disable CPUs with the affinity mask, but MS doesn't recognize that. The other solution (besides removing a CPU) is to run a VM and allocate only one CPU...

Those are good articles. Profiler will work if you can limit how the developers access (meaning trace their logins).

Not sure that's a correlation. If the page file is growing, I'd make it larger to start with. Restarting SQL Server can clear things out and it changes access patterns...

I've run integrity checks daily, as mentioned above, before backups. Alert someone if you find errors.

For rebuilds, I've moved to procedures that look for fragmentation and rebuild those ones only....