Showing posts with label article. Show all posts
Showing posts with label article. Show all posts

Thursday, March 29, 2012

database move

I recently moved a database and its transaction log file to another drive due
to space issues. I followed the kb article 224071 on how to move a user
database and it appears that it worked correctly.
However, now the database comes up as "read-only" and if I view the
properties of the db and try to remove the "read-only" designation, I get an
error that it can't.
Any thoughts?
Robert
Hi Robert
Check the SQL Server error log to see if there is any information on the
problem. You may also want to check that the readonly attribute is not set on
the mdf and ldf files.
John
"Robert Gandrud" wrote:

> I recently moved a database and its transaction log file to another drive due
> to space issues. I followed the kb article 224071 on how to move a user
> database and it appears that it worked correctly.
> However, now the database comes up as "read-only" and if I view the
> properties of the db and try to remove the "read-only" designation, I get an
> error that it can't.
> Any thoughts?
> Robert
|||In the move of this large db/log to another volume, the sql service account
that starts mssqlserver didn't have specific rights to the new location. I
gave it full control to the new db location and rebooted.
The error log then stated that it performed a full recovery on that db,
which it couldn't do before. I was then able to remove the Read-only
property in the db properties in Ent. Mgr.
Thanks for your help.
Also, for some reason, I have about a 30GB log file. I was under the
understanding that if I backup the transaction log, that it would commit the
transactions and severly reduce my log file size, but that didn't seem to
work.
Any thoughts on that?
Thanks again,
Robert
"John Bell" wrote:
[vbcol=seagreen]
> Hi Robert
> Check the SQL Server error log to see if there is any information on the
> problem. You may also want to check that the readonly attribute is not set on
> the mdf and ldf files.
> John
> "Robert Gandrud" wrote:
|||Hi
Check out
http://msdn.microsoft.com/library/de...r_da2_1uzr.asp
on shrinking the transaction log.
John
"Robert Gandrud" wrote:
[vbcol=seagreen]
> In the move of this large db/log to another volume, the sql service account
> that starts mssqlserver didn't have specific rights to the new location. I
> gave it full control to the new db location and rebooted.
> The error log then stated that it performed a full recovery on that db,
> which it couldn't do before. I was then able to remove the Read-only
> property in the db properties in Ent. Mgr.
> Thanks for your help.
> Also, for some reason, I have about a 30GB log file. I was under the
> understanding that if I backup the transaction log, that it would commit the
> transactions and severly reduce my log file size, but that didn't seem to
> work.
> Any thoughts on that?
> Thanks again,
> Robert
> "John Bell" wrote:

database move

I recently moved a database and its transaction log file to another drive du
e
to space issues. I followed the kb article 224071 on how to move a user
database and it appears that it worked correctly.
However, now the database comes up as "read-only" and if I view the
properties of the db and try to remove the "read-only" designation, I get an
error that it can't.
Any thoughts'
RobertHi Robert
Check the SQL Server error log to see if there is any information on the
problem. You may also want to check that the readonly attribute is not set o
n
the mdf and ldf files.
John
"Robert Gandrud" wrote:

> I recently moved a database and its transaction log file to another drive
due
> to space issues. I followed the kb article 224071 on how to move a user
> database and it appears that it worked correctly.
> However, now the database comes up as "read-only" and if I view the
> properties of the db and try to remove the "read-only" designation, I get
an
> error that it can't.
> Any thoughts'
> Robert|||In the move of this large db/log to another volume, the sql service account
that starts mssqlserver didn't have specific rights to the new location. I
gave it full control to the new db location and rebooted.
The error log then stated that it performed a full recovery on that db,
which it couldn't do before. I was then able to remove the Read-only
property in the db properties in Ent. Mgr.
Thanks for your help.
Also, for some reason, I have about a 30GB log file. I was under the
understanding that if I backup the transaction log, that it would commit the
transactions and severly reduce my log file size, but that didn't seem to
work.
Any thoughts on that?
Thanks again,
Robert
"John Bell" wrote:
[vbcol=seagreen]
> Hi Robert
> Check the SQL Server error log to see if there is any information on the
> problem. You may also want to check that the readonly attribute is not set
on
> the mdf and ldf files.
> John
> "Robert Gandrud" wrote:
>|||Hi
Check out
http://msdn.microsoft.com/library/d...r />
_1uzr.asp
on shrinking the transaction log.
John
"Robert Gandrud" wrote:
[vbcol=seagreen]
> In the move of this large db/log to another volume, the sql service accoun
t
> that starts mssqlserver didn't have specific rights to the new location.
I
> gave it full control to the new db location and rebooted.
> The error log then stated that it performed a full recovery on that db,
> which it couldn't do before. I was then able to remove the Read-only
> property in the db properties in Ent. Mgr.
> Thanks for your help.
> Also, for some reason, I have about a 30GB log file. I was under the
> understanding that if I backup the transaction log, that it would commit t
he
> transactions and severly reduce my log file size, but that didn't seem to
> work.
> Any thoughts on that?
> Thanks again,
> Robert
> "John Bell" wrote:
>sql

database move

I recently moved a database and its transaction log file to another drive due
to space issues. I followed the kb article 224071 on how to move a user
database and it appears that it worked correctly.
However, now the database comes up as "read-only" and if I view the
properties of the db and try to remove the "read-only" designation, I get an
error that it can't.
Any thoughts'
RobertHi Robert
Check the SQL Server error log to see if there is any information on the
problem. You may also want to check that the readonly attribute is not set on
the mdf and ldf files.
John
"Robert Gandrud" wrote:
> I recently moved a database and its transaction log file to another drive due
> to space issues. I followed the kb article 224071 on how to move a user
> database and it appears that it worked correctly.
> However, now the database comes up as "read-only" and if I view the
> properties of the db and try to remove the "read-only" designation, I get an
> error that it can't.
> Any thoughts'
> Robert|||In the move of this large db/log to another volume, the sql service account
that starts mssqlserver didn't have specific rights to the new location. I
gave it full control to the new db location and rebooted.
The error log then stated that it performed a full recovery on that db,
which it couldn't do before. I was then able to remove the Read-only
property in the db properties in Ent. Mgr.
Thanks for your help.
Also, for some reason, I have about a 30GB log file. I was under the
understanding that if I backup the transaction log, that it would commit the
transactions and severly reduce my log file size, but that didn't seem to
work.
Any thoughts on that?
Thanks again,
Robert
"John Bell" wrote:
> Hi Robert
> Check the SQL Server error log to see if there is any information on the
> problem. You may also want to check that the readonly attribute is not set on
> the mdf and ldf files.
> John
> "Robert Gandrud" wrote:
> > I recently moved a database and its transaction log file to another drive due
> > to space issues. I followed the kb article 224071 on how to move a user
> > database and it appears that it worked correctly.
> >
> > However, now the database comes up as "read-only" and if I view the
> > properties of the db and try to remove the "read-only" designation, I get an
> > error that it can't.
> >
> > Any thoughts'
> >
> > Robert|||Hi
Check out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_1uzr.asp
on shrinking the transaction log.
John
"Robert Gandrud" wrote:
> In the move of this large db/log to another volume, the sql service account
> that starts mssqlserver didn't have specific rights to the new location. I
> gave it full control to the new db location and rebooted.
> The error log then stated that it performed a full recovery on that db,
> which it couldn't do before. I was then able to remove the Read-only
> property in the db properties in Ent. Mgr.
> Thanks for your help.
> Also, for some reason, I have about a 30GB log file. I was under the
> understanding that if I backup the transaction log, that it would commit the
> transactions and severly reduce my log file size, but that didn't seem to
> work.
> Any thoughts on that?
> Thanks again,
> Robert
> "John Bell" wrote:
> > Hi Robert
> >
> > Check the SQL Server error log to see if there is any information on the
> > problem. You may also want to check that the readonly attribute is not set on
> > the mdf and ldf files.
> >
> > John
> >
> > "Robert Gandrud" wrote:
> >
> > > I recently moved a database and its transaction log file to another drive due
> > > to space issues. I followed the kb article 224071 on how to move a user
> > > database and it appears that it worked correctly.
> > >
> > > However, now the database comes up as "read-only" and if I view the
> > > properties of the db and try to remove the "read-only" designation, I get an
> > > error that it can't.
> > >
> > > Any thoughts'
> > >
> > > Robertsql

Tuesday, March 27, 2012

Database Modelling in UML

The Methods & Tools newsletter has released in its archive section the
article "Database Modelling in UML". This article offers a step by step
approach to transform a UML object-oriented class model in a purely
relational database.

http://www.methodsandtools.com/archive/archive.php?id=9Franco Martinig via SQLMonster.com wrote:

> The Methods & Tools newsletter has released in its archive section the
> article "Database Modelling in UML". This article offers a step by step
> approach to transform a UML object-oriented class model in a purely
> relational database.
> http://www.methodsandtools.com/archive/archive.php?id=9

The article is rather difficult to believe after lines like this:

"The relational model only offers a public data access model. All data is
equally exposed and open to any process to update, query or manipulate it.
Information hiding is unknown."

This statement is true in the same sense that it is true that you have to
turn a crank on the front of a car to get it started. It depends on
whether or not you are Rip Van Winkle.

I kept reading looking for a qualifier, but the mistake is repeated later
on, "The relational model exposes all data equally, with limited support
for associating behaviour with data elements through triggers, indexes and
constraints."

--
Kenneth Downs
Secure Data Software, Inc.
(Ken)nneth@.(Sec)ure(Dat)a(.com)|||Perhaps for another perspective, read:
http://www.dbdebunk.com/page/page/622916.htm
http://www.dbdebunk.com/page/page/622867.htm

--
Anith

Sunday, March 25, 2012

database mirroring error? -- Scenario HASL2.3

HASL2.3 refers to the scenario within this article of a Mirror Server Loss
followed by Witness Loss:
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
We have SQL Server 2005 Standard Edition, SP1, + hotfix 2153 installed on
Win2k3 R2 servers.
We were planning on upgrading some hardware (adding a disk array) to our
secondary site (datacenter B) and I thought that it would be a good time to
test a couple of database mirroring scenarios.
I set up database mirroring on a test database. The primary was on a server
in datacenter A. I set up a witness on a box located in the test lab at our
office . With this setup I was running database mirroring in a high safety
with automatic failover (synchronous) mode.
Mirroring was working. I manually failed over and back. No problem there.
They shut down the server within datacenter B. The server in datacenter A
could still talk to my watcher box in the lab in our office. The primary
database on the server within datacenter A stayed available but it showed
that the mirrored server was disconnected (as expected).
I stopped SQL Server on the watch box in the lab. At that point the primary
database on the server within datacenter A became unavailable (Principal,
Disconnected / In Recovery). The database was unavailable (as expected).
The fly in the ointment:
They finished working on the server within datacenter B. The box came back
up without any issues. The other databases on that server are intact and
everything looks good. SQL Server is running normally...BUT the database
mirroring did not resume. The article indicates that "If Server B is
restored first, mirroring resumes, although no automatic failover is
possible without a witness." I did NOT experience this. My "Server B" has
been back online for 45 minutes and its status still shows as "Principal,
Disconnected / In Recovery" on Server A (datacenter A) and "Mirror,
Disconnected / In Recovery" on Server B (datacenter B).
Has anyone else experienced this scenario? I could try turning on the watch
server again, but I would like to see the two servers (principal and mirror)
synchronize on their own. I realize that automatic failover will not be
possible until I bring the watch back online, but the mirrored database(s)
should be available now that both the principal and mirror are back online.
Right?
--
Keith Kratochvilmy understanding of the situation is that when both or even one of the
datacenters comes online, it cannot automatically failover because both
are unable to deciede which of them is the actual principal(beacuse of
the link between them is not there) unless there is a witness as u
said. if both come online both try to actively become the principal and
hence the same problem
if u add a witness it should solve your problem or u can manually make
the mirror as your principal
Keith Kratochvil wrote:
> HASL2.3 refers to the scenario within this article of a Mirror Server Loss
> followed by Witness Loss:
> http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
>
> We have SQL Server 2005 Standard Edition, SP1, + hotfix 2153 installed on
> Win2k3 R2 servers.
> We were planning on upgrading some hardware (adding a disk array) to our
> secondary site (datacenter B) and I thought that it would be a good time to
> test a couple of database mirroring scenarios.
> I set up database mirroring on a test database. The primary was on a server
> in datacenter A. I set up a witness on a box located in the test lab at our
> office . With this setup I was running database mirroring in a high safety
> with automatic failover (synchronous) mode.
> Mirroring was working. I manually failed over and back. No problem there.
> They shut down the server within datacenter B. The server in datacenter A
> could still talk to my watcher box in the lab in our office. The primary
> database on the server within datacenter A stayed available but it showed
> that the mirrored server was disconnected (as expected).
>
> I stopped SQL Server on the watch box in the lab. At that point the primary
> database on the server within datacenter A became unavailable (Principal,
> Disconnected / In Recovery). The database was unavailable (as expected).
>
> The fly in the ointment:
> They finished working on the server within datacenter B. The box came back
> up without any issues. The other databases on that server are intact and
> everything looks good. SQL Server is running normally...BUT the database
> mirroring did not resume. The article indicates that "If Server B is
> restored first, mirroring resumes, although no automatic failover is
> possible without a witness." I did NOT experience this. My "Server B" has
> been back online for 45 minutes and its status still shows as "Principal,
> Disconnected / In Recovery" on Server A (datacenter A) and "Mirror,
> Disconnected / In Recovery" on Server B (datacenter B).
>
> Has anyone else experienced this scenario? I could try turning on the watch
> server again, but I would like to see the two servers (principal and mirror)
> synchronize on their own. I realize that automatic failover will not be
> possible until I bring the watch back online, but the mirrored database(s)
> should be available now that both the principal and mirror are back online.
> Right?
> --
> Keith Kratochvil|||Please re-read my post.
I had an automatic failover setup configured between data center A
(Primary), data center B (Mirror), and our office (Witness).
I wanted to test what would happen if we lost the Mirror and then the
Witness.
When we lost the Mirror (because it was down for hardware maintenance)
everything kept running because the Witness was still available.
I shut down the Witness and the Primary stopped working (as expected).
The hardware upgrade on the Mirror was complete and we brought that machine
back online. At this point we had
Primary server: on
Mirror server: on
Witness server: off
Mirroring: broken
Expected Result: Primary and Mirror would start "talking" to each other,
synchronize any changes , and come back online.
Actual Result: the database that I mirrored (MirroredDemo) is unavailable.
When I try to connect to or use that database on the primary I receive the
following message:
"Database MirroredDemo is enabled for Database Mirroring, but neither the
partner nor witness server instances are available: the database cannot be
opened.
"
Current situation:
(Via SSMS) The database is showing that it is "Principal, Disconnected / In
Recovery" within the database list. If I look at the database mirroring
properties the status text is: "No connection: cannot connect to the mirror
or witness server instances." In this state the database is UNAVAILABLE
If I bring the witness back online the databae shows that it is "Principal,
Disconnected." Database Mirroring is not functioning. The good news is
that I can access the database. The bad news is that I cannot fail over. I
receive this message when I try to fail over: "Msg 1422, Level 16, State 2,
Line 1
The mirror server instance is not caught up to the recent changes to
database "MirroredDemo". Unable to fail over."
I thought that I might need to resume the mirroring session. With the
witness server still offline, I tried to execute this command to resume
mirroring: "ALTER DATABASE mirroreddemo SET PARTNER RESUME"
No luck.
I brought the witness online. The status (as shown within the database list
of SSMS) is still "Principal/Disconnected."
I tried resuming mirroring (again, with the command "ALTER DATABASE
mirroreddemo SET PARTNER RESUME") but that did not work either.
At this point the P,M, and W are all online.
Still, the status within the database mirroring properties on the principal
shows "No connection: cannot connect to the mirror or witness server
instances"
I am stumped. Why didn't it (mirroring) come back online and start working
after all the servers are back online?
In researching this issue I have discovered the following articles:
http://groups.google.com/group/microsoft.public.sqlserver.server/browse_thread/thread/9211508f9b08072d/1de7d680cfd4d127?lnk=st&q=&rnum=2&hl=en#1de7d680cfd4d127
http://forums.microsoft.com/MSDN/showpost.aspx?postid=441900&siteid=1
We are in a similar situation as Muhammad. We have a few servers with more
than 100 databases on them. We are hoping to use mirroring as a high
availability solution to keep servers in different data centers in synch.
After reading those posts I am concerned that database mirroring might not
be able to meet our needs.
When we were running on SQL2k we used Replication. That is a path I would
rather not revisit.
Can anyone offer a solution to these problems
--mirroring not resuming properly on this one database
--mirroring not working (playing nice) on a server with many databases
Keith Kratochvil
"Udit Ghai" <ghai.udit@.gmail.com> wrote in message
news:1160458659.575183.108970@.i3g2000cwc.googlegroups.com...
> my understanding of the situation is that when both or even one of the
> datacenters comes online, it cannot automatically failover because both
> are unable to deciede which of them is the actual principal(beacuse of
> the link between them is not there) unless there is a witness as u
> said. if both come online both try to actively become the principal and
> hence the same problem
> if u add a witness it should solve your problem or u can manually make
> the mirror as your principal
> Keith Kratochvil wrote:
>> HASL2.3 refers to the scenario within this article of a Mirror Server
>> Loss
>> followed by Witness Loss:
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
>>
>> We have SQL Server 2005 Standard Edition, SP1, + hotfix 2153 installed on
>> Win2k3 R2 servers.
>> We were planning on upgrading some hardware (adding a disk array) to our
>> secondary site (datacenter B) and I thought that it would be a good time
>> to
>> test a couple of database mirroring scenarios.
>> I set up database mirroring on a test database. The primary was on a
>> server
>> in datacenter A. I set up a witness on a box located in the test lab at
>> our
>> office . With this setup I was running database mirroring in a high
>> safety
>> with automatic failover (synchronous) mode.
>> Mirroring was working. I manually failed over and back. No problem
>> there.
>> They shut down the server within datacenter B. The server in datacenter
>> A
>> could still talk to my watcher box in the lab in our office. The primary
>> database on the server within datacenter A stayed available but it showed
>> that the mirrored server was disconnected (as expected).
>>
>> I stopped SQL Server on the watch box in the lab. At that point the
>> primary
>> database on the server within datacenter A became unavailable (Principal,
>> Disconnected / In Recovery). The database was unavailable (as expected).
>>
>> The fly in the ointment:
>> They finished working on the server within datacenter B. The box came
>> back
>> up without any issues. The other databases on that server are intact and
>> everything looks good. SQL Server is running normally...BUT the
>> database
>> mirroring did not resume. The article indicates that "If Server B is
>> restored first, mirroring resumes, although no automatic failover is
>> possible without a witness." I did NOT experience this. My "Server B"
>> has
>> been back online for 45 minutes and its status still shows as "Principal,
>> Disconnected / In Recovery" on Server A (datacenter A) and "Mirror,
>> Disconnected / In Recovery" on Server B (datacenter B).
>>
>> Has anyone else experienced this scenario? I could try turning on the
>> watch
>> server again, but I would like to see the two servers (principal and
>> mirror)
>> synchronize on their own. I realize that automatic failover will not be
>> possible until I bring the watch back online, but the mirrored
>> database(s)
>> should be available now that both the principal and mirror are back
>> online.
>> Right?
>> --
>> Keith Kratochvil
>|||Hello?
Is anyone out there?
More importantly, does anyone have any ideas, suggestions, or helpful
comments?
--
Keith Kratochvil

Thursday, March 22, 2012

database mirroring - correction to technet article requested

This is a very informative document:
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
However, I would like to request one correction:
Step 4 under "Setup and Security" indicates that you have to specify the
partner and the witness. It tells you to to issue "ALTER DATABASE...SET
PARTNER..." on the intended principal first. Then you execute the same
command on the intended mirror.
Problem:
I could not get it to work that way. When I set up Mirroring in my
environment (9.0.2153) I had to execute the command on the mirror first then
against the primary.
--
Keith KratochvilHi Keith!
The early revisions of this document, I believe was based on a beta, so it is possible that the
behavior changed between that and production. Did you do a feedback at the bottom of that page?
(I see the same thing, btw, that you have to do mirror before principal...)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
> This is a very informative document:
> http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
>
> However, I would like to request one correction:
> Step 4 under "Setup and Security" indicates that you have to specify the partner and the witness.
> It tells you to to issue "ALTER DATABASE...SET PARTNER..." on the intended principal first. Then
> you execute the same command on the intended mirror.
> Problem:
> I could not get it to work that way. When I set up Mirroring in my environment (9.0.2153) I had
> to execute the command on the mirror first then against the primary.
>
> --
> Keith Kratochvil
>
>|||argh. "Please limit comments to 256 characters"
I will try to be more to the point.
--
Keith Kratochvil
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:es8ewZH9GHA.3348@.TK2MSFTNGP03.phx.gbl...
> Hi Keith!
> The early revisions of this document, I believe was based on a beta, so it
> is possible that the behavior changed between that and production. Did you
> do a feedback at the bottom of that page?
> (I see the same thing, btw, that you have to do mirror before
> principal...)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
> news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
>> This is a very informative document:
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
>>
>> However, I would like to request one correction:
>> Step 4 under "Setup and Security" indicates that you have to specify the
>> partner and the witness. It tells you to to issue "ALTER DATABASE...SET
>> PARTNER..." on the intended principal first. Then you execute the same
>> command on the intended mirror.
>> Problem:
>> I could not get it to work that way. When I set up Mirroring in my
>> environment (9.0.2153) I had to execute the command on the mirror first
>> then against the primary.
>>
>> --
>> Keith Kratochvil
>>
>|||> argh. "Please limit comments to 256 characters"
Like a SQL 6.5 varchar?
;-)
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:OxGJasH9GHA.788@.TK2MSFTNGP05.phx.gbl...
> argh. "Please limit comments to 256 characters"
> I will try to be more to the point.
> --
> Keith Kratochvil
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:es8ewZH9GHA.3348@.TK2MSFTNGP03.phx.gbl...
>> Hi Keith!
>> The early revisions of this document, I believe was based on a beta, so
>> it is possible that the behavior changed between that and production. Did
>> you do a feedback at the bottom of that page?
>> (I see the same thing, btw, that you have to do mirror before
>> principal...)
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
>> news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
>> This is a very informative document:
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
>>
>> However, I would like to request one correction:
>> Step 4 under "Setup and Security" indicates that you have to specify the
>> partner and the witness. It tells you to to issue "ALTER DATABASE...SET
>> PARTNER..." on the intended principal first. Then you execute the same
>> command on the intended mirror.
>> Problem:
>> I could not get it to work that way. When I set up Mirroring in my
>> environment (9.0.2153) I had to execute the command on the mirror first
>> then against the primary.
>>
>> --
>> Keith Kratochvil
>>
>>
>

database mirroring - correction to technet article requested

This is a very informative document:
http://www.microsoft.com/technet/pr...5/dbmirror.mspx
However, I would like to request one correction:
Step 4 under "Setup and Security" indicates that you have to specify the
partner and the witness. It tells you to to issue "ALTER DATABASE...SET
PARTNER..." on the intended principal first. Then you execute the same
command on the intended mirror.
Problem:
I could not get it to work that way. When I set up Mirroring in my
environment (9.0.2153) I had to execute the command on the mirror first then
against the primary.
Keith KratochvilHi Keith!
The early revisions of this document, I believe was based on a beta, so it i
s possible that the
behavior changed between that and production. Did you do a feedback at the b
ottom of that page?
(I see the same thing, btw, that you have to do mirror before principal...)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
> This is a very informative document:
> http://www.microsoft.com/technet/pr...5/dbmirror.mspx
>
> However, I would like to request one correction:
> Step 4 under "Setup and Security" indicates that you have to specify the p
artner and the witness.
> It tells you to to issue "ALTER DATABASE...SET PARTNER..." on the intended
principal first. Then
> you execute the same command on the intended mirror.
> Problem:
> I could not get it to work that way. When I set up Mirroring in my enviro
nment (9.0.2153) I had
> to execute the command on the mirror first then against the primary.
>
> --
> Keith Kratochvil
>
>|||argh. "Please limit comments to 256 characters"
I will try to be more to the point.
Keith Kratochvil
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:es8ewZH9GHA.3348@.TK2MSFTNGP03.phx.gbl...
> Hi Keith!
> The early revisions of this document, I believe was based on a beta, so it
> is possible that the behavior changed between that and production. Did you
> do a feedback at the bottom of that page?
> (I see the same thing, btw, that you have to do mirror before
> principal...)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
> news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
>|||> argh. "Please limit comments to 256 characters"
Like a SQL 6.5 varchar?
;-)
Hope this helps.
Dan Guzman
SQL Server MVP
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:OxGJasH9GHA.788@.TK2MSFTNGP05.phx.gbl...
> argh. "Please limit comments to 256 characters"
> I will try to be more to the point.
> --
> Keith Kratochvil
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:es8ewZH9GHA.3348@.TK2MSFTNGP03.phx.gbl...
>

database mirroring - correction to technet article requested

This is a very informative document:
http://www.microsoft.com/technet/pro.../dbmirror.mspx
However, I would like to request one correction:
Step 4 under "Setup and Security" indicates that you have to specify the
partner and the witness. It tells you to to issue "ALTER DATABASE...SET
PARTNER..." on the intended principal first. Then you execute the same
command on the intended mirror.
Problem:
I could not get it to work that way. When I set up Mirroring in my
environment (9.0.2153) I had to execute the command on the mirror first then
against the primary.
Keith Kratochvil
Hi Keith!
The early revisions of this document, I believe was based on a beta, so it is possible that the
behavior changed between that and production. Did you do a feedback at the bottom of that page?
(I see the same thing, btw, that you have to do mirror before principal...)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
> This is a very informative document:
> http://www.microsoft.com/technet/pro.../dbmirror.mspx
>
> However, I would like to request one correction:
> Step 4 under "Setup and Security" indicates that you have to specify the partner and the witness.
> It tells you to to issue "ALTER DATABASE...SET PARTNER..." on the intended principal first. Then
> you execute the same command on the intended mirror.
> Problem:
> I could not get it to work that way. When I set up Mirroring in my environment (9.0.2153) I had
> to execute the command on the mirror first then against the primary.
>
> --
> Keith Kratochvil
>
>
|||argh. "Please limit comments to 256 characters"
I will try to be more to the point.
Keith Kratochvil
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:es8ewZH9GHA.3348@.TK2MSFTNGP03.phx.gbl...
> Hi Keith!
> The early revisions of this document, I believe was based on a beta, so it
> is possible that the behavior changed between that and production. Did you
> do a feedback at the bottom of that page?
> (I see the same thing, btw, that you have to do mirror before
> principal...)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
> news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
>
|||> argh. "Please limit comments to 256 characters"
Like a SQL 6.5 varchar?
;-)
Hope this helps.
Dan Guzman
SQL Server MVP
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:OxGJasH9GHA.788@.TK2MSFTNGP05.phx.gbl...
> argh. "Please limit comments to 256 characters"
> I will try to be more to the point.
> --
> Keith Kratochvil
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:es8ewZH9GHA.3348@.TK2MSFTNGP03.phx.gbl...
>

Wednesday, March 21, 2012

DataBASE Mirror Resource

Are there any good resources for data mirror in SQL 2005 SP1?

I tried to search on microsoft.com, there is an article, but it is outdated, it only described data mirror in SQL 2005 RTM.

appreciate any links or input.

Owen

What do you want to know?

There's:

Functionality:

http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx

Best Practice:

http://download.microsoft.com/download/4/f/8/4f8f2dc9-a9a7-4b68-98cb-163482c95e0b/DBM_Best_Pract.doc

Alerts:

http://www.microsoft.com/technet/prodtechnol/sql/2005/mirroringevents.mspx

Couple of webcasts:

Kimberly's

http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032290565&EventCategory=5&culture=en-US&CountryCode=US

Mine:

http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032290576&EventCategory=5&culture=en-US&CountryCode=US

A FAQ:

http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirfaq.mspx

Thanks,

Mark

sql

Sunday, March 11, 2012

Database Maintenance Plan Question

In Microsoft Knowledge Base Article 303292, one of the workarounds
states to create 2 maintenance plans, one for simple, and one for
full/bulk recovery models. Assuming I currently have 10 user
databases, 3 simple and 7 full and I put them into the appropriate
plan, I understand how they would be backed up. How would databases
created after the plans are setup be added?
Thanks much, Lane LesperanceYou would have to change the main plan each time a db is added.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Lane Lesperance" <llesperance@.cooperpower.com> wrote in message
news:66feb5c.0403190933.4f0296a5@.posting.google.com...
> In Microsoft Knowledge Base Article 303292, one of the workarounds
> states to create 2 maintenance plans, one for simple, and one for
> full/bulk recovery models. Assuming I currently have 10 user
> databases, 3 simple and 7 full and I put them into the appropriate
> plan, I understand how they would be backed up. How would databases
> created after the plans are setup be added?
> Thanks much, Lane Lesperance