how to Allow Multiple access to data base over network

Hello All, I have a running/ woking database, but only one user can
access the data base at a time on the newtork, If more than one user
try accessing the database, it will frezee until the first to grab the
data base logs out. Please how do I solve this problem. I have sql 2000
enterprise edition running on the server.
Regards
Agboola.1default wrote:
> Hello All, I have a running/ woking database, but only one user can
> access the data base at a time on the newtork, If more than one user
> try accessing the database, it will frezee until the first to grab the
> data base logs out. Please how do I solve this problem. I have sql 2000
> enterprise edition running on the server.
> Regards
> Agboola.
>
First, check the database properties to make sure it's not in
Single-User mode. However, that doesn't sound like your problem.
What exactly freezes up? It sounds like your first user is doing
something that is blocking other users. You can confirm that by
querying the sysprocesses table in the master database, or by issuing
the command 'sp_who2' in Query Analyzer.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Looks like you have the database in restricted or single user mode. But you
should receive messages like these, instead of freezing the session:
Database 'Northwind' is already open and can only have one user at a time.
Database 'Northwind' is in restricted mode. Only the database owner and
members of the dbcreator and sysadmin roles can access it.
Try this first: Using Enterprise Manager, right-click your database,
Properties, select the Options tab and make sure the Restrict access option
is not checked.
Hope this helps,
Ben Nevarez, MCDBA, OCP
Database Administrator
"1default" wrote:

> Hello All, I have a running/ woking database, but only one user can
> access the data base at a time on the newtork, If more than one user
> try accessing the database, it will frezee until the first to grab the
> data base logs out. Please how do I solve this problem. I have sql 2000
> enterprise edition running on the server.
> Regards
> Agboola.
>

How to activate the MSDTC service?

Hello,

As newbie in server country I try a course example to test a distributed transaction accessing both SQL Server 2005 and Sql Server 2005 Express.

But I get an error message saying:
>MSDTC on server is not available

I Internetted somewhere that MSDTC stands for TransactionManager service.
If I look in the 'Services' list I do not see something like MSDTC, so I think it is not installed or started.

How do I install or activate the MSDTC service?

Thanks in advange,
Henk

Hi,

What OS are you using? I have Win2K3 and I do see "Distributed Transaction Coordinator" as a service.

Thanks

Waseem

|||

In the services list it should be named "Distributed Transaction Coordinator".

You should check ControlPanel->AdministrativeTools->Component Services->Computers->My Computer->Properties.

Have a look at http://msdn2.microsoft.com/en-us/library/ms684146.aspx for a general documentation.

|||

Thanks both of you!

I'm using WinXP Prof and I see a 'Distributed Transaction Coordinator' service thats waiting to be started....
After starting it, my program runs fine!

regards,

Henk

How to access the DB with Integrated Security

Hello,

I'm new to ASP, but developping in Sql for years.

What we would like to have is that the user is accessing the database over it's own Windows Logon. Our triggers log quite some changes and are using UserName() for this. I've treid to force the IIS to accept Windows Integration only, the SqlDataSource users a connection that has Integrated Security = True. But when connection to the site i'm gatting error that there is no trusted connection for the user . (dot) ...

I suppose i'm missing something but could you give me a hint where to start looking.... THX

Hello my friend,

Is the database and the website running on the same domain? I ask because it may be that the SQL Server has no recognition of the Windows account being used on the website server. To cater for future requirements, including the ability of third parties to be able to access this data source, I would use SQL Server authentication (but not the sa account!). Create a sql server user with restrictions on the tables/views/procedures/etc they can use. This is much more secure and extendable than the Windows approach.

Kind regards

Scotty

|||

It is on the same domain.

The mean reason for trying this approach is the triggering, in our classic applications we use the windowslogon and so we can use the username() function in our triggers to log who has changed what values when ... when using a common user we would loose this functionallity, That's why we tried to do this.

A bit stange to me is the proposal of this sql user. And i've seen it in most of the posts i've been reading on these problems, because, the first thing in every book on Sql Security is to close down the SqlServer Logins, and here you have to use them !!

|||

Yes and no.

You force the users to connect as SQL logins and then you restrict these logins as much as possible, as opposed to a Windows account. You can configure a sql user to only allow read-only access to 1 column in 1 table out of the whole database if necessary. Disallow everything and then allow as necessary is an approach all of the security books will endorse. I find that the best books on SQL come from Wrox.

Kind regards

Scotty