Mark Breen
marklbreen at gmail.com
Sat Jan 8 09:34:58 CST 2011
Hello John, In this case, I would like to know whether there is a database corruption issue or a connectivity. What about quickly creating a new db names testconn and see if you can connect to that. If it works and disco does not, then quickly check the db mappings from the properties dialog box. If you are mapped and you think that you should be able to see it, then maybe the db is corrupt. A few things to do are, stop and start the server, then refresh the branch and check again. Detach and re-attach the db and see if it helps Start thinking about a restore is that any help? I have seen ghost db's hang around but usually the three-step dance of stop start services, reboot, delete again etc will remove it. HTH Mark On 8 January 2011 05:06, jwcolby <jwcolby at colbyconsulting.com> wrote: > I went back in with MSE and looked at that server. While I can see the > databases of interest, if I click on them and try to see the tables inside, > I get an error "the database DISCO is not available" and the plus symbol in > front of the database disappears. > > So I can see that the db exists but not actually access it (from my > workstation). > > I can see and open the database from MSE on the server itself. > > Is this an ownership / rights kind of issue? I am not getting an actual > error number from my workstation, just an "not available" generic kind of > message. > > If it is ownership / rights, how do I go about discovering how to fix it? > > -- > John W. Colby > www.ColbyConsulting.com > _______________________________________________ > dba-VB mailing list > dba-VB at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-vb > http://www.databaseadvisors.com > >