Record Locks: users

Showing posts with label users. Show all posts

Friday, March 30, 2012

Recovery of database Immediately

Hi,
We are having a database and all times users are connected to the server and
using the database.
Suddenly the Server failed( Some problem crashed).
At this point of time I want all the users to connect asusual without having
a knowledge of that the server fail.
Is any way to handle this situation in SQL Server.
Please give me a solution as soon as Possible
Thanks,
HerbertHi,
You need to setup a failover clustering.
SQL Server 2000 failover clustering provides high availability support.
Incase of of an operating system failure or a crash, you can configure one
failover cluster to fail over to any other node in the failover cluster
configuration. This will minimize system downtime, thus providing high
server availability.
See Failover Clustering Architecture architecture topic in books online
Thanks
Hari
SQL Server MVP
"Herbert" <Herbert@.discussions.microsoft.com> wrote in message
news:B28C91A1-9414-4462-93D2-07F8D807E291@.microsoft.com...
> Hi,
> We are having a database and all times users are connected to the server
> and
> using the database.
> Suddenly the Server failed( Some problem crashed).
> At this point of time I want all the users to connect asusual without
> having
> a knowledge of that the server fail.
> Is any way to handle this situation in SQL Server.
> Please give me a solution as soon as Possible
> Thanks,
> Herbert|||Note that clustering is not an immediate failover. The cluster sw need to realize the one node is
down, start the services on the other node and then SQL server need to perform automatic recovery
for each database.
A more immediate failover (without even client disconnect) will be available in SLQ Server 2005 with
database mirroring.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:u7ep9ljdFHA.1684@.TK2MSFTNGP09.phx.gbl...
> Hi,
> You need to setup a failover clustering.
> SQL Server 2000 failover clustering provides high availability support. Incase of of an operating
> system failure or a crash, you can configure one failover cluster to fail over to any other node
> in the failover cluster configuration. This will minimize system downtime, thus providing high
> server availability.
> See Failover Clustering Architecture architecture topic in books online
> Thanks
> Hari
> SQL Server MVP
> "Herbert" <Herbert@.discussions.microsoft.com> wrote in message
> news:B28C91A1-9414-4462-93D2-07F8D807E291@.microsoft.com...
>> Hi,
>> We are having a database and all times users are connected to the server and
>> using the database.
>> Suddenly the Server failed( Some problem crashed).
>> At this point of time I want all the users to connect asusual without having
>> a knowledge of that the server fail.
>> Is any way to handle this situation in SQL Server.
>> Please give me a solution as soon as Possible
>> Thanks,
>> Herbert
>|||Hi tibor karaszi,
i s any way in SQL 2000 to Recover the database without disconnecting the
Client.
Thanks,
Herbert
"Tibor Karaszi" wrote:
> Note that clustering is not an immediate failover. The cluster sw need to realize the one node is
> down, start the services on the other node and then SQL server need to perform automatic recovery
> for each database.
> A more immediate failover (without even client disconnect) will be available in SLQ Server 2005 with
> database mirroring.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:u7ep9ljdFHA.1684@.TK2MSFTNGP09.phx.gbl...
> > Hi,
> >
> > You need to setup a failover clustering.
> >
> > SQL Server 2000 failover clustering provides high availability support. Incase of of an operating
> > system failure or a crash, you can configure one failover cluster to fail over to any other node
> > in the failover cluster configuration. This will minimize system downtime, thus providing high
> > server availability.
> >
> > See Failover Clustering Architecture architecture topic in books online
> >
> > Thanks
> > Hari
> > SQL Server MVP
> >
> > "Herbert" <Herbert@.discussions.microsoft.com> wrote in message
> > news:B28C91A1-9414-4462-93D2-07F8D807E291@.microsoft.com...
> >> Hi,
> >>
> >> We are having a database and all times users are connected to the server and
> >> using the database.
> >>
> >> Suddenly the Server failed( Some problem crashed).
> >> At this point of time I want all the users to connect asusual without having
> >> a knowledge of that the server fail.
> >>
> >> Is any way to handle this situation in SQL Server.
> >>
> >> Please give me a solution as soon as Possible
> >>
> >> Thanks,
> >> Herbert
> >
> >
>|||Assuming you mean if the SQL server service or whole machine stops, then no. Not with current
version of SQL server. In a disconnected world, most make the application handle this, though.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Herbert" <Herbert@.discussions.microsoft.com> wrote in message
news:22D3E638-27D9-41AA-A45F-2B1424386DA1@.microsoft.com...
> Hi tibor karaszi,
> i s any way in SQL 2000 to Recover the database without disconnecting the
> Client.
> Thanks,
> Herbert
>
> "Tibor Karaszi" wrote:
>> Note that clustering is not an immediate failover. The cluster sw need to realize the one node is
>> down, start the services on the other node and then SQL server need to perform automatic recovery
>> for each database.
>> A more immediate failover (without even client disconnect) will be available in SLQ Server 2005
>> with
>> database mirroring.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
>> news:u7ep9ljdFHA.1684@.TK2MSFTNGP09.phx.gbl...
>> > Hi,
>> >
>> > You need to setup a failover clustering.
>> >
>> > SQL Server 2000 failover clustering provides high availability support. Incase of of an
>> > operating
>> > system failure or a crash, you can configure one failover cluster to fail over to any other
>> > node
>> > in the failover cluster configuration. This will minimize system downtime, thus providing high
>> > server availability.
>> >
>> > See Failover Clustering Architecture architecture topic in books online
>> >
>> > Thanks
>> > Hari
>> > SQL Server MVP
>> >
>> > "Herbert" <Herbert@.discussions.microsoft.com> wrote in message
>> > news:B28C91A1-9414-4462-93D2-07F8D807E291@.microsoft.com...
>> >> Hi,
>> >>
>> >> We are having a database and all times users are connected to the server and
>> >> using the database.
>> >>
>> >> Suddenly the Server failed( Some problem crashed).
>> >> At this point of time I want all the users to connect asusual without having
>> >> a knowledge of that the server fail.
>> >>
>> >> Is any way to handle this situation in SQL Server.
>> >>
>> >> Please give me a solution as soon as Possible
>> >>
>> >> Thanks,
>> >> Herbert
>> >
>> >
>>sql

Monday, March 12, 2012

Recover database password

Hi all,

Is it possible to recover or find the password of database or resetting is the only option? I have a database that has a two users in the Users tab. How to find out the password for these?

Thanks,

Check out the answers of Nai-Dong Jin and me on this posthttp://forums.asp.net/t/1128538.aspx

|||

Hi Richard,

Thanks but I think you misunderstood my question. I am talking about the users that are there in the Security tab or the Users tab of SQL Server. This is more of an SQL Server administration question than an ASP.NET question.

|||

Okay in the security tab it's not possible to recover the password you have to reset it

|||

Thanks for confirming it.

Monday, February 20, 2012

record locking-is this all automatic?

Hi I am using SQL 2000 and will be working on a database that will have a lo
t
of users. I was wondering there may be a case were I need to lock a record,
like when one user will be modifying its' data. I was wondering how to do
this? I am using stored procedures. I will probably need to lock the recor
d
after a user does a select on a particular table. Also what are some of the
ways around this, would one be creating multiple duplicate tables so several
users can be modifying in a sense the same record at the same time?
Thanks.
--
Paul G
Software engineer.The common way is to create a Locks table. Then when you want to lock, for
example, a sales order, you would first check for a lock already there.
SELECT * FROM Locks
WHERE LockIdentifier = "SalesOrder4389"
and if you find a lock, then someone already is editing it. If you don't
find it, you can insert your own lock
INSERT INTO Locks (LockDate, LockedByUsername, LockedByFullname,
LockIdentifier, LockedAtMachineName)
VALUES (getdate(), 'paulg', 'Paul Ganonymous', 'SalesOrder4389', 'NERZHUL')
You lock other things by having different lock identifiers
e.g. "Invoice332", "Customer33", "Ticket 98", etc
The only downside is that if someone's PC crashes (or lose connection)
before they have a chance to clean up their lock, the lock will be dangling,
and you'll have to have an administrative screen to see locks and to remove
them. Also, whenever someone logs in, maybe clean up their locks then.
Alternativly, you can use the sp_getapplock/sp_releaseapplock built-in to
SQL Server. It works exactly like i described above, but it's built into SQL
Server, and SQL Sever will clean up any locks when a user disconnects (no
dangling locks)
To get a lock:
EXECUTE sp_getapplock 'SalesOrder4389', 'exclusive', 'Session', 0
To release a lock
EXECUTE sp_releaseapplock 'SalesOrder4389', 'Session'
With applocks, you could even go overboard and have
"Shared" lock if a user is only going to be looking at it (and others
can look too)
"Update" lock if a user is going to be changing something (others can
look, but nobody else can modify)
"Exclusive" lock means only i get it.
Important to note: "Application Locks" in SQL Server doesn't mean SQL Server
locks anything for you. You still have to check for locks by trying to get
an applock. If you don't get it, you have to write the code to not proceed
to viewing/editing.
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:1861A5DD-7AE7-44AA-82A6-49FA918CA31A@.microsoft.com...
> Hi I am using SQL 2000 and will be working on a database that will have a
> lot
> of users. I was wondering there may be a case were I need to lock a
> record,
> like when one user will be modifying its' data. I was wondering how to do
> this? I am using stored procedures. I will probably need to lock the
> record
> after a user does a select on a particular table. Also what are some of
> the
> ways around this, would one be creating multiple duplicate tables so
> several
> users can be modifying in a sense the same record at the same time?
> Thanks.
> --
> Paul G
> Software engineer.|||SQL Server books online covers transactions and locking.
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:1861A5DD-7AE7-44AA-82A6-49FA918CA31A@.microsoft.com...
> Hi I am using SQL 2000 and will be working on a database that will have a
> lot
> of users. I was wondering there may be a case were I need to lock a
> record,
> like when one user will be modifying its' data. I was wondering how to do
> this? I am using stored procedures. I will probably need to lock the
> record
> after a user does a select on a particular table. Also what are some of
> the
> ways around this, would one be creating multiple duplicate tables so
> several
> users can be modifying in a sense the same record at the same time?
> Thanks.
> --
> Paul G
> Software engineer.

record locking-is this all automatic?

Hi I am using SQL 2000 and will be working on a database that will have a lot
of users. I was wondering there may be a case were I need to lock a record,
like when one user will be modifying its' data. I was wondering how to do
this? I am using stored procedures. I will probably need to lock the record
after a user does a select on a particular table. Also what are some of the
ways around this, would one be creating multiple duplicate tables so several
users can be modifying in a sense the same record at the same time?
Thanks.
--
Paul G
Software engineer.The common way is to create a Locks table. Then when you want to lock, for
example, a sales order, you would first check for a lock already there.
SELECT * FROM Locks
WHERE LockIdentifier = "SalesOrder4389"
and if you find a lock, then someone already is editing it. If you don't
find it, you can insert your own lock
INSERT INTO Locks (LockDate, LockedByUsername, LockedByFullname,
LockIdentifier, LockedAtMachineName)
VALUES (getdate(), 'paulg', 'Paul Ganonymous', 'SalesOrder4389', 'NERZHUL')
You lock other things by having different lock identifiers
e.g. "Invoice332", "Customer33", "Ticket 98", etc
The only downside is that if someone's PC crashes (or lose connection)
before they have a chance to clean up their lock, the lock will be dangling,
and you'll have to have an administrative screen to see locks and to remove
them. Also, whenever someone logs in, maybe clean up their locks then.
Alternativly, you can use the sp_getapplock/sp_releaseapplock built-in to
SQL Server. It works exactly like i described above, but it's built into SQL
Server, and SQL Sever will clean up any locks when a user disconnects (no
dangling locks)
To get a lock:
EXECUTE sp_getapplock 'SalesOrder4389', 'exclusive', 'Session', 0
To release a lock
EXECUTE sp_releaseapplock 'SalesOrder4389', 'Session'
With applocks, you could even go overboard and have
"Shared" lock if a user is only going to be looking at it (and others
can look too)
"Update" lock if a user is going to be changing something (others can
look, but nobody else can modify)
"Exclusive" lock means only i get it.
Important to note: "Application Locks" in SQL Server doesn't mean SQL Server
locks anything for you. You still have to check for locks by trying to get
an applock. If you don't get it, you have to write the code to not proceed
to viewing/editing.
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:1861A5DD-7AE7-44AA-82A6-49FA918CA31A@.microsoft.com...
> Hi I am using SQL 2000 and will be working on a database that will have a
> lot
> of users. I was wondering there may be a case were I need to lock a
> record,
> like when one user will be modifying its' data. I was wondering how to do
> this? I am using stored procedures. I will probably need to lock the
> record
> after a user does a select on a particular table. Also what are some of
> the
> ways around this, would one be creating multiple duplicate tables so
> several
> users can be modifying in a sense the same record at the same time?
> Thanks.
> --
> Paul G
> Software engineer.|||SQL Server books online covers transactions and locking.
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:1861A5DD-7AE7-44AA-82A6-49FA918CA31A@.microsoft.com...
> Hi I am using SQL 2000 and will be working on a database that will have a
> lot
> of users. I was wondering there may be a case were I need to lock a
> record,
> like when one user will be modifying its' data. I was wondering how to do
> this? I am using stored procedures. I will probably need to lock the
> record
> after a user does a select on a particular table. Also what are some of
> the
> ways around this, would one be creating multiple duplicate tables so
> several
> users can be modifying in a sense the same record at the same time?
> Thanks.
> --
> Paul G
> Software engineer.

Friday, March 30, 2012

Recovery of database Immediately

Recovery of database Immediately

Recovery of database Immediately

Monday, March 12, 2012

Recover database password

Monday, February 20, 2012

record locking-is this all automatic?

record locking-is this all automatic?

Record Locks

Blog Archive

About Me