Database mirroring?

Is database mirroring being delivered as a part of SP1 that is coming out
soon?
Can I setup mirroring with Developer Edition?
OlavAFAIK yes and yes :).
MC
"Olav" <x@.y.com> wrote in message
news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
> Is database mirroring being delivered as a part of SP1 that is coming out
> soon?
> Can I setup mirroring with Developer Edition?
> Olav
>|||Yes & Yes
--
Andrew J. Kelly SQL MVP
"Olav" <x@.y.com> wrote in message
news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
> Is database mirroring being delivered as a part of SP1 that is coming out
> soon?
> Can I setup mirroring with Developer Edition?
> Olav
>|||Yes, but keep in mind it wasn't ready yet when they released 2005, so you'll
be a beta tester without the word "beta". Expect bugs, like everything else
with 2005 so far.
"Olav" <x@.y.com> wrote in message
news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
> Is database mirroring being delivered as a part of SP1 that is coming out
> soon?
> Can I setup mirroring with Developer Edition?
> Olav
>|||That is not a correct statement. Mirroring was fully complete at RTM. MS
simply decided that not enough people fully tested the feature during the
beta period so they wanted to extend it's testing time. In reality it now
has more beta testing than other features that were in RTM to begin with.
--
Andrew J. Kelly SQL MVP
"AFN" <replywithingroup@.notreal.com> wrote in message
news:g4Q_f.848$543.683@.tornado.socal.rr.com...
> Yes, but keep in mind it wasn't ready yet when they released 2005, so
> you'll be a beta tester without the word "beta". Expect bugs, like
> everything else with 2005 so far.
>
> "Olav" <x@.y.com> wrote in message
> news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
>> Is database mirroring being delivered as a part of SP1 that is coming out
>> soon?
>> Can I setup mirroring with Developer Edition?
>> Olav
>|||No, that is NOT accurate.
Database Mirroring was feature complete at RTM and had undergone VERY
rigorous testing over a multi-year time frame. The decision was made to not
expose it in the RTM, because not enough customers had tested it against
their applications to ensure that additional problems wouldn't occur due to
all of the different permutations that are possible. It could be enabled
and used when RTM was released and several hundred customers have continued
to beta test it over the last 6 months. It is being enabled in SP1, because
they now have sufficient customer facing testing completed on it.
This is one of the features that has had more testing time than anything
else in the product and is EXTREMELY stable.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"AFN" <replywithingroup@.notreal.com> wrote in message
news:g4Q_f.848$543.683@.tornado.socal.rr.com...
> Yes, but keep in mind it wasn't ready yet when they released 2005, so
> you'll be a beta tester without the word "beta". Expect bugs, like
> everything else with 2005 so far.
>
> "Olav" <x@.y.com> wrote in message
> news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
>> Is database mirroring being delivered as a part of SP1 that is coming out
>> soon?
>> Can I setup mirroring with Developer Edition?
>> Olav
>

Database Mirroring with SQLEXPRESS as witness

I am trying to setup SQLServer 2005 to use Database Mirroring.
The principal and mirror servers are running on Windows2003 64bit edition.
The witness server is running Windows2003 32bit.
I have configured endpoints for both the principal and mirror but when I try
to setup SQLEXPRESS as the witness using...
create endpoint MirroringEndPoint
state=started
as tcp (listener_port=10111)
for database_mirroring (role=all)
I get..
Msg 7878, Level 16, State 4, Line 4
This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this edition
of SQL Server.
SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then it
complains about mirroring not being supported in a production environment
which is why I have upgraded to SP2.
Best regards
MarkSorry, I misread. Specify role=witness, which is the only role supported for
Express Edition.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mark Baldwin" <sWozzi3@.community.nospam> wrote in message
news:uBslxtVmHHA.3736@.TK2MSFTNGP03.phx.gbl...
>I am trying to setup SQLServer 2005 to use Database Mirroring.
> The principal and mirror servers are running on Windows2003 64bit edition.
The witness server is
> running Windows2003 32bit.
> I have configured endpoints for both the principal and mirror but when I t
ry to setup SQLEXPRESS
> as the witness using...
> create endpoint MirroringEndPoint
> state=started
> as tcp (listener_port=10111)
> for database_mirroring (role=all)
> I get..
> Msg 7878, Level 16, State 4, Line 4
> This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this editio
n of SQL Server.
> SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then it
complains about
> mirroring not being supported in a production environment which is why I h
ave upgraded to SP2.
> --
> Best regards
> Mark
>|||You need standard or enterprise edition for mirroring. By the name of your i
nstance to judge, it is
express edition.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mark Baldwin" <sWozzi3@.community.nospam> wrote in message
news:uBslxtVmHHA.3736@.TK2MSFTNGP03.phx.gbl...
>I am trying to setup SQLServer 2005 to use Database Mirroring.
> The principal and mirror servers are running on Windows2003 64bit edition.
The witness server is
> running Windows2003 32bit.
> I have configured endpoints for both the principal and mirror but when I t
ry to setup SQLEXPRESS
> as the witness using...
> create endpoint MirroringEndPoint
> state=started
> as tcp (listener_port=10111)
> for database_mirroring (role=all)
> I get..
> Msg 7878, Level 16, State 4, Line 4
> This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this editio
n of SQL Server.
> SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then it
complains about
> mirroring not being supported in a production environment which is why I h
ave upgraded to SP2.
> --
> Best regards
> Mark
>|||Thanks, that seems to have sorted the problem out but I have another issue
with security now - still I shall leave that to another thread
Best regards
Mark
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OzTxF%23VmHHA.4768@.TK2MSFTNGP05.phx.gbl...
> Sorry, I misread. Specify role=witness, which is the only role supported
> for Express Edition.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mark Baldwin" <sWozzi3@.community.nospam> wrote in message
> news:uBslxtVmHHA.3736@.TK2MSFTNGP03.phx.gbl...
>

Database Mirroring with SQLEXPRESS as witness

I am trying to setup SQLServer 2005 to use Database Mirroring.
The principal and mirror servers are running on Windows2003 64bit edition.
The witness server is running Windows2003 32bit.
I have configured endpoints for both the principal and mirror but when I try
to setup SQLEXPRESS as the witness using...
create endpoint MirroringEndPoint
state=started
as tcp (listener_port=10111)
for database_mirroring (role=all)
I get..
Msg 7878, Level 16, State 4, Line 4
This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this edition
of SQL Server.
SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then it
complains about mirroring not being supported in a production environment
which is why I have upgraded to SP2.
--
Best regards
MarkSorry, I misread. Specify role=witness, which is the only role supported for Express Edition.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mark Baldwin" <sWozzi3@.community.nospam> wrote in message
news:uBslxtVmHHA.3736@.TK2MSFTNGP03.phx.gbl...
>I am trying to setup SQLServer 2005 to use Database Mirroring.
> The principal and mirror servers are running on Windows2003 64bit edition. The witness server is
> running Windows2003 32bit.
> I have configured endpoints for both the principal and mirror but when I try to setup SQLEXPRESS
> as the witness using...
> create endpoint MirroringEndPoint
> state=started
> as tcp (listener_port=10111)
> for database_mirroring (role=all)
> I get..
> Msg 7878, Level 16, State 4, Line 4
> This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this edition of SQL Server.
> SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then it complains about
> mirroring not being supported in a production environment which is why I have upgraded to SP2.
> --
> Best regards
> Mark
>|||You need standard or enterprise edition for mirroring. By the name of your instance to judge, it is
express edition.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mark Baldwin" <sWozzi3@.community.nospam> wrote in message
news:uBslxtVmHHA.3736@.TK2MSFTNGP03.phx.gbl...
>I am trying to setup SQLServer 2005 to use Database Mirroring.
> The principal and mirror servers are running on Windows2003 64bit edition. The witness server is
> running Windows2003 32bit.
> I have configured endpoints for both the principal and mirror but when I try to setup SQLEXPRESS
> as the witness using...
> create endpoint MirroringEndPoint
> state=started
> as tcp (listener_port=10111)
> for database_mirroring (role=all)
> I get..
> Msg 7878, Level 16, State 4, Line 4
> This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this edition of SQL Server.
> SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then it complains about
> mirroring not being supported in a production environment which is why I have upgraded to SP2.
> --
> Best regards
> Mark
>|||Thanks, that seems to have sorted the problem out but I have another issue
with security now - still I shall leave that to another thread
--
Best regards
Mark
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OzTxF%23VmHHA.4768@.TK2MSFTNGP05.phx.gbl...
> Sorry, I misread. Specify role=witness, which is the only role supported
> for Express Edition.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mark Baldwin" <sWozzi3@.community.nospam> wrote in message
> news:uBslxtVmHHA.3736@.TK2MSFTNGP03.phx.gbl...
>>I am trying to setup SQLServer 2005 to use Database Mirroring.
>> The principal and mirror servers are running on Windows2003 64bit
>> edition. The witness server is running Windows2003 32bit.
>> I have configured endpoints for both the principal and mirror but when I
>> try to setup SQLEXPRESS as the witness using...
>> create endpoint MirroringEndPoint
>> state=started
>> as tcp (listener_port=10111)
>> for database_mirroring (role=all)
>> I get..
>> Msg 7878, Level 16, State 4, Line 4
>> This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this
>> edition of SQL Server.
>> SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then
>> it complains about mirroring not being supported in a production
>> environment which is why I have upgraded to SP2.
>> --
>> Best regards
>> Mark
>

Database mirroring support also by SQL server 2005 without SP1

Hi All,

I get a general question about the feacture "Database Mirroring". Is it support by SQL Server Standard. Edition without SP1? Of i still need to upgrade the server from SQL Server 2005 to SQL Server 2005 with SP1?

Another question: are there any problem if the one machine(server) has installed SQL server 2005 Standard edition and the other with "Developer Editon".

I hope some one can answer my question. Thanks anyway!

Regards,

Pat

Yes, it's supported in SQL server 2005 standard edition. But by default it's disable. you must specify the trace flag 1400 as a startup parameter. Please refer http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=423000&SiteId=1 for more detail.

There should not be problem if one server is "standard edition" and other one is "developer edition".

|||

Hi All,

Anyone know or i still to install the SQL Server 2005 SP 1 first before i can use the feature "Database Mirroring"?

Best regards,

Pat

|||

I believe your question was answered by the above post

YES, you can do database mirroring in SQL2005, with or without SP1 (need to set trace flag 1400)

For your other question, mirroring between STD and DEV edition

This post should help, even though it's between STD and ENT (DEV IS Enterprise edition)

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=730526&SiteID=1

|||

In non-SP1, Database mirroring exists, but it is not supported. What that means is that you are using it at your own risk. If it blows up and deletes allof your data, MS won't help you unless you are running SP1.

Database mirroring support also by SQL server 2005 without SP1

Hi All,

I get a general question about the feacture "Database Mirroring". Is it support by SQL Server Standard. Edition without SP1? Of i still need to upgrade the server from SQL Server 2005 to SQL Server 2005 with SP1?

Another question: are there any problem if the one machine(server) has installed SQL server 2005 Standard edition and the other with "Developer Editon".

I hope some one can answer my question. Thanks anyway!

Regards,

Pat

Yes, it's supported in SQL server 2005 standard edition. But by default it's disable. you must specify the trace flag 1400 as a startup parameter. Please refer http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=423000&SiteId=1 for more detail.

There should not be problem if one server is "standard edition" and other one is "developer edition".

|||

Hi All,

Anyone know or i still to install the SQL Server 2005 SP 1 first before i can use the feature "Database Mirroring"?

Best regards,

Pat

|||

I believe your question was answered by the above post

YES, you can do database mirroring in SQL2005, with or without SP1 (need to set trace flag 1400)

For your other question, mirroring between STD and DEV edition

This post should help, even though it's between STD and ENT (DEV IS Enterprise edition)

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=730526&SiteID=1

|||

In non-SP1, Database mirroring exists, but it is not supported. What that means is that you are using it at your own risk. If it blows up and deletes allof your data, MS won't help you unless you are running SP1.

sql

database mirroring question

Is Asynchronous database mirroring support in the Standard Edition of
SQL 2005?
I've read some docs that say it isn't. However, my manager saids that
he was told it was (or would work), something about 'single stream'? I
have not been able to find any docs that talks about 'single stream'.
Can anyone advise or point me in the right direction?
thanks all,
JDJoeyD
If I remember well, database mirroring is supported only on Enterprise
Edition
"JoeyD" <joeydba@.gmail.com> wrote in message
news:1168635799.710707.324810@.51g2000cwl.googlegroups.com...
> Is Asynchronous database mirroring support in the Standard Edition of
> SQL 2005?
> I've read some docs that say it isn't. However, my manager saids that
> he was told it was (or would work), something about 'single stream'? I
> have not been able to find any docs that talks about 'single stream'.
> Can anyone advise or point me in the right direction?
> thanks all,
> JD
>|||Synchronous mirroring is supported on Standard and Enterprise editions.
Asynchronous mode is only supported on Enterprise edition.
--
Paul Randal
Principal Lead Program Manager
Core Storage Engine, Microsoft SQL Server Team
http://blogs.msdn.com/sqlserverstorageengine/default.aspx
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uh6Amz7NHHA.3916@.TK2MSFTNGP02.phx.gbl...
> JoeyD
> If I remember well, database mirroring is supported only on Enterprise
> Edition
>
> "JoeyD" <joeydba@.gmail.com> wrote in message
> news:1168635799.710707.324810@.51g2000cwl.googlegroups.com...
>> Is Asynchronous database mirroring support in the Standard Edition of
>> SQL 2005?
>> I've read some docs that say it isn't. However, my manager saids that
>> he was told it was (or would work), something about 'single stream'? I
>> have not been able to find any docs that talks about 'single stream'.
>> Can anyone advise or point me in the right direction?
>> thanks all,
>> JD
>|||Thanks Paul for the reply. I've done some more testing on my own and
have found this to be true. Not sure what my manager had heard or where
he had heard it.
Joe
Paul S. Randal [MS] wrote:
> Synchronous mirroring is supported on Standard and Enterprise editions.
> Asynchronous mode is only supported on Enterprise edition.
> --
> Paul Randal
> Principal Lead Program Manager
> Core Storage Engine, Microsoft SQL Server Team
> http://blogs.msdn.com/sqlserverstorageengine/default.aspx
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:uh6Amz7NHHA.3916@.TK2MSFTNGP02.phx.gbl...
> > JoeyD
> > If I remember well, database mirroring is supported only on Enterprise
> > Edition
> >
> >
> >
> > "JoeyD" <joeydba@.gmail.com> wrote in message
> > news:1168635799.710707.324810@.51g2000cwl.googlegroups.com...
> >> Is Asynchronous database mirroring support in the Standard Edition of
> >> SQL 2005?
> >>
> >> I've read some docs that say it isn't. However, my manager saids that
> >> he was told it was (or would work), something about 'single stream'? I
> >> have not been able to find any docs that talks about 'single stream'.
> >> Can anyone advise or point me in the right direction?
> >>
> >> thanks all,
> >> JD
> >>
> >
> >

database mirroring question

Is Asynchronous database mirroring support in the Standard Edition of
SQL 2005?
I've read some docs that say it isn't. However, my manager saids that
he was told it was (or would work), something about 'single stream'? I
have not been able to find any docs that talks about 'single stream'.
Can anyone advise or point me in the right direction?
thanks all,
JD
JoeyD
If I remember well, database mirroring is supported only on Enterprise
Edition
"JoeyD" <joeydba@.gmail.com> wrote in message
news:1168635799.710707.324810@.51g2000cwl.googlegro ups.com...
> Is Asynchronous database mirroring support in the Standard Edition of
> SQL 2005?
> I've read some docs that say it isn't. However, my manager saids that
> he was told it was (or would work), something about 'single stream'? I
> have not been able to find any docs that talks about 'single stream'.
> Can anyone advise or point me in the right direction?
> thanks all,
> JD
>
|||Synchronous mirroring is supported on Standard and Enterprise editions.
Asynchronous mode is only supported on Enterprise edition.
Paul Randal
Principal Lead Program Manager
Core Storage Engine, Microsoft SQL Server Team
http://blogs.msdn.com/sqlserverstorageengine/default.aspx
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uh6Amz7NHHA.3916@.TK2MSFTNGP02.phx.gbl...
> JoeyD
> If I remember well, database mirroring is supported only on Enterprise
> Edition
>
> "JoeyD" <joeydba@.gmail.com> wrote in message
> news:1168635799.710707.324810@.51g2000cwl.googlegro ups.com...
>
|||Thanks Paul for the reply. I've done some more testing on my own and
have found this to be true. Not sure what my manager had heard or where
he had heard it.
Joe
Paul S. Randal [MS] wrote:[vbcol=seagreen]
> Synchronous mirroring is supported on Standard and Enterprise editions.
> Asynchronous mode is only supported on Enterprise edition.
> --
> Paul Randal
> Principal Lead Program Manager
> Core Storage Engine, Microsoft SQL Server Team
> http://blogs.msdn.com/sqlserverstorageengine/default.aspx
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:uh6Amz7NHHA.3916@.TK2MSFTNGP02.phx.gbl...

database mirroring question

Is Asynchronous database mirroring support in the Standard Edition of
SQL 2005?
I've read some docs that say it isn't. However, my manager saids that
he was told it was (or would work), something about 'single stream'? I
have not been able to find any docs that talks about 'single stream'.
Can anyone advise or point me in the right direction?
thanks all,
JDJoeyD
If I remember well, database mirroring is supported only on Enterprise
Edition
"JoeyD" <joeydba@.gmail.com> wrote in message
news:1168635799.710707.324810@.51g2000cwl.googlegroups.com...
> Is Asynchronous database mirroring support in the Standard Edition of
> SQL 2005?
> I've read some docs that say it isn't. However, my manager saids that
> he was told it was (or would work), something about 'single stream'? I
> have not been able to find any docs that talks about 'single stream'.
> Can anyone advise or point me in the right direction?
> thanks all,
> JD
>|||Synchronous mirroring is supported on Standard and Enterprise editions.
Asynchronous mode is only supported on Enterprise edition.
Paul Randal
Principal Lead Program Manager
Core Storage Engine, Microsoft SQL Server Team
http://blogs.msdn.com/sqlserverstor...ne/default.aspx
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uh6Amz7NHHA.3916@.TK2MSFTNGP02.phx.gbl...
> JoeyD
> If I remember well, database mirroring is supported only on Enterprise
> Edition
>
> "JoeyD" <joeydba@.gmail.com> wrote in message
> news:1168635799.710707.324810@.51g2000cwl.googlegroups.com...
>|||Thanks Paul for the reply. I've done some more testing on my own and
have found this to be true. Not sure what my manager had heard or where
he had heard it.
Joe
Paul S. Randal [MS] wrote:[vbcol=seagreen]
> Synchronous mirroring is supported on Standard and Enterprise editions.
> Asynchronous mode is only supported on Enterprise edition.
> --
> Paul Randal
> Principal Lead Program Manager
> Core Storage Engine, Microsoft SQL Server Team
> http://blogs.msdn.com/sqlserverstor...ne/default.aspx
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:uh6Amz7NHHA.3916@.TK2MSFTNGP02.phx.gbl...sql

Database Mirroring Monitor Job Error

We have recently set up two SQL Server 2005 Standard Edition servers with database mirroring. The mirrors function and fail over without a problem, but the Database Mirroring Monitor Job fails every time with the following error message:

Incorrect syntax near '.'. [SQLSTATE 42000] (Error 102) Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. [SQLSTATE 42000] (Error 319). The step failed.

Both SQL Servers are running SP2 with the latest patches.

Can you please let me know what we have to do to resolve this issue?

Thank you!

Bosko

Is this been like this since the invocation of Database mirroring on these instances?

If not see what has been changed since the last successful occurence.

|||The problems started upon implementation of the database mirroring|||

I'm also facing the same issue.

Did anyone find a solution or workaround?

|||

I posted this in a couple different forums/newsgroups and never got an answer. We are still having this problem.

Bosko

Database Mirroring Monitor Job Error

We have recently set up two SQL Server 2005 Standard Edition servers with database mirroring. The mirrors function and fail over without a problem, but the Database Mirroring Monitor Job fails every time with the following error message:

Incorrect syntax near '.'. [SQLSTATE 42000] (Error 102) Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. [SQLSTATE 42000] (Error 319). The step failed.

Both SQL Servers are running SP2 with the latest patches.

Can you please let me know what we have to do to resolve this issue?

Thank you!

Bosko

Is this been like this since the invocation of Database mirroring on these instances?

If not see what has been changed since the last successful occurence.

|||The problems started upon implementation of the database mirroringsql

Database Mirroring Monitor Job Error

We have recently set up two SQL Server 2005 Standard Edition servers
with database mirroring. The mirrors function and fail over without a
problem, but the Database Mirroring Monitor Job fails every time with
the following error message:

Incorrect syntax near '.'. [SQLSTATE 42000] (Error 102) Incorrect
syntax near the keyword 'with'. If this statement is a common table
expression or an xmlnamespaces clause, the previous statement must be
terminated with a semicolon. [SQLSTATE 42000] (Error 319). The step
failed.

Both SQL Servers are running SP2 with the latest patches.

Can anyone help with the resolutionto this this issue?

Thank you!
Bosko(bosko19@.gmail.com) writes:

Quote:

Originally Posted by

We have recently set up two SQL Server 2005 Standard Edition servers
with database mirroring. The mirrors function and fail over without a
problem, but the Database Mirroring Monitor Job fails every time with
the following error message:
>
Incorrect syntax near '.'. [SQLSTATE 42000] (Error 102) Incorrect
syntax near the keyword 'with'. If this statement is a common table
expression or an xmlnamespaces clause, the previous statement must be
terminated with a semicolon. [SQLSTATE 42000] (Error 319). The step
failed.
>
Both SQL Servers are running SP2 with the latest patches.
>
Can anyone help with the resolutionto this this issue?

Eh, that looks bad. I haven't worked much with mirroring, or more precisely
not at all. But a syntax errors is not what I would expect. Could you
list the exact name of the servers and databases involved? My suspicion
is that there is a problem with special characters.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||On Apr 13, 6:45 pm, Erland Sommarskog <esq...@.sommarskog.sewrote:

Quote:

Originally Posted by

(bosk...@.gmail.com) writes:

Quote:

Originally Posted by

We have recently set up two SQL Server 2005 Standard Edition servers
with database mirroring. The mirrors function and fail over without a
problem, but the Database Mirroring Monitor Job fails every time with
the following error message:

>

Quote:

Originally Posted by

Incorrect syntax near '.'. [SQLSTATE 42000] (Error 102) Incorrect
syntax near the keyword 'with'. If this statement is a common table
expression or an xmlnamespaces clause, the previous statement must be
terminated with a semicolon. [SQLSTATE 42000] (Error 319). The step
failed.

>

Quote:

Originally Posted by

Both SQL Servers are running SP2 with the latest patches.

>

Quote:

Originally Posted by

Can anyone help with the resolutionto this this issue?

>
Eh, that looks bad. I haven't worked much with mirroring, or more precisely
not at all. But a syntax errors is not what I would expect. Could you
list the exact name of the servers and databases involved? My suspicion
is that there is a problem with special characters.
>
--
Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>
Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

LOL...I didn't think it looked good either :)

The database server has a dash in it (i.e. CompanyName-SQL1 and SQL2
respecitvely). All databases are just alpha characters except for one
that begins with a number sequence (i.e. 1000DatabaseName).

Thank you in advance!

Bosko|||(bosko19@.gmail.com) writes:

Quote:

Originally Posted by

The database server has a dash in it (i.e. CompanyName-SQL1 and SQL2
respecitvely). All databases are just alpha characters except for one
that begins with a number sequence (i.e. 1000DatabaseName).

What service-pack level are you at? (For all three machines.)

If you are on SP2, you should definitely submit a bug on
http://connect.microsoft.com/SqlServer/. And if it's not an acceptable
workaround to rename the servers, I think you should open a case with
Microsoft, and demand that you get a hotfix.

If you are not on SP2, I recommend you to download it to see if it addresses
the problem. Note there is a rollup to SP2 which addresses two serious
bugs with maintenance plans. Make sure you get the rollup, if you use
maintenance plans.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Erland Sommarskog (esquel@.sommarskog.se) writes:

Quote:

Originally Posted by

What service-pack level are you at? (For all three machines.)

Sorry, I see now in your first post that you are on SP2.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||On Apr 16, 5:30 pm, Erland Sommarskog <esq...@.sommarskog.sewrote:

Quote:

Originally Posted by

Erland Sommarskog (esq...@.sommarskog.se) writes:

Quote:

Originally Posted by

What service-pack level are you at? (For all three machines.)

>
Sorry, I see now in your first post that you are on SP2.
>
--
Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>
Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Thank you for taking the time to look into the issue! I will submit
the case to Microsoft and hopefully get a resolution from them.

Bosko

Database Mirroring - setting up the witness

SQL Server 2005 Standard Edition SP1 + .2153 hotfixes, Windows 2003 R2 SP1
Witness: SQL Server 2005 Developer Edition SP1 + .2153 hotfixes
Corporate stuff runs in the parent domain (including witness)
Hosted (client) servers run in the child domain(s).
I set up mirroring between two SQL2k5 boxes in our child domain. SQL Server
runs under a network account in the child domain. We run our corparate SQL
Servers under a different account in our parent domain.
I wanted to have the witness box (located in our corporate domain) monitor
the primary and mirrors in the various child domains. I am running into the
following error message: "The ALTER DATABASE command could not be sent to
the remote server instance 'TCP://Witness-Server.TheParentDomain.com:5022'.
The database mirroring configuration was not changed. Verify that the server
is connected, and try again."
I verified that the appropriate endpoints exist within the witness via the
following query: SELECT name, role_desc, state_desc FROM
sys.database_mirroring_endpoints
What am I doing wrong?
Keith KratochvilThe service accounts are most likely different between the two domains. You
need to add the service account of the witness to the SQL Server hosting the
principal and mirror and vice versa. You then have to grant CONNECT TO
permissions to the account for the Database Mirroring endpoint.
Mike Hotek
MHS Enterprises, Inc
http://www.mssqlserver.com
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:%23T73eWR0GHA.2036@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005 Standard Edition SP1 + .2153 hotfixes, Windows 2003 R2 SP1
> Witness: SQL Server 2005 Developer Edition SP1 + .2153 hotfixes
> Corporate stuff runs in the parent domain (including witness)
> Hosted (client) servers run in the child domain(s).
>
> I set up mirroring between two SQL2k5 boxes in our child domain. SQL
> Server runs under a network account in the child domain. We run our
> corparate SQL Servers under a different account in our parent domain.
> I wanted to have the witness box (located in our corporate domain) monitor
> the primary and mirrors in the various child domains. I am running into
> the following error message: "The ALTER DATABASE command could not be sent
> to the remote server instance
> 'TCP://Witness-Server.TheParentDomain.com:5022'. The database mirroring
> configuration was not changed. Verify that the server is connected, and
> try again."
> I verified that the appropriate endpoints exist within the witness via the
> following query: SELECT name, role_desc, state_desc FROM
> sys.database_mirroring_endpoints
> What am I doing wrong?
> --
> Keith Kratochvil
>
>

Database Mirroring - setting up the witness

SQL Server 2005 Standard Edition SP1 + .2153 hotfixes, Windows 2003 R2 SP1
Witness: SQL Server 2005 Developer Edition SP1 + .2153 hotfixes
Corporate stuff runs in the parent domain (including witness)
Hosted (client) servers run in the child domain(s).
I set up mirroring between two SQL2k5 boxes in our child domain. SQL Server
runs under a network account in the child domain. We run our corparate SQL
Servers under a different account in our parent domain.
I wanted to have the witness box (located in our corporate domain) monitor
the primary and mirrors in the various child domains. I am running into the
following error message: "The ALTER DATABASE command could not be sent to
the remote server instance 'TCP://Witness-Server.TheParentDomain.com:5022'.
The database mirroring configuration was not changed. Verify that the server
is connected, and try again."
I verified that the appropriate endpoints exist within the witness via the
following query: SELECT name, role_desc, state_desc FROM
sys.database_mirroring_endpoints
What am I doing wrong?
--
Keith KratochvilThe service accounts are most likely different between the two domains. You
need to add the service account of the witness to the SQL Server hosting the
principal and mirror and vice versa. You then have to grant CONNECT TO
permissions to the account for the Database Mirroring endpoint.
--
Mike Hotek
MHS Enterprises, Inc
http://www.mssqlserver.com
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:%23T73eWR0GHA.2036@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005 Standard Edition SP1 + .2153 hotfixes, Windows 2003 R2 SP1
> Witness: SQL Server 2005 Developer Edition SP1 + .2153 hotfixes
> Corporate stuff runs in the parent domain (including witness)
> Hosted (client) servers run in the child domain(s).
>
> I set up mirroring between two SQL2k5 boxes in our child domain. SQL
> Server runs under a network account in the child domain. We run our
> corparate SQL Servers under a different account in our parent domain.
> I wanted to have the witness box (located in our corporate domain) monitor
> the primary and mirrors in the various child domains. I am running into
> the following error message: "The ALTER DATABASE command could not be sent
> to the remote server instance
> 'TCP://Witness-Server.TheParentDomain.com:5022'. The database mirroring
> configuration was not changed. Verify that the server is connected, and
> try again."
> I verified that the appropriate endpoints exist within the witness via the
> following query: SELECT name, role_desc, state_desc FROM
> sys.database_mirroring_endpoints
> What am I doing wrong?
> --
> Keith Kratochvil
>
>sql

Database mirroring

Hi All

I need to find out on limitation in SQL 2005 standered edition on numbers of databases can be mirrored, in other words whats the maximum numbers of databases can be used for database mirroring

Thanks

Alps

I believe that there is no limitation on using databases in database mirroring.

More info :

Database Mirroring in SQL Server 2005.

Thanks.

Naras.

|||As explained there is not such limit, but on 1 server it is not advisable to have more than 10 database that is based on the tests performed on a high-end spec. hardware. Also when it comes to recover in case of any recovery it will take more time to recover and in this case based on your requirement you might look at to restrict upto 5 database per instance.

Database Mirroring

I'd like to verify that to use Asynchronous database mirroring is NOT
support for Standard Edition.
I've read some docs that say it isn't. However, my manager saids that
he was told it was (or would work), something about 'single stream'? I
have not been able to find any docs that talks about 'single stream'.
Can anyone advise or point me in the right direction?
thanks all,
JD
Standard Edition Database Mirroring is supported as follows:
Single REDO thread and the safety setting is always on.
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
"JoeyD" wrote:

> I'd like to verify that to use Asynchronous database mirroring is NOT
> support for Standard Edition.
> I've read some docs that say it isn't. However, my manager saids that
> he was told it was (or would work), something about 'single stream'? I
> have not been able to find any docs that talks about 'single stream'.
> Can anyone advise or point me in the right direction?
> thanks all,
> JD
>
sql

Database Mirroring

I'd like to verify that to use Asynchronous database mirroring is NOT
support for Standard Edition.
I've read some docs that say it isn't. However, my manager saids that
he was told it was (or would work), something about 'single stream'? I
have not been able to find any docs that talks about 'single stream'.
Can anyone advise or point me in the right direction?
thanks all,
JDStandard Edition Database Mirroring is supported as follows:
Single REDO thread and the safety setting is always on.
http://www.microsoft.com/sql/prodin...e-features.mspx
"JoeyD" wrote:

> I'd like to verify that to use Asynchronous database mirroring is NOT
> support for Standard Edition.
> I've read some docs that say it isn't. However, my manager saids that
> he was told it was (or would work), something about 'single stream'? I
> have not been able to find any docs that talks about 'single stream'.
> Can anyone advise or point me in the right direction?
> thanks all,
> JD
>

Database Maintenance

We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Edition
Server. We setup a database maintenance (Database Integrity and Index,
Reorganize data and indexes, etc. ) to run every week. However, the report
shows that the maintenance job did not run because the database needs to be
in a single user mode. How do you setup a single user mode to run the
database maintenance? When the database maintenance is done, how do you
remove the single user mode? Thanks.
Uncheck the "Attempt to repair minor problems" checkbox. All this does is
hide problems until they become unfixable.
Run DBCC CHECKDB manually. You will find you have a problem. Fix the
problem. You will likely have to take the system offline to fix it.
Database corruption issues are very often due to disk subsystem failures.
Check on that and repair if necessary.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. We setup a database maintenance (Database Integrity and
> Index, Reorganize data and indexes, etc. ) to run every week. However,
> the report shows that the maintenance job did not run because the database
> needs to be in a single user mode. How do you setup a single user mode to
> run the database maintenance? When the database maintenance is done, how
> do you remove the single user mode? Thanks.
>
|||Thanks very much for your prompt response, Geoff.
If I run DBCC CHECKDB manually, what kind of problems do you expect that I
will encounter? Normally, are these problems easy to fix? Thanks.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23h63CRMOGHA.2268@.TK2MSFTNGP09.phx.gbl...
> Uncheck the "Attempt to repair minor problems" checkbox. All this does is
> hide problems until they become unfixable.
> Run DBCC CHECKDB manually. You will find you have a problem. Fix the
> problem. You will likely have to take the system offline to fix it.
> Database corruption issues are very often due to disk subsystem failures.
> Check on that and repair if necessary.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
>
|||How do you take the system offline to fix a problem?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23h63CRMOGHA.2268@.TK2MSFTNGP09.phx.gbl...
> Uncheck the "Attempt to repair minor problems" checkbox. All this does is
> hide problems until they become unfixable.
> Run DBCC CHECKDB manually. You will find you have a problem. Fix the
> problem. You will likely have to take the system offline to fix it.
> Database corruption issues are very often due to disk subsystem failures.
> Check on that and repair if necessary.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
>
|||Answering both responses.
I don't know what kinds of problems you will find. You can run DBCC CHECKDB
anytime, but it does create a significant load on the system. I would do it
at a low activity time. To do a repair, you first have to take the database
into single-user mode. Both topics are covered in BOL under DBCC CHECKDB
and DBCC DBREPAIR. I suggest you do a LOT of reading before trying
anything.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OLSGtcMOGHA.3924@.TK2MSFTNGP14.phx.gbl...
> How do you take the system offline to fix a problem?
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23h63CRMOGHA.2268@.TK2MSFTNGP09.phx.gbl...
>
|||Thanks very much for your prompt response, Geoff.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OKBZgjMOGHA.3576@.TK2MSFTNGP15.phx.gbl...
> Answering both responses.
> I don't know what kinds of problems you will find. You can run DBCC
> CHECKDB anytime, but it does create a significant load on the system. I
> would do it at a low activity time. To do a repair, you first have to
> take the database into single-user mode. Both topics are covered in BOL
> under DBCC CHECKDB and DBCC DBREPAIR. I suggest you do a LOT of reading
> before trying anything.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OLSGtcMOGHA.3924@.TK2MSFTNGP14.phx.gbl...
>

Database Maintenance

We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Edition
Server. We setup a database maintenance (Database Integrity and Index,
Reorganize data and indexes, etc. ) to run every week. However, the report
shows that the maintenance job did not run because the database needs to be
in a single user mode. How do you setup a single user mode to run the
database maintenance? When the database maintenance is done, how do you
remove the single user mode? Thanks.Uncheck the "Attempt to repair minor problems" checkbox. All this does is
hide problems until they become unfixable.
Run DBCC CHECKDB manually. You will find you have a problem. Fix the
problem. You will likely have to take the system offline to fix it.
Database corruption issues are very often due to disk subsystem failures.
Check on that and repair if necessary.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. We setup a database maintenance (Database Integrity and
> Index, Reorganize data and indexes, etc. ) to run every week. However,
> the report shows that the maintenance job did not run because the database
> needs to be in a single user mode. How do you setup a single user mode to
> run the database maintenance? When the database maintenance is done, how
> do you remove the single user mode? Thanks.
>|||Thanks very much for your prompt response, Geoff.
If I run DBCC CHECKDB manually, what kind of problems do you expect that I
will encounter? Normally, are these problems easy to fix? Thanks.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23h63CRMOGHA.2268@.TK2MSFTNGP09.phx.gbl...
> Uncheck the "Attempt to repair minor problems" checkbox. All this does is
> hide problems until they become unfixable.
> Run DBCC CHECKDB manually. You will find you have a problem. Fix the
> problem. You will likely have to take the system offline to fix it.
> Database corruption issues are very often due to disk subsystem failures.
> Check on that and repair if necessary.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
>> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
>> Edition Server. We setup a database maintenance (Database Integrity and
>> Index, Reorganize data and indexes, etc. ) to run every week. However,
>> the report shows that the maintenance job did not run because the
>> database needs to be in a single user mode. How do you setup a single
>> user mode to run the database maintenance? When the database maintenance
>> is done, how do you remove the single user mode? Thanks.
>|||How do you take the system offline to fix a problem?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23h63CRMOGHA.2268@.TK2MSFTNGP09.phx.gbl...
> Uncheck the "Attempt to repair minor problems" checkbox. All this does is
> hide problems until they become unfixable.
> Run DBCC CHECKDB manually. You will find you have a problem. Fix the
> problem. You will likely have to take the system offline to fix it.
> Database corruption issues are very often due to disk subsystem failures.
> Check on that and repair if necessary.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
>> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
>> Edition Server. We setup a database maintenance (Database Integrity and
>> Index, Reorganize data and indexes, etc. ) to run every week. However,
>> the report shows that the maintenance job did not run because the
>> database needs to be in a single user mode. How do you setup a single
>> user mode to run the database maintenance? When the database maintenance
>> is done, how do you remove the single user mode? Thanks.
>|||Answering both responses.
I don't know what kinds of problems you will find. You can run DBCC CHECKDB
anytime, but it does create a significant load on the system. I would do it
at a low activity time. To do a repair, you first have to take the database
into single-user mode. Both topics are covered in BOL under DBCC CHECKDB
and DBCC DBREPAIR. I suggest you do a LOT of reading before trying
anything.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OLSGtcMOGHA.3924@.TK2MSFTNGP14.phx.gbl...
> How do you take the system offline to fix a problem?
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23h63CRMOGHA.2268@.TK2MSFTNGP09.phx.gbl...
>> Uncheck the "Attempt to repair minor problems" checkbox. All this does
>> is hide problems until they become unfixable.
>> Run DBCC CHECKDB manually. You will find you have a problem. Fix the
>> problem. You will likely have to take the system offline to fix it.
>> Database corruption issues are very often due to disk subsystem failures.
>> Check on that and repair if necessary.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>> "Diane Walker" <ett9300@.yahoo.com> wrote in message
>> news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
>> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
>> Edition Server. We setup a database maintenance (Database Integrity and
>> Index, Reorganize data and indexes, etc. ) to run every week. However,
>> the report shows that the maintenance job did not run because the
>> database needs to be in a single user mode. How do you setup a single
>> user mode to run the database maintenance? When the database
>> maintenance is done, how do you remove the single user mode? Thanks.
>>
>|||Thanks very much for your prompt response, Geoff.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OKBZgjMOGHA.3576@.TK2MSFTNGP15.phx.gbl...
> Answering both responses.
> I don't know what kinds of problems you will find. You can run DBCC
> CHECKDB anytime, but it does create a significant load on the system. I
> would do it at a low activity time. To do a repair, you first have to
> take the database into single-user mode. Both topics are covered in BOL
> under DBCC CHECKDB and DBCC DBREPAIR. I suggest you do a LOT of reading
> before trying anything.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OLSGtcMOGHA.3924@.TK2MSFTNGP14.phx.gbl...
>> How do you take the system offline to fix a problem?
>> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
>> news:%23h63CRMOGHA.2268@.TK2MSFTNGP09.phx.gbl...
>> Uncheck the "Attempt to repair minor problems" checkbox. All this does
>> is hide problems until they become unfixable.
>> Run DBCC CHECKDB manually. You will find you have a problem. Fix the
>> problem. You will likely have to take the system offline to fix it.
>> Database corruption issues are very often due to disk subsystem
>> failures. Check on that and repair if necessary.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>> "Diane Walker" <ett9300@.yahoo.com> wrote in message
>> news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
>> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
>> Edition Server. We setup a database maintenance (Database Integrity
>> and Index, Reorganize data and indexes, etc. ) to run every week.
>> However, the report shows that the maintenance job did not run because
>> the database needs to be in a single user mode. How do you setup a
>> single user mode to run the database maintenance? When the database
>> maintenance is done, how do you remove the single user mode? Thanks.
>>
>>
>

Database Maintenance

We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Edition
Server. We setup a database maintenance (Database Integrity and Index,
Reorganize data and indexes, etc. ) to run every week. However, the report
shows that the maintenance job did not run because the database needs to be
in a single user mode. How do you setup a single user mode to run the
database maintenance? When the database maintenance is done, how do you
remove the single user mode? Thanks.Uncheck the "Attempt to repair minor problems" checkbox. All this does is
hide problems until they become unfixable.
Run DBCC CHECKDB manually. You will find you have a problem. Fix the
problem. You will likely have to take the system offline to fix it.
Database corruption issues are very often due to disk subsystem failures.
Check on that and repair if necessary.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. We setup a database maintenance (Database Integrity and
> Index, Reorganize data and indexes, etc. ) to run every week. However,
> the report shows that the maintenance job did not run because the database
> needs to be in a single user mode. How do you setup a single user mode to
> run the database maintenance? When the database maintenance is done, how
> do you remove the single user mode? Thanks.
>|||Thanks very much for your prompt response, Geoff.
If I run DBCC CHECKDB manually, what kind of problems do you expect that I
will encounter? Normally, are these problems easy to fix? Thanks.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23h63CRMOGHA.2268@.TK2MSFTNGP09.phx.gbl...
> Uncheck the "Attempt to repair minor problems" checkbox. All this does is
> hide problems until they become unfixable.
> Run DBCC CHECKDB manually. You will find you have a problem. Fix the
> problem. You will likely have to take the system offline to fix it.
> Database corruption issues are very often due to disk subsystem failures.
> Check on that and repair if necessary.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
>|||How do you take the system offline to fix a problem?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23h63CRMOGHA.2268@.TK2MSFTNGP09.phx.gbl...
> Uncheck the "Attempt to repair minor problems" checkbox. All this does is
> hide problems until they become unfixable.
> Run DBCC CHECKDB manually. You will find you have a problem. Fix the
> problem. You will likely have to take the system offline to fix it.
> Database corruption issues are very often due to disk subsystem failures.
> Check on that and repair if necessary.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
>|||Answering both responses.
I don't know what kinds of problems you will find. You can run DBCC CHECKDB
anytime, but it does create a significant load on the system. I would do it
at a low activity time. To do a repair, you first have to take the database
into single-user mode. Both topics are covered in BOL under DBCC CHECKDB
and DBCC DBREPAIR. I suggest you do a LOT of reading before trying
anything.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OLSGtcMOGHA.3924@.TK2MSFTNGP14.phx.gbl...
> How do you take the system offline to fix a problem?
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23h63CRMOGHA.2268@.TK2MSFTNGP09.phx.gbl...
>|||Thanks very much for your prompt response, Geoff.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OKBZgjMOGHA.3576@.TK2MSFTNGP15.phx.gbl...
> Answering both responses.
> I don't know what kinds of problems you will find. You can run DBCC
> CHECKDB anytime, but it does create a significant load on the system. I
> would do it at a low activity time. To do a repair, you first have to
> take the database into single-user mode. Both topics are covered in BOL
> under DBCC CHECKDB and DBCC DBREPAIR. I suggest you do a LOT of reading
> before trying anything.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OLSGtcMOGHA.3924@.TK2MSFTNGP14.phx.gbl...
>

Database Mail Works Locally but not from Web

I'm building a web site in Visual Web Developer Express on a SQL Server 2005 Developer Edition database, on XP Pro with IIS 5.1 up and running.

Database Mail is configured and works well from the VWD environment. I can launch the site locally from VWD and the stored procedures that call the database mail functions execute perfectly.

However, when I copy the site from the development folder under VWD to my IIS default web page, nothing is ever generated from database mail. I can open the site in IIS and everything looks like it's responding correctly (data updates, refreshes etc) but the behind-the-scenes processes that should be generating email traffic don't do anything.

Review of the database mail log through SQL Server Management Studio shows no activity at all during the timeframe of the "on line" IIS sessions, so it appears that the process isn't hearing anything calling it (or is ignoring the calls if they are happening).

Why would it work in one environment and not another on the same machine? Is there a setup configuration or permissions issue that I've missed somewhere?

Thanks in advance.

I suggest it is a permissions thing. I suggest this is asked in the development forums, in how to conifgure your website to talk to your database with the correct permissions.|||

You were correct, the sp_send_dbmail SPROC used by my stored procedure resides in the MSDB database. The default configuration does not include the ASPNET account with any permissions. Once I found the SPROC and granted Execute permission to ASPNET, everything started working as intended. It's magic!