I have a web based application that could have many clients/users.
Should I create a user account for each client browsing the web site.
They can only access certain data after they have been verified from a
user table. They use a common database login to access the data. This
is planned to be a public free site. So hopefully the client count
will be high.create login that the application uses to get to the DB... instead of
creating a login for each user.|||Ok thats they wey I'm approaching it now.|||Are you using an ODBC or DSN less, either way assuming the users should
have the same permissions then 1 user is created in the db with a certain
level of permissions. You may also have an admin section , therfore the
admin user may have a different set of permissions
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
"nathan001" <nathan@.thelosthorizon.com> wrote in message
news:1143477924.849156.7120@.z34g2000cwc.googlegroups.com...
> Ok thats they wey I'm approaching it now.
>|||From what you describe, it sounds like you need ASP.NET Forms
Authentication. At a minimum, you will need to implement a table with one
row for each subscriber.
ASP.NET Forms Authentication Overview
http://msdn2.microsoft.com/en-us/library/7t6b43z4.aspx
As for database (server) logins, you will need to implement one login for
each type of user (admin, subscriber, guest, etc.) and then use SQL Server
role based permissions to restrict each user's access to specific database
objects.
SQL Server 2000 Administrator's Pocket Consultant - Chapter 5: SQL Server
2000 Security
http://www.microsoft.com/technet/pr...s/c05ppcsq.mspx
SQL Server 2000 Operations Guide: Security Administration
http://www.microsoft.com/technet/pr...in/sqlops3.mspx
SQL Server 2000 Resource Kit - Chapter 10: Implementing Security
http://www.microsoft.com/technet/pr...fr=true
If this database is hosted by a 3rd party internet service provider, then
you will need to coordinate with the server administrator to setup the
logins and permissions, becuase these configurations require server admin
rights. If your ISP provides this functionality through their website
management tool, then that's great, but that would be exceptional.
"nathan001" <nathan@.thelosthorizon.com> wrote in message
news:1143473709.083112.37370@.i40g2000cwc.googlegroups.com...
>I have a web based application that could have many clients/users.
> Should I create a user account for each client browsing the web site.
> They can only access certain data after they have been verified from a
> user table. They use a common database login to access the data. This
> is planned to be a public free site. So hopefully the client count
> will be high.
>
Showing posts with label clients. Show all posts
Showing posts with label clients. Show all posts
Friday, February 17, 2012
database locking malaise / restarting SQL Server fine points
Our company, primarily a software dev house, also manages an SQL Server
DB for one of our clients. A few days ago, we experienced repeated
timeouts in our .NET web and desktop applications, which threw this
error:
System.Data.SqlClient.SqlException: Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is
not responding.
The timeouts seemed to be caused by locks placed on the database by a
stored proc which adds a new customers, when an order is placed. These
locks could be seen in Enterprise Manager / Management / Current
Activity / Locks, some of the locks' properties pointing to this stored
proc.
Now the strange part: we rebooted the server in question, which had no
apparent effect, ie still lots of locks, timeouts, etc. But a few
hours later, we pushed "Stop" and "Start" in the SQL Server Service
Manager - and everything magically started working again, no further
problems since then (24 hours).
So my key question: when you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
If the answer to these questions is yes, then we can rest a bit easy,
just say the DB got screwy, we had to restart it, but otherwise, we
have some serious investigating to do, to try to prevent this
recurring.
Thanks very much for any advice.
Harlan Wood
sfk3ml4x9w35
_____at_____
thegoldensun.comwhen you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
--both do the same thing, there is nothing that SQL will retain the
locks..in any case, SQL will release the locks..
DB for one of our clients. A few days ago, we experienced repeated
timeouts in our .NET web and desktop applications, which threw this
error:
System.Data.SqlClient.SqlException: Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is
not responding.
The timeouts seemed to be caused by locks placed on the database by a
stored proc which adds a new customers, when an order is placed. These
locks could be seen in Enterprise Manager / Management / Current
Activity / Locks, some of the locks' properties pointing to this stored
proc.
Now the strange part: we rebooted the server in question, which had no
apparent effect, ie still lots of locks, timeouts, etc. But a few
hours later, we pushed "Stop" and "Start" in the SQL Server Service
Manager - and everything magically started working again, no further
problems since then (24 hours).
So my key question: when you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
If the answer to these questions is yes, then we can rest a bit easy,
just say the DB got screwy, we had to restart it, but otherwise, we
have some serious investigating to do, to try to prevent this
recurring.
Thanks very much for any advice.
Harlan Wood
sfk3ml4x9w35
_____at_____
thegoldensun.comwhen you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
--both do the same thing, there is nothing that SQL will retain the
locks..in any case, SQL will release the locks..
database locking malaise / restarting SQL Server fine points
Our company, primarily a software dev house, also manages an SQL Server
DB for one of our clients. A few days ago, we experienced repeated
timeouts in our .NET web and desktop applications, which threw this
error:
System.Data.SqlClient.SqlException: Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is
not responding.
The timeouts seemed to be caused by locks placed on the database by a
stored proc which adds a new customers, when an order is placed. These
locks could be seen in Enterprise Manager / Management / Current
Activity / Locks, some of the locks' properties pointing to this stored
proc.
Now the strange part: we rebooted the server in question, which had no
apparent effect, ie still lots of locks, timeouts, etc. But a few
hours later, we pushed "Stop" and "Start" in the SQL Server Service
Manager - and everything magically started working again, no further
problems since then (24 hours).
So my key question: when you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
If the answer to these questions is yes, then we can rest a bit easy,
just say the DB got screwy, we had to restart it, but otherwise, we
have some serious investigating to do, to try to prevent this
recurring.
Thanks very much for any advice.
Harlan Wood
sfk3ml4x9w35
_____at_____
thegoldensun.com
when you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
--both do the same thing, there is nothing that SQL will retain the
locks..in any case, SQL will release the locks..
DB for one of our clients. A few days ago, we experienced repeated
timeouts in our .NET web and desktop applications, which threw this
error:
System.Data.SqlClient.SqlException: Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is
not responding.
The timeouts seemed to be caused by locks placed on the database by a
stored proc which adds a new customers, when an order is placed. These
locks could be seen in Enterprise Manager / Management / Current
Activity / Locks, some of the locks' properties pointing to this stored
proc.
Now the strange part: we rebooted the server in question, which had no
apparent effect, ie still lots of locks, timeouts, etc. But a few
hours later, we pushed "Stop" and "Start" in the SQL Server Service
Manager - and everything magically started working again, no further
problems since then (24 hours).
So my key question: when you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
If the answer to these questions is yes, then we can rest a bit easy,
just say the DB got screwy, we had to restart it, but otherwise, we
have some serious investigating to do, to try to prevent this
recurring.
Thanks very much for any advice.
Harlan Wood
sfk3ml4x9w35
_____at_____
thegoldensun.com
when you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
--both do the same thing, there is nothing that SQL will retain the
locks..in any case, SQL will release the locks..
database locking malaise / restarting SQL Server fine points
Our company, primarily a software dev house, also manages an SQL Server
DB for one of our clients. A few days ago, we experienced repeated
timeouts in our .NET web and desktop applications, which threw this
error:
System.Data.SqlClient.SqlException: Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is
not responding.
The timeouts seemed to be caused by locks placed on the database by a
stored proc which adds a new customers, when an order is placed. These
locks could be seen in Enterprise Manager / Management / Current
Activity / Locks, some of the locks' properties pointing to this stored
proc.
Now the strange part: we rebooted the server in question, which had no
apparent effect, ie still lots of locks, timeouts, etc. But a few
hours later, we pushed "Stop" and "Start" in the SQL Server Service
Manager - and everything magically started working again, no further
problems since then (24 hours).
So my key question: when you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
If the answer to these questions is yes, then we can rest a bit easy,
just say the DB got screwy, we had to restart it, but otherwise, we
have some serious investigating to do, to try to prevent this
recurring.
Thanks very much for any advice.
Harlan Wood
sfk3ml4x9w35
_____at_____
thegoldensun.comwhen you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
--both do the same thing, there is nothing that SQL will retain the
locks..in any case, SQL will release the locks..
DB for one of our clients. A few days ago, we experienced repeated
timeouts in our .NET web and desktop applications, which threw this
error:
System.Data.SqlClient.SqlException: Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is
not responding.
The timeouts seemed to be caused by locks placed on the database by a
stored proc which adds a new customers, when an order is placed. These
locks could be seen in Enterprise Manager / Management / Current
Activity / Locks, some of the locks' properties pointing to this stored
proc.
Now the strange part: we rebooted the server in question, which had no
apparent effect, ie still lots of locks, timeouts, etc. But a few
hours later, we pushed "Stop" and "Start" in the SQL Server Service
Manager - and everything magically started working again, no further
problems since then (24 hours).
So my key question: when you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
If the answer to these questions is yes, then we can rest a bit easy,
just say the DB got screwy, we had to restart it, but otherwise, we
have some serious investigating to do, to try to prevent this
recurring.
Thanks very much for any advice.
Harlan Wood
sfk3ml4x9w35
_____at_____
thegoldensun.comwhen you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
--both do the same thing, there is nothing that SQL will retain the
locks..in any case, SQL will release the locks..
Database lock makes all Clients hold
We are using SQL2000 with SP3, Windows 2000 Svr Std with SP4
Sometimes, we found all clients had no response. Later, we found that the
all clients are waiting response from sql server.
Then in querry analyzer, we use this script:
select * FROM master..sysprocesses where status='sleeping' AND
waittype=0x000 AND open_tran > 0
and then we found out one computer is locking and after request that
computer logout the program, then, all clients can run again.
However, I have no idea why this case happen and I am still searching what's
the meaning the about select statement.
Can anyone help me?
IvanTalk to the person who wrote that program, as you have a bug in the application because it doesn't
and the transaction properly.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Ivan Kan" <ivankan@.no-ip.com> wrote in message news:uJg1Qb3lDHA.1740@.TK2MSFTNGP12.phx.gbl...
> We are using SQL2000 with SP3, Windows 2000 Svr Std with SP4
> Sometimes, we found all clients had no response. Later, we found that the
> all clients are waiting response from sql server.
> Then in querry analyzer, we use this script:
> select * FROM master..sysprocesses where status='sleeping' AND
> waittype=0x000 AND open_tran > 0
> and then we found out one computer is locking and after request that
> computer logout the program, then, all clients can run again.
> However, I have no idea why this case happen and I am still searching what's
> the meaning the about select statement.
> Can anyone help me?
> Ivan
>
>
Sometimes, we found all clients had no response. Later, we found that the
all clients are waiting response from sql server.
Then in querry analyzer, we use this script:
select * FROM master..sysprocesses where status='sleeping' AND
waittype=0x000 AND open_tran > 0
and then we found out one computer is locking and after request that
computer logout the program, then, all clients can run again.
However, I have no idea why this case happen and I am still searching what's
the meaning the about select statement.
Can anyone help me?
IvanTalk to the person who wrote that program, as you have a bug in the application because it doesn't
and the transaction properly.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Ivan Kan" <ivankan@.no-ip.com> wrote in message news:uJg1Qb3lDHA.1740@.TK2MSFTNGP12.phx.gbl...
> We are using SQL2000 with SP3, Windows 2000 Svr Std with SP4
> Sometimes, we found all clients had no response. Later, we found that the
> all clients are waiting response from sql server.
> Then in querry analyzer, we use this script:
> select * FROM master..sysprocesses where status='sleeping' AND
> waittype=0x000 AND open_tran > 0
> and then we found out one computer is locking and after request that
> computer logout the program, then, all clients can run again.
> However, I have no idea why this case happen and I am still searching what's
> the meaning the about select statement.
> Can anyone help me?
> Ivan
>
>
Subscribe to:
Posts (Atom)