I just change Administrator password. All services of SQL Server were
started, but my Databases became suspend. How can I solve this problem.
Thx,r u running in windows authentication or sql authentication'
--
Shaju Thomas
"Saroeurn Long" <saroeurn_long@.nida.gov.kh> wrote in message
news:u#HPcrboDHA.3288@.tk2msftngp13.phx.gbl...
> I just change Administrator password. All services of SQL Server were
> started, but my Databases became suspend. How can I solve this problem.
> Thx,
>|||I run in sql authentication
"Shaju" <answer@.hotmail.com> wrote in message
news:O0HZ44doDHA.2272@.tk2msftngp13.phx.gbl...
> r u running in windows authentication or sql authentication'
> --
> Shaju Thomas
> "Saroeurn Long" <saroeurn_long@.nida.gov.kh> wrote in message
> news:u#HPcrboDHA.3288@.tk2msftngp13.phx.gbl...
> > I just change Administrator password. All services of SQL Server were
> > started, but my Databases became suspend. How can I solve this problem.
> >
> > Thx,
> >
> >
>|||Is it suspend or suspect
--
Shaju Thomas
"Saroeurn Long" <saroeurn_long@.nida.gov.kh> wrote in message
news:#sw3raeoDHA.2000@.TK2MSFTNGP10.phx.gbl...
> I run in sql authentication
>
> "Shaju" <answer@.hotmail.com> wrote in message
> news:O0HZ44doDHA.2272@.tk2msftngp13.phx.gbl...
> > r u running in windows authentication or sql authentication'
> >
> > --
> > Shaju Thomas
> > "Saroeurn Long" <saroeurn_long@.nida.gov.kh> wrote in message
> > news:u#HPcrboDHA.3288@.tk2msftngp13.phx.gbl...
> > > I just change Administrator password. All services of SQL Server were
> > > started, but my Databases became suspend. How can I solve this
problem.
> > >
> > > Thx,
> > >
> > >
> >
> >
>|||Hello,
Did you have any jobs running on the old userid /
password ?
If so cancel them, as what could be happening is your db
was going though with a job when the password change come
up.
Check in managment your current processors.
>--Original Message--
>I just change Administrator password. All services of SQL
Server were
>started, but my Databases became suspend. How can I solve
this problem.
>Thx,
>
>.
>
Showing posts with label became. Show all posts
Showing posts with label became. Show all posts
Tuesday, March 27, 2012
Sunday, March 25, 2012
Database became suspect while logshipping and adding a datafile
Hello,
We do loshipping between two servers. Our database in primary server
grew, so we had to add a datafile to the primary database. However, we missed
a point. The directory, in which we created a datafile at primary site does
not exist
in the standby site. As another saying, we forgot to create the directory at
standby
site before adding the datafile to primary site. Now, the standby database
is in suspect mode, and we can not do anything. We tried sp_resetstatus,
creating the directory, and recovering the database again but nothing
changes, however the database becomes suspect again immediately, when we try
to restore the log. Please help.......
Erdinc,
Do a full backup on the primary server and restore that over your DR.
Make sure your path names are the same. Then continue as normal.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Erdinc the logshipping man wrote:
> Hello,
> We do loshipping between two servers. Our database in primary server
> grew, so we had to add a datafile to the primary database. However, we missed
> a point. The directory, in which we created a datafile at primary site does
> not exist
> in the standby site. As another saying, we forgot to create the directory at
> standby
> site before adding the datafile to primary site. Now, the standby database
> is in suspect mode, and we can not do anything. We tried sp_resetstatus,
> creating the directory, and recovering the database again but nothing
> changes, however the database becomes suspect again immediately, when we try
> to restore the log. Please help.......
We do loshipping between two servers. Our database in primary server
grew, so we had to add a datafile to the primary database. However, we missed
a point. The directory, in which we created a datafile at primary site does
not exist
in the standby site. As another saying, we forgot to create the directory at
standby
site before adding the datafile to primary site. Now, the standby database
is in suspect mode, and we can not do anything. We tried sp_resetstatus,
creating the directory, and recovering the database again but nothing
changes, however the database becomes suspect again immediately, when we try
to restore the log. Please help.......
Erdinc,
Do a full backup on the primary server and restore that over your DR.
Make sure your path names are the same. Then continue as normal.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Erdinc the logshipping man wrote:
> Hello,
> We do loshipping between two servers. Our database in primary server
> grew, so we had to add a datafile to the primary database. However, we missed
> a point. The directory, in which we created a datafile at primary site does
> not exist
> in the standby site. As another saying, we forgot to create the directory at
> standby
> site before adding the datafile to primary site. Now, the standby database
> is in suspect mode, and we can not do anything. We tried sp_resetstatus,
> creating the directory, and recovering the database again but nothing
> changes, however the database becomes suspect again immediately, when we try
> to restore the log. Please help.......
Database became suspect while logshipping and adding a datafile
Hello,
We do loshipping between two servers. Our database in primary server
grew, so we had to add a datafile to the primary database. However, we missed
a point. The directory, in which we created a datafile at primary site does
not exist
in the standby site. As another saying, we forgot to create the directory at
standby
site before adding the datafile to primary site. Now, the standby database
is in suspect mode, and we can not do anything. We tried sp_resetstatus,
creating the directory, and recovering the database again but nothing
changes, however the database becomes suspect again immediately, when we try
to restore the log. Please help.......Erdinc,
Do a full backup on the primary server and restore that over your DR.
Make sure your path names are the same. Then continue as normal.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Erdinc the logshipping man wrote:
> Hello,
> We do loshipping between two servers. Our database in primary server
> grew, so we had to add a datafile to the primary database. However, we missed
> a point. The directory, in which we created a datafile at primary site does
> not exist
> in the standby site. As another saying, we forgot to create the directory at
> standby
> site before adding the datafile to primary site. Now, the standby database
> is in suspect mode, and we can not do anything. We tried sp_resetstatus,
> creating the directory, and recovering the database again but nothing
> changes, however the database becomes suspect again immediately, when we try
> to restore the log. Please help.......|||Thanks for your help. Is not there a way of saving the database before making
a full
restore?
"Mark Allison" wrote:
> Erdinc,
> Do a full backup on the primary server and restore that over your DR.
> Make sure your path names are the same. Then continue as normal.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Erdinc the logshipping man wrote:
> > Hello,
> >
> > We do loshipping between two servers. Our database in primary server
> > grew, so we had to add a datafile to the primary database. However, we missed
> > a point. The directory, in which we created a datafile at primary site does
> > not exist
> > in the standby site. As another saying, we forgot to create the directory at
> > standby
> > site before adding the datafile to primary site. Now, the standby database
> > is in suspect mode, and we can not do anything. We tried sp_resetstatus,
> > creating the directory, and recovering the database again but nothing
> > changes, however the database becomes suspect again immediately, when we try
> > to restore the log. Please help.......
>
We do loshipping between two servers. Our database in primary server
grew, so we had to add a datafile to the primary database. However, we missed
a point. The directory, in which we created a datafile at primary site does
not exist
in the standby site. As another saying, we forgot to create the directory at
standby
site before adding the datafile to primary site. Now, the standby database
is in suspect mode, and we can not do anything. We tried sp_resetstatus,
creating the directory, and recovering the database again but nothing
changes, however the database becomes suspect again immediately, when we try
to restore the log. Please help.......Erdinc,
Do a full backup on the primary server and restore that over your DR.
Make sure your path names are the same. Then continue as normal.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Erdinc the logshipping man wrote:
> Hello,
> We do loshipping between two servers. Our database in primary server
> grew, so we had to add a datafile to the primary database. However, we missed
> a point. The directory, in which we created a datafile at primary site does
> not exist
> in the standby site. As another saying, we forgot to create the directory at
> standby
> site before adding the datafile to primary site. Now, the standby database
> is in suspect mode, and we can not do anything. We tried sp_resetstatus,
> creating the directory, and recovering the database again but nothing
> changes, however the database becomes suspect again immediately, when we try
> to restore the log. Please help.......|||Thanks for your help. Is not there a way of saving the database before making
a full
restore?
"Mark Allison" wrote:
> Erdinc,
> Do a full backup on the primary server and restore that over your DR.
> Make sure your path names are the same. Then continue as normal.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Erdinc the logshipping man wrote:
> > Hello,
> >
> > We do loshipping between two servers. Our database in primary server
> > grew, so we had to add a datafile to the primary database. However, we missed
> > a point. The directory, in which we created a datafile at primary site does
> > not exist
> > in the standby site. As another saying, we forgot to create the directory at
> > standby
> > site before adding the datafile to primary site. Now, the standby database
> > is in suspect mode, and we can not do anything. We tried sp_resetstatus,
> > creating the directory, and recovering the database again but nothing
> > changes, however the database becomes suspect again immediately, when we try
> > to restore the log. Please help.......
>
Database became suspect while logshipping and adding a datafile
Hello,
We do loshipping between two servers. Our database in primary server
grew, so we had to add a datafile to the primary database. However, we misse
d
a point. The directory, in which we created a datafile at primary site does
not exist
in the standby site. As another saying, we forgot to create the directory at
standby
site before adding the datafile to primary site. Now, the standby database
is in suspect mode, and we can not do anything. We tried sp_resetstatus,
creating the directory, and recovering the database again but nothing
changes, however the database becomes suspect again immediately, when we try
to restore the log. Please help.......Erdinc,
Do a full backup on the primary server and restore that over your DR.
Make sure your path names are the same. Then continue as normal.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Erdinc the logshipping man wrote:
> Hello,
> We do loshipping between two servers. Our database in primary server
> grew, so we had to add a datafile to the primary database. However, we mis
sed
> a point. The directory, in which we created a datafile at primary site do
es
> not exist
> in the standby site. As another saying, we forgot to create the directory
at
> standby
> site before adding the datafile to primary site. Now, the standby database
> is in suspect mode, and we can not do anything. We tried sp_resetstatus,
> creating the directory, and recovering the database again but nothing
> changes, however the database becomes suspect again immediately, when we t
ry
> to restore the log. Please help.......
We do loshipping between two servers. Our database in primary server
grew, so we had to add a datafile to the primary database. However, we misse
d
a point. The directory, in which we created a datafile at primary site does
not exist
in the standby site. As another saying, we forgot to create the directory at
standby
site before adding the datafile to primary site. Now, the standby database
is in suspect mode, and we can not do anything. We tried sp_resetstatus,
creating the directory, and recovering the database again but nothing
changes, however the database becomes suspect again immediately, when we try
to restore the log. Please help.......Erdinc,
Do a full backup on the primary server and restore that over your DR.
Make sure your path names are the same. Then continue as normal.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Erdinc the logshipping man wrote:
> Hello,
> We do loshipping between two servers. Our database in primary server
> grew, so we had to add a datafile to the primary database. However, we mis
sed
> a point. The directory, in which we created a datafile at primary site do
es
> not exist
> in the standby site. As another saying, we forgot to create the directory
at
> standby
> site before adding the datafile to primary site. Now, the standby database
> is in suspect mode, and we can not do anything. We tried sp_resetstatus,
> creating the directory, and recovering the database again but nothing
> changes, however the database becomes suspect again immediately, when we t
ry
> to restore the log. Please help.......
Subscribe to:
Posts (Atom)