Posting again as i had no reply : Moving dbs

Is there a way that one can detach/move a database that is in norecovery or
standby state thats awaiting more T-logs to be applied and then attach/bring
it
back in the same state and continue with T-logs restores ? I know one can
detach a nonrecovered/standby database but while attaching it it recovers
it... and
that what i want to avoid.
Any way to modify some system tables (sysdatabases) to achieve this. Any
help would be much appreciated. Using SQL 2000.Not that I can see. I had a couple of tries at this but I see no documented
way to do it. As you rightly say, FOR ATTACH recovers the database. I guess
you could probably do something with the status but I would not recomend
hacking the system tables.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OPA7f$$cDHA.2416@.TK2MSFTNGP09.phx.gbl...
Is there a way that one can detach/move a database that is in norecovery or
standby state thats awaiting more T-logs to be applied and then attach/bring
it
back in the same state and continue with T-logs restores ? I know one can
detach a nonrecovered/standby database but while attaching it it recovers
it... and
that what i want to avoid.
Any way to modify some system tables (sysdatabases) to achieve this. Any
help would be much appreciated. Using SQL 2000.|||All I would say is that it would probably be unsupported should you
encounter any issues so you're on your own. If this is a production
environment I would strongly recomend against it.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%237mkvdJdDHA.2804@.TK2MSFTNGP11.phx.gbl...
I tried to do this and was successful. It does involve hacking sysdatabases
. But am also hesitant as I am not too sure what the future holds. It works
fine now...But would hate to see some error later down the line
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:ucdZNaIdDHA.1128@.tk2msftngp13.phx.gbl...
> Not that I can see. I had a couple of tries at this but I see no
documented
> way to do it. As you rightly say, FOR ATTACH recovers the database. I
guess
> you could probably do something with the status but I would not recomend
> hacking the system tables.
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:OPA7f$$cDHA.2416@.TK2MSFTNGP09.phx.gbl...
> Is there a way that one can detach/move a database that is in norecovery
or
> standby state thats awaiting more T-logs to be applied and then
attach/bring
> it
> back in the same state and continue with T-logs restores ? I know one can
> detach a nonrecovered/standby database but while attaching it it recovers
> it... and
> that what i want to avoid.
> Any way to modify some system tables (sysdatabases) to achieve this. Any
> help would be much appreciated. Using SQL 2000.
>
>

Possible to restrict which dbs are shown in Management Studio...

Hi,
I'm migrating a load of databases from a SQL 2000 server to SQL 2005 and was
wondering if anyone knew how to restrict the list of databases that users
see when they connect using the Management Studio to only those that they
have access to? This was done in SQL 2000 by using the following:
http://support.microsoft.com/default.aspx/kb/889696
Any help is appreciated.
Thanks - Joe.In 2005, you have meta-data security built-in. By default, a user can't even see the existence of an
object they don't have permissions to use. Database is the one exception though, but you can handle
that through the VIEW DEFINITION permission.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Joe Mills" <joemills84@.hotmail.com> wrote in message news:u2y1H$0BHHA.2328@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I'm migrating a load of databases from a SQL 2000 server to SQL 2005 and was wondering if anyone
> knew how to restrict the list of databases that users see when they connect using the Management
> Studio to only those that they have access to? This was done in SQL 2000 by using the following:
> http://support.microsoft.com/default.aspx/kb/889696
> Any help is appreciated.
> Thanks - Joe.
>

Possible to restrict which dbs are shown in Management Studio...

Hi,
I'm migrating a load of databases from a SQL 2000 server to SQL 2005 and was
wondering if anyone knew how to restrict the list of databases that users
see when they connect using the Management Studio to only those that they
have access to? This was done in SQL 2000 by using the following:
http://support.microsoft.com/default.aspx/kb/889696
Any help is appreciated.
Thanks - Joe.In 2005, you have meta-data security built-in. By default, a user can't even
see the existence of an
object they don't have permissions to use. Database is the one exception tho
ugh, but you can handle
that through the VIEW DEFINITION permission.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Joe Mills" <joemills84@.hotmail.com> wrote in message news:u2y1H$0BHHA.2328@.TK2MSFTNGP02.phx
.gbl...
> Hi,
> I'm migrating a load of databases from a SQL 2000 server to SQL 2005 and w
as wondering if anyone
> knew how to restrict the list of databases that users see when they connec
t using the Management
> Studio to only those that they have access to? This was done in SQL 2000 b
y using the following:
> http://support.microsoft.com/default.aspx/kb/889696
> Any help is appreciated.
> Thanks - Joe.
>