Steve Erbach
erbachs at gmail.com
Sun Feb 13 21:22:29 CST 2005
Billy and Jim, I have the answer. I've been working on an ASP.NET application that uses a SQL Server backend. The SQL Server database is hosted on a shared SQL Server by CrystalTech. There are 401 databases on this particular SQL Server. On Jan. 17th I backed up my client's database to my local server. For some reason my backup brought in all the various syslogins for all the rest of the databases on that CrystalTech server. None of them can get at the data on my own server, of course; I just somehow copied the login definitions for all 450+ users of that CrystalTech server. Beats the tar out of me. Steve Erbach Neenah, WI On Sun, 13 Feb 2005 19:09:31 +0000, Billy Pang <tuxedo_man at hotmail.com> wrote: > Not sure how those logins got there in first place. first thing I'd check > is syslogins table to see when they were created. (ie. SELECT crdate,* FROM > master.dbo.SYSLOGINS). maybe that provides some insight. what is an > example of the bogus logins that are created? do they follow some sort of > naming convention? maybe it was created during some sort of app install. > > HTH > > Billy