You can see the filegroup a table belongs to by looking at the properties of the table in Management Studio. If you only see "primary" for the filegroup, you...

There's the SQL Server Upgrade Advisor, a free download from MS: http://www.microsoft.com/downloads/details.aspx?familyid=F5A6C5E9-4CD9-4E42-A21C-7291E7F0F852&displaylang=en. It will explain things that need to be changed before or after upgrading.

This is explained thoroughly in BookOnLine. Also in this thread posted this morning: http://www.sqlservercentral.com/Forums/Topic853971-145-1.aspx.

I've never heard of a tool that imports a .dmp file to SQL Server and the product you mentioned sure doesn't give much information. I didn't even see anything...

You could add the operators to the fixed database role SQLAgentOperatorRole in msdb, which can view and execute jobs it doesn't own. Review the other permissions the role has...

Check out Jeffery Williams' solution in this thread: http://www.sqlservercentral.com/Forums/Topic765071-1291-1.aspx

In particular, the method described by Dale Cunningham in that thread has always worked for me.

As long as the user in msdb doesn't have any other permissions, I don't see any harm in it. The role only allows members to work with packages that...

No. Only members of sysadmin or db_owner roles or the user who created the diagram can open it. The reason I've seen for this is that the diagrams...

Are you scripting just database users or logins also? The thread that Henrico references suggests using MS's sp_help_revlogin which scripts logins, including their default database. A newer version...

If you job step is a T-SQL Backup command, you can add COPY_ONLY to it. Is your job a Maintenance Plan?

Olympia, Washington.

When I tried this in a test database, I got an error on sp_grantdbacces that said, 'User, group, or role 'x' already exists in the current database'. I think...

I haven't encountered any problems restoring a backup to prior interim version, only bewteen major versions, e.g. SQL 2005 to SQL 2000.

The db_owner role is probably a good choice, but be aware that a user in this role can drop the database. You definitely don't want to allow the user...