I have an issue with SQL Server 2000. I am taking over maintenance of a set of databases at different sites. Each site has multiple databases, with different users controlling each database. The application has been working for several months, but error reports have started in the last few weeks. One site is reporting an error that states the user for the database is 'not a valid user in database 'tempdb'. I have been able to get access to the problem system. As a temporary solution, I found that adding a user for a specific database to the access list for tempdb allowed the application using the database to continue. (The user is a SQL user rather than a windows account). Therefore, this appears to address the problem. However, if this is to be done for all users there are over a 100 accounts to add access to tempdb. I wondered if there is a more straightforward fix. Is it better practice to use a role to assign multiple users access to a particular resource in SQL Server? From what I have read today, it appears that the public role might be what I need. I don't have access to the server today so I cannot check if the public role is assigned. Would this be the sensible next step to investigate? Can anyone suggest the situations where a users access to tempdb would be revoked? The sys admins for the machine report no changes to the setup. So, I am not sure why SQL Server previously allowed access. Thanks.