After installation of MS SQL 2000 i noticed the following default db's that were installed by default;

Northwind
tempdb
Master
Msdb
pubs
Model

Problem is all my users can see these db's. Is it safe to remove them? If not, how does one restrict others from seeing them? All of them have the PUBLIC permission by default so everyone can see them. I have looked everywhere and there doesnt seem to be a way to hide them from peoples view.

You would hide them like any other DB, remove a users permissions to access the DB.

Northwind is the MS example db that they seem to use for everything, these days. Feel free to delete that.

Tempdb is just that -- the tempdb... Feel free to delete that.

I'm not sure on the rest, I only have SQL 7, and I haven't logged into it in a long time -- no need

Someone else will have to fill you in on the rest.

I was able to hide all except Master and tempdb. It seems that even those these show when using mixed mode users cannot do anything with them.

I have a few users connecting to their databases using mixed mode instead of Windows Authentication. I guess thats the only way you can connect to a MS SQL db if your using SQL Query from a remote locate. So far the windows authentication mode denies the user the connection. Really must find a tool that users can use to connect to their db's.

Master, model, tempdb and MSDB are system databases - you can't drop one of these databases without causing serious harm to SQL Server.

pubs and Northwind are simply samples to help you lear SQL Server

If you have just installed MS SQL 2000 make sure you have the latest patch installed. http://www.microsoft.com/sql

Ray

Ok, so how do i restrict users from seeing it? I have a user whos logging in via Enterprise Server and after connection using, SQL Server Authentication he can see all my databases. This is very annoying. I should be able to hide these db's from his view and only allow him to see his own database. The other question is, is there a way to use Windows Authentication from a remote connection, not local. If so, where does the user setup his connection login etc?

I don't know the answers to your questions. I have one application that I run on my SQL server. I am the only one that goes in there so I have never worried about these issues.

Ray

Use an SQL login for external users - unless you have very few users doing it with Windows Authenication will be a nightmare.

You can't hide the other databases - it's just the way MS SQL is.

I've never seen anyone able to hide them. It used to be anoying when I was at brinkster.net, it'd load hundreds of DBs in enterprise manager then I'd have to scroll and find mine.

There is no way to hide the databases from view in EM.

I was able to hide all these db's by removing the GUEST permission on them with the exception of 2 db's, MASTER and TEMPDB.

Write a how to. If you can pull this off, you are the David Copperfield of the MS SQL World.

SQL Server doesn't have a guest user, and Enterprise Manager could care less about NTFS.

after I actually thought about what you were talking about, this may make a little sense. are you using 2000 or 2003?