Hide databases in EM/QA

I have a MSSQL 2000 SP4 with ~200 databases of our clients.
Each client can access only his own database, but in Enterprise Manager
he able to view all databases on server.
How can I hide all other databases from client?Unfortunately, with SQL Server 2000, using Enterprise Mangler and Query
Analyzer, you will find that almost impossible.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
<slousch@.gmail.com> wrote in message
news:1161762813.020209.171520@.f16g2000cwb.googlegroups.com...
>I have a MSSQL 2000 SP4 with ~200 databases of our clients.
> Each client can access only his own database, but in Enterprise Manager
> he able to view all databases on server.
> How can I hide all other databases from client?
>|||This is only true for Enterprise Manager. The users will be
able to see all the user databases although they can only
access those that they have been granted access to
explicitly or implicitly (groups, guest account
considerations).
In Query Analyzer, the databases will be restricted or
filtered to those which the user has access to.
-Sue
On Wed, 25 Oct 2006 12:18:33 -0700, "Arnie Rowland"
<arnie@.1568.com> wrote:

>Unfortunately, with SQL Server 2000, using Enterprise Mangler and Query
>Analyzer, you will find that almost impossible.|||Sue,
Maybe I'm doing something wrong, but this seems to work and provide a list
of all databases on the server EVEN if the login does not have permissions
for the database.
SELECT name
FROM master..sysdatabases
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:t810k2dq7tpgrmsi4lkvivgvevss73fs7a@.
4ax.com...
> This is only true for Enterprise Manager. The users will be
> able to see all the user databases although they can only
> access those that they have been granted access to
> explicitly or implicitly (groups, guest account
> considerations).
> In Query Analyzer, the databases will be restricted or
> filtered to those which the user has access to.
> -Sue
> On Wed, 25 Oct 2006 12:18:33 -0700, "Arnie Rowland"
> <arnie@.1568.com> wrote:
>
>|||That does not affect the view. Look at the available
databases in QA from the databases drop down.
-Sue
On Wed, 25 Oct 2006 22:48:19 -0700, "Arnie Rowland"
<arnie@.1568.com> wrote:

>Sue,
>Maybe I'm doing something wrong, but this seems to work and provide a list
>of all databases on the server EVEN if the login does not have permissions
>for the database.
>SELECT name
>FROM master..sysdatabases|||While I agree that the databases won't show up in the Object Explorer, I
read the OP's question as "How can I hide all other databases from client?",
and I replied that that was virtually impossible.
Your rejoinder seems to indicate to the OP that is was safe to use QA since
"the databases will be restricted or filtered to those which the user has
access to."
And I disagree that is it possible to 'hide all other databases" while using
QA.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:mr91k2921p9mn4ousa61lj4govgj0brt44@.
4ax.com...
> That does not affect the view. Look at the available
> databases in QA from the databases drop down.
> -Sue
> On Wed, 25 Oct 2006 22:48:19 -0700, "Arnie Rowland"
> <arnie@.1568.com> wrote:
>
>

HELP: Merge Agent failed - Error number: MSSQL_REPL-2147199402)

We have 50+ clients that use a pull merge subscription. There are 2
databases and each databases has only 1 publication. Each client has ONE
subscription to each of the 2 databases.
We had to set the retention to unlimited to avoid the following error:
The Merge Agent failed after detecting that retention-based metadata cleanup
has deleted metadata at the Publisher for changes not yet sent to the
Subscriber. You must reinitialize the subscription (without upload).
(Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199402)
Get help: http://help/MSSQL_REPL-2147199402
The article http://support.microsoft.com/kb/919929/kb/919929 has a hotfix
BUT it says that it is if a Subscriber subscribes to two publications in the
same Subscriber database. This is not the case.
We had a ticket open with Miscrosoft but they were unable to find the
solution for it after 4 or 5 weeks.
The clients use their subscription databases directly and they are synced to
the server every 30 minutes.
Anybody have any idea what is causing this and how to solve this problem.
The LDF's are getting quite large and we need to find a solution soon.
Thanks in advance!
I fail to understand how the ldf's fit in here. It sounds like there are
some long running transactions which transcend the log dump boundaries. Have
you investigated what these open transactions are? Are they replication
related?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"RichardD" <RichardD@.discussions.microsoft.com> wrote in message
news:B0445940-5C26-403B-8589-692458B82098@.microsoft.com...
> We have 50+ clients that use a pull merge subscription. There are 2
> databases and each databases has only 1 publication. Each client has ONE
> subscription to each of the 2 databases.
> We had to set the retention to unlimited to avoid the following error:
> The Merge Agent failed after detecting that retention-based metadata
> cleanup
> has deleted metadata at the Publisher for changes not yet sent to the
> Subscriber. You must reinitialize the subscription (without upload).
> (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199402)
> Get help: http://help/MSSQL_REPL-2147199402
> The article http://support.microsoft.com/kb/919929/kb/919929 has a hotfix
> BUT it says that it is if a Subscriber subscribes to two publications in
> the
> same Subscriber database. This is not the case.
> We had a ticket open with Miscrosoft but they were unable to find the
> solution for it after 4 or 5 weeks.
> The clients use their subscription databases directly and they are synced
> to
> the server every 30 minutes.
> Anybody have any idea what is causing this and how to solve this problem.
> The LDF's are getting quite large and we need to find a solution soon.
> Thanks in advance!
>
|||I also expect, the size of the log file has nothing to do with your
retention period.
I'm afraid I can't help on your retention period problem, but perhaps
your ldfs are growing because of a combination of the recovery model
your database is using, and your backup strategy.
Have a look at the following articles, perhaps they will help:
http://msdn2.microsoft.com/en-us/library/ms175987.aspx
http://msdn2.microsoft.com/en-us/library/ms175495.aspx
Tim Hill
On Feb 23, 6:24 pm, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:[vbcol=seagreen]
> I fail to understand how the ldf's fit in here. It sounds like there are
> some long running transactions which transcend the log dump boundaries. Have
> you investigated what these open transactions are? Are they replication
> related?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
> "RichardD" <Richa...@.discussions.microsoft.com> wrote in message
> news:B0445940-5C26-403B-8589-692458B82098@.microsoft.com...
>
>
>
>
|||You are right. I have already fixed the issue with the log files.
Regarding the error MSSQL_REPL-2147199402 we suspect that the subscribers
changed their computer date beyond 14 days (default retention) and it caused
this error.
One reason we suspect this is that out of 40+ subscribers to the one
publication, only a few had this problem and a couple of them had it happen
twice.
Does this sound like a possibility to you?
We are about to change their retention from unlimited back to 14 days. Is
there anything we should be aware of before doing this?
Thanks so much for your help.
|||Yes, we figured out the log file issue. Thank you anyway.
We are still looking for the solution for the Error number:
MSSQL_REPL-2147199402.
Any ideas?