It's possible to create a maintenance plan with Enterprise manager

It's possible to create a maintenance plan with Enterprise manager in my MSDE
db?
When I try to create a "maintenance plan" I have blank menu (for example
"Use this directory" or "remove files older than" or "backup file extension"
).
Any help will be appreciated.
Thanks
hi Andrea,
andrea favero wrote:
> It's possible to create a maintenance plan with Enterprise manager in
> my MSDE db?
> When I try to create a "maintenance plan" I have blank menu (for
> example "Use this directory" or "remove files older than" or "backup
> file extension" ).
> Any help will be appreciated.
> Thanks
yes it is... the produced maintenance plan will result in a number of jobs
scheduled using SQL Server Agent scheduler...
at schedule occuring, the Job will execute the included job step(s) calling
the maintenance plan runtime and it will be processed...
the properties you are specifying regard "where do you want the backup file
to be stored", so you have to provide the full path of the database backups
browsing (or typing) the actual folder from the SQL Server OS point of
view..
"remove files older than" specifies to delete old backups (older then N
minutes/hours/days/etc :D), but probably a missing piece in MSDE package
does not fill those properties automatically (and you wont be able to set
this manually)
"backup file extension" means what the default extension will be for the
created physical files... again, probably a missing piece in MSDE package
does not fill those properties automatically..
you could probably go on and later manually edit the job step, where a call
to xp_sqlmaint is performed in the way
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
4BDC174A-0C83-4B10-9054-D7388950FF8F -Rpt "C:\Programmi\Microsoft SQL
Server\MSSQL\LOG\DB Maintenance
Plan14.txt" -WriteHistory -VrfyBackup -BkUpMedia
ISK -BkUpDB -UseDefDir -DelBkUps 0 -BkExt "bak"'
and so modifying the -DelBkUps 0 in
-DelBkUps 1days or whatever... but you have to manually dig in the sqlmaint
parameter list
(http://msdn.microsoft.com/library/de...maint_19ix.asp)
personally I do not like SQL Server 7.0 and 2000 maintenance plan utility
and I strongly prefer writing my job by hand specifying the actual
statements that will be perfomed instead of assuming the black box (and
buggy) of maintenance plan will do what I expect to be done...
SQL Server 2005 modified that behavior, but SQLExpress is not provided with
the maintenance plan runtime and with the SQLServer Agent anymore, thus you
have to resort on third party (or home made) scheduler or on the native OS
AT scheduler like in http://www.sqldbatips.com/showarticle.asp?ID=29
BTW, as MSDE usuer, you are not likely supposed to legally interact with it
via Enterprise Manager or Query Analyzer..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Issue with job run setup in Enterprise Manager

Hello All,
I have a job that consist of over 120 steps. I was able to setup it in Enter
prise Manager and run it. However, the job history can only show display 100
job steps 20 other job steps were missing. Is there a limit set on sysjobhi
story table or am I looking
at the wrong table? Please advice.
Thanks.
DavidThat is very interesting, and I do not know if it is related to the number
of histories per job, but maybe worth a try...
In SEM right click SQL Agent and go to the tab with Job history setup and
try both checking unlimited, and/or max histories per job to something like
300... See if that helps..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:A58F9373-EFBA-4426-A2CB-2E14328B18B9@.microsoft.com...
> Hello All,
> I have a job that consist of over 120 steps. I was able to setup it in
Enterprise Manager and run it. However, the job history can only show
display 100 job steps 20 other job steps were missing. Is there a limit set
on sysjobhistory table or am I looking at the wrong table? Please advice.
> Thanks.
> David

Issue with job run setup in Enterprise Manager

Hello All,
I have a job that consist of over 120 steps. I was able to setup it in Enterprise Manager and run it. However, the job history can only show display 100 job steps 20 other job steps were missing. Is there a limit set on sysjobhistory table or am I looking
at the wrong table? Please advice.
Thanks.
David
That is very interesting, and I do not know if it is related to the number
of histories per job, but maybe worth a try...
In SEM right click SQL Agent and go to the tab with Job history setup and
try both checking unlimited, and/or max histories per job to something like
300... See if that helps..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:A58F9373-EFBA-4426-A2CB-2E14328B18B9@.microsoft.com...
> Hello All,
> I have a job that consist of over 120 steps. I was able to setup it in
Enterprise Manager and run it. However, the job history can only show
display 100 job steps 20 other job steps were missing. Is there a limit set
on sysjobhistory table or am I looking at the wrong table? Please advice.
> Thanks.
> David

Issue with job run setup in Enterprise Manager

Hello All
I have a job that consist of over 120 steps. I was able to setup it in Enterprise Manager and run it. However, the job history can only show display 100 job steps 20 other job steps were missing. Is there a limit set on sysjobhistory table or am I looking at the wrong table? Please advice
Thanks
DavidThat is very interesting, and I do not know if it is related to the number
of histories per job, but maybe worth a try...
In SEM right click SQL Agent and go to the tab with Job history setup and
try both checking unlimited, and/or max histories per job to something like
300... See if that helps..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:A58F9373-EFBA-4426-A2CB-2E14328B18B9@.microsoft.com...
> Hello All,
> I have a job that consist of over 120 steps. I was able to setup it in
Enterprise Manager and run it. However, the job history can only show
display 100 job steps 20 other job steps were missing. Is there a limit set
on sysjobhistory table or am I looking at the wrong table? Please advice.
> Thanks.
> David

Issue with Attaching database (MS SQL Server 2000)

Attach a database as MYDB_X using Enterprise manager. (File names:
MYDB_X.MDF & MYDB_X_LOG.LDF)
Detach this database,
Rename the files as MYDB_X11.MDF & MYDB_X11_LOG.LDF
Select this MDF file in Attach Database Dlg of Enterprise manager.
"Attach As" gets populated as MYDB_X (Name as last attached)
Attach DB as MYDB_X11.
Detach this database,
Rename the files as MYDB_X.MDF & MYDB_X_LOG.LDF
Select this MDF file in Attach Database Dlg of Enterprise manager.
"Attach As" gets populated as MYDB_X11 (Name as last attached)
Attach DB as MYDB_X.
Detach this database,
Select this MDF file in Attach Database Dlg of Enterprise manager,
"Attach As" gets populated as MYDB_X11
When MDF file is selected shouldnt it get populated with MYDB_X? Or how to
make sql server remember the last "Attach As"'
It seems that, "Database Name" property doesnt get updated everytime in Db
attach process... If database name length is more then only its updating.
DhirenHi
I think this is a known issue http://tinyurl.com/jk8fr, the workaround would
be to use sp_renamedb and attach it as the original name. If you are
attaching using sp_attach_db then it would not be an issue.
John
"Tinu" wrote:
> Attach a database as MYDB_X using Enterprise manager. (File names:
> MYDB_X.MDF & MYDB_X_LOG.LDF)
> Detach this database,
> Rename the files as MYDB_X11.MDF & MYDB_X11_LOG.LDF
> Select this MDF file in Attach Database Dlg of Enterprise manager.
> "Attach As" gets populated as MYDB_X (Name as last attached)
> Attach DB as MYDB_X11.
> Detach this database,
> Rename the files as MYDB_X.MDF & MYDB_X_LOG.LDF
> Select this MDF file in Attach Database Dlg of Enterprise manager.
> "Attach As" gets populated as MYDB_X11 (Name as last attached)
> Attach DB as MYDB_X.
> Detach this database,
> Select this MDF file in Attach Database Dlg of Enterprise manager,
> "Attach As" gets populated as MYDB_X11
> When MDF file is selected shouldnt it get populated with MYDB_X? Or how to
> make sql server remember the last "Attach As"'
> It seems that, "Database Name" property doesnt get updated everytime in Db
> attach process... If database name length is more then only its updating.
> Dhiren
>
>

Issue with Attaching database (MS SQL Server 2000)

Attach a database as MYDB_X using Enterprise manager. (File names:
MYDB_X.MDF & MYDB_X_LOG.LDF)
Detach this database,
Rename the files as MYDB_X11.MDF & MYDB_X11_LOG.LDF
Select this MDF file in Attach Database Dlg of Enterprise manager.
"Attach As" gets populated as MYDB_X (Name as last attached)
Attach DB as MYDB_X11.
Detach this database,
Rename the files as MYDB_X.MDF & MYDB_X_LOG.LDF
Select this MDF file in Attach Database Dlg of Enterprise manager.
"Attach As" gets populated as MYDB_X11 (Name as last attached)
Attach DB as MYDB_X.
Detach this database,
Select this MDF file in Attach Database Dlg of Enterprise manager,
"Attach As" gets populated as MYDB_X11
When MDF file is selected shouldnt it get populated with MYDB_X? Or how to
make sql server remember the last "Attach As"'
It seems that, "Database Name" property doesnt get updated everytime in Db
attach process... If database name length is more then only its updating.
DhirenHi
I think this is a known issue http://tinyurl.com/jk8fr, the workaround would
be to use sp_renamedb and attach it as the original name. If you are
attaching using sp_attach_db then it would not be an issue.
John
"Tinu" wrote:

> Attach a database as MYDB_X using Enterprise manager. (File names:
> MYDB_X.MDF & MYDB_X_LOG.LDF)
> Detach this database,
> Rename the files as MYDB_X11.MDF & MYDB_X11_LOG.LDF
> Select this MDF file in Attach Database Dlg of Enterprise manager.
> "Attach As" gets populated as MYDB_X (Name as last attached)
> Attach DB as MYDB_X11.
> Detach this database,
> Rename the files as MYDB_X.MDF & MYDB_X_LOG.LDF
> Select this MDF file in Attach Database Dlg of Enterprise manager.
> "Attach As" gets populated as MYDB_X11 (Name as last attached)
> Attach DB as MYDB_X.
> Detach this database,
> Select this MDF file in Attach Database Dlg of Enterprise manager,
> "Attach As" gets populated as MYDB_X11
> When MDF file is selected shouldnt it get populated with MYDB_X? Or how to
> make sql server remember the last "Attach As"'
> It seems that, "Database Name" property doesnt get updated everytime in Db
> attach process... If database name length is more then only its updating.
> Dhiren
>
>

Issue installing SQL 2000 Enterprise

I need some help, I am attempting to install SQL 2k Enterprise and nothing is happening. When I attempt to start the installation again, I get a message of "Another instance is already running."

Can anyone help me with this? I need to have this installed tonight for work I need to do tomorrow.

Thanks

the error message says that Setp/Autorun is already running. What is the OS on this box. You need to have server version to install Enterprise Edition of SQL Server. If the os is not Server version(windows 2000 server/2003/NT) you can only install Client tool

Madhu

|||

I faced this type of issue before because the installation was aborted in the middle abnormally. And when i started it again it said another instance is already running. But after restarting the server it was thru.

Not sure if that is the same case with you...

Issue installing SQL 2000 Enterprise

I need some help, I am attempting to install SQL 2k Enterprise and nothing is happening. When I attempt to start the installation again, I get a message of "Another instance is already running."

Can anyone help me with this? I need to have this installed tonight for work I need to do tomorrow.

Thanks

the error message says that Setp/Autorun is already running. What is the OS on this box. You need to have server version to install Enterprise Edition of SQL Server. If the os is not Server version(windows 2000 server/2003/NT) you can only install Client tool

Madhu

|||

I faced this type of issue before because the installation was aborted in the middle abnormally. And when i started it again it said another instance is already running. But after restarting the server it was thru.

Not sure if that is the same case with you...

Issue in setting up the database Mirrioring environment for SQL Server 2005.

Environment:SQL Server 2005 Enterprise in Win2k3 Enterprise on 32(x86) bit machine

I am able to enable the Trace Flag 1400 using DBCC TRACEON (1400) GO. Only then we can able to configure for the ENDPOINTS.

I successfully configured the ENDPOINTS for both the principal server and Mirror server .And then when I started the START MIRRORING.

I got the error message. Please find the Message below.

An error occured while starting mirroring.

additional Information:
:..>Alter failed for Database 'KQDB', (Microsoft SqlServer.Smo)

:..>An exception occured while executing a Transact-SQL statement or batch
[Microsoft SqlServer.Connection.info]

:..>Database mirroring Transport is disabled in the endpoint configuration.
[Microsft SQL Server,Error: 1486]

If anyone have a solution on how to setup a database mirroring environment.Please send.

You must start up the sql service with trace flag 1400. It is not enough to use DBCC TRACE ON.

Thanks,

Mark

|||I've been encountering the same issue. I've set the trace flag on startup, and still have no luck.
I've gone through every step in the online help, verified that BOTH server instances are listening (the pids corresponds to the ports) and I cannot shake this message:

"Database Mirroring Transport is disabled in the endpoint configuration."

The error comes following the command:

alter database AdventureWorks SET PARTNER = 'TCP://10.0.25.72:5022'
go

It does not seem to matter what port I enter, and it doesn't matter what the IP address is. I've tried this on both the Mirror and on the Primary (ie - in every order).

The mirroring endpoints seem be created properly. I've explored all steps in the msdn "Troubleshooting Database Mirroring Setup" document, checking the various system tables for status, etc. but it is to no avail.

I disabled the 'VIA' protocol in the Configuartion Manager, one of the hints I found from the various newsgroups i've browsed.

I am trying to mirror (without a witness) between two instances on the same server. I am well aware that this is not supported, but I need to kick the tires in a testing playground.

Is this a common problem? The lack of postings with this issue indicate that it may not be, but honestly, i'm stymied.

If anyone has encountered and solved this, please respond, and hopefully it will help others as well.

Cheers,

brentj

|||Can you just please tell use how to start the sql service with trace flag 1400.|||

chanmm wrote:

Can you just please tell use how to start the sql service with trace flag 1400.

You don't need the trace flag if you install SP1 which has now released.

Otherwise if SP1 isn't yet an option (which it really should be if you want to use db mirroring), you can add -T1400 as a startup parameter via the SQL Configuration Manager, properties of the SQL Server service -> advanced tab ->Startup Parameters.

it's not particularly well indexed or cross-referenced but BOL has details here :

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/c82d19e5-5557-4235-9a70-37983607a1fd.htm

thx, Simon.

|||I'm wondering if the thread started for this post resolved this issue? I have set Trace Flag 1400 "-T1400;..." in startup configuration options, rebooted and restarted servers and still not able to mirror. Also given the error "Database Mirroring Transport is disabled."

Anyone figure this out? Next I install SQL 2005 SP1.|||To update on my experience:
I installed SP1 and interestingly it even strips the Trace Flag 1400 out of the startup options for you so you don't leave that remnant of a failed Mirroring Attempt - good work guys!

I got an asynchronous mirror working after installing SQL 2005 SP1 but have not fully tested it.|||Sample is there in the updated SQL BOL docs. No gotchas except the fact that security configuration is the MOST critical. If you get that done, the rest is a breeze.

Issue in setting up the database Mirrioring environment for SQL Server 2005.

Environment:SQL Server 2005 Enterprise in Win2k3 Enterprise on 32(x86) bit machine

I am able to enable the Trace Flag 1400 using DBCC TRACEON (1400) GO. Only then we can able to configure for the ENDPOINTS.

I successfully configured the ENDPOINTS for both the principal server and Mirror server .And then when I started the START MIRRORING.

I got the error message. Please find the Message below.

An error occured while starting mirroring.

additional Information:
:..>Alter failed for Database 'KQDB', (Microsoft SqlServer.Smo)

:..>An exception occured while executing a Transact-SQL statement or batch
[Microsoft SqlServer.Connection.info]

:..>Database mirroring Transport is disabled in the endpoint configuration.
[Microsft SQL Server,Error: 1486]

If anyone have a solution on how to setup a database mirroring environment.Please send.

You must start up the sql service with trace flag 1400. It is not enough to use DBCC TRACE ON.

Thanks,

Mark

|||I've been encountering the same issue. I've set the trace flag on startup, and still have no luck.
I've gone through every step in the online help, verified that BOTH server instances are listening (the pids corresponds to the ports) and I cannot shake this message:

"Database Mirroring Transport is disabled in the endpoint configuration."

The error comes following the command:

alter database AdventureWorks SET PARTNER = 'TCP://10.0.25.72:5022'
go

It does not seem to matter what port I enter, and it doesn't matter what the IP address is. I've tried this on both the Mirror and on the Primary (ie - in every order).

The mirroring endpoints seem be created properly. I've explored all steps in the msdn "Troubleshooting Database Mirroring Setup" document, checking the various system tables for status, etc. but it is to no avail.

I disabled the 'VIA' protocol in the Configuartion Manager, one of the hints I found from the various newsgroups i've browsed.

I am trying to mirror (without a witness) between two instances on the same server. I am well aware that this is not supported, but I need to kick the tires in a testing playground.

Is this a common problem? The lack of postings with this issue indicate that it may not be, but honestly, i'm stymied.

If anyone has encountered and solved this, please respond, and hopefully it will help others as well.

Cheers,

brentj

|||Can you just please tell use how to start the sql service with trace flag 1400.|||

chanmm wrote:

Can you just please tell use how to start the sql service with trace flag 1400.

You don't need the trace flag if you install SP1 which has now released.

Otherwise if SP1 isn't yet an option (which it really should be if you want to use db mirroring), you can add -T1400 as a startup parameter via the SQL Configuration Manager, properties of the SQL Server service -> advanced tab ->Startup Parameters.

it's not particularly well indexed or cross-referenced but BOL has details here :

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/c82d19e5-5557-4235-9a70-37983607a1fd.htm

thx, Simon.

|||I'm wondering if the thread started for this post resolved this issue? I have set Trace Flag 1400 "-T1400;..." in startup configuration options, rebooted and restarted servers and still not able to mirror. Also given the error "Database Mirroring Transport is disabled."

Anyone figure this out? Next I install SQL 2005 SP1.|||To update on my experience:
I installed SP1 and interestingly it even strips the Trace Flag 1400 out of the startup options for you so you don't leave that remnant of a failed Mirroring Attempt - good work guys!

I got an asynchronous mirror working after installing SQL 2005 SP1 but have not fully tested it.|||Sample is there in the updated SQL BOL docs. No gotchas except the fact that security configuration is the MOST critical. If you get that done, the rest is a breeze.

Issue in setting up the database Mirrioring environment for SQL Server 2005.

Environment:SQL Server 2005 Enterprise in Win2k3 Enterprise on 32(x86) bit machine

I am able to enable the Trace Flag 1400 using DBCC TRACEON (1400) GO. Only then we can able to configure for the ENDPOINTS.

I successfully configured the ENDPOINTS for both the principal server and Mirror server .And then when I started the START MIRRORING.

I got the error message. Please find the Message below.

An error occured while starting mirroring.

additional Information:
:..>Alter failed for Database 'KQDB', (Microsoft SqlServer.Smo)

:..>An exception occured while executing a Transact-SQL statement or batch
[Microsoft SqlServer.Connection.info]

:..>Database mirroring Transport is disabled in the endpoint configuration.
[Microsft SQL Server,Error: 1486]

If anyone have a solution on how to setup a database mirroring environment.Please send.

You must start up the sql service with trace flag 1400. It is not enough to use DBCC TRACE ON.

Thanks,

Mark

|||I've been encountering the same issue. I've set the trace flag on startup, and still have no luck.
I've gone through every step in the online help, verified that BOTH server instances are listening (the pids corresponds to the ports) and I cannot shake this message:

"Database Mirroring Transport is disabled in the endpoint configuration."

The error comes following the command:

alter database AdventureWorks SET PARTNER = 'TCP://10.0.25.72:5022'
go

It does not seem to matter what port I enter, and it doesn't matter what the IP address is. I've tried this on both the Mirror and on the Primary (ie - in every order).

The mirroring endpoints seem be created properly. I've explored all steps in the msdn "Troubleshooting Database Mirroring Setup" document, checking the various system tables for status, etc. but it is to no avail.

I disabled the 'VIA' protocol in the Configuartion Manager, one of the hints I found from the various newsgroups i've browsed.

I am trying to mirror (without a witness) between two instances on the same server. I am well aware that this is not supported, but I need to kick the tires in a testing playground.

Is this a common problem? The lack of postings with this issue indicate that it may not be, but honestly, i'm stymied.

If anyone has encountered and solved this, please respond, and hopefully it will help others as well.

Cheers,

brentj

|||Can you just please tell use how to start the sql service with trace flag 1400.|||

chanmm wrote:

Can you just please tell use how to start the sql service with trace flag 1400.

You don't need the trace flag if you install SP1 which has now released.

Otherwise if SP1 isn't yet an option (which it really should be if you want to use db mirroring), you can add -T1400 as a startup parameter via the SQL Configuration Manager, properties of the SQL Server service -> advanced tab ->Startup Parameters.

it's not particularly well indexed or cross-referenced but BOL has details here :

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/c82d19e5-5557-4235-9a70-37983607a1fd.htm

thx, Simon.

|||I'm wondering if the thread started for this post resolved this issue? I have set Trace Flag 1400 "-T1400;..." in startup configuration options, rebooted and restarted servers and still not able to mirror. Also given the error "Database Mirroring Transport is disabled."

Anyone figure this out? Next I install SQL 2005 SP1.|||To update on my experience:
I installed SP1 and interestingly it even strips the Trace Flag 1400 out of the startup options for you so you don't leave that remnant of a failed Mirroring Attempt - good work guys!

I got an asynchronous mirror working after installing SQL 2005 SP1 but have not fully tested it.|||Sample is there in the updated SQL BOL docs. No gotchas except the fact that security configuration is the MOST critical. If you get that done, the rest is a breeze.

Issue in setting up the database Mirrioring environment for SQL Server 2005.

Environment:SQL Server 2005 Enterprise in Win2k3 Enterprise on 32(x86) bit machine

I am able to enable the Trace Flag 1400 using DBCC TRACEON (1400) GO. Only then we can able to configure for the ENDPOINTS.

I successfully configured the ENDPOINTS for both the principal server and Mirror server .And then when I started the START MIRRORING.

I got the error message. Please find the Message below.

An error occured while starting mirroring.

additional Information:
:..>Alter failed for Database 'KQDB', (Microsoft SqlServer.Smo)

:..>An exception occured while executing a Transact-SQL statement or batch
[Microsoft SqlServer.Connection.info]

:..>Database mirroring Transport is disabled in the endpoint configuration.
[Microsft SQL Server,Error: 1486]

If anyone have a solution on how to setup a database mirroring environment.Please send.

You must start up the sql service with trace flag 1400. It is not enough to use DBCC TRACE ON.

Thanks,

Mark

|||I've been encountering the same issue. I've set the trace flag on startup, and still have no luck.
I've gone through every step in the online help, verified that BOTH server instances are listening (the pids corresponds to the ports) and I cannot shake this message:

"Database Mirroring Transport is disabled in the endpoint configuration."

The error comes following the command:

alter database AdventureWorks SET PARTNER = 'TCP://10.0.25.72:5022'
go

It does not seem to matter what port I enter, and it doesn't matter what the IP address is. I've tried this on both the Mirror and on the Primary (ie - in every order).

The mirroring endpoints seem be created properly. I've explored all steps in the msdn "Troubleshooting Database Mirroring Setup" document, checking the various system tables for status, etc. but it is to no avail.

I disabled the 'VIA' protocol in the Configuartion Manager, one of the hints I found from the various newsgroups i've browsed.

I am trying to mirror (without a witness) between two instances on the same server. I am well aware that this is not supported, but I need to kick the tires in a testing playground.

Is this a common problem? The lack of postings with this issue indicate that it may not be, but honestly, i'm stymied.

If anyone has encountered and solved this, please respond, and hopefully it will help others as well.

Cheers,

brentj

|||Can you just please tell use how to start the sql service with trace flag 1400.|||

chanmm wrote:

Can you just please tell use how to start the sql service with trace flag 1400.

You don't need the trace flag if you install SP1 which has now released.

Otherwise if SP1 isn't yet an option (which it really should be if you want to use db mirroring), you can add -T1400 as a startup parameter via the SQL Configuration Manager, properties of the SQL Server service -> advanced tab ->Startup Parameters.

it's not particularly well indexed or cross-referenced but BOL has details here :

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/c82d19e5-5557-4235-9a70-37983607a1fd.htm

thx, Simon.

|||I'm wondering if the thread started for this post resolved this issue? I have set Trace Flag 1400 "-T1400;..." in startup configuration options, rebooted and restarted servers and still not able to mirror. Also given the error "Database Mirroring Transport is disabled."

Anyone figure this out? Next I install SQL 2005 SP1.|||To update on my experience:
I installed SP1 and interestingly it even strips the Trace Flag 1400 out of the startup options for you so you don't leave that remnant of a failed Mirroring Attempt - good work guys!

I got an asynchronous mirror working after installing SQL 2005 SP1 but have not fully tested it.|||Sample is there in the updated SQL BOL docs. No gotchas except the fact that security configuration is the MOST critical. If you get that done, the rest is a breeze.

Issue in setting up the database Mirrioring environment for SQL Server 2005.

Environment:SQL Server 2005 Enterprise in Win2k3 Enterprise on 32(x86) bit machine

I am able to enable the Trace Flag 1400 using DBCC TRACEON (1400) GO. Only then we can able to configure for the ENDPOINTS.

I successfully configured the ENDPOINTS for both the principal server and Mirror server .And then when I started the START MIRRORING.

I got the error message. Please find the Message below.

An error occured while starting mirroring.

additional Information:
:..>Alter failed for Database 'KQDB', (Microsoft SqlServer.Smo)

:..>An exception occured while executing a Transact-SQL statement or batch
[Microsoft SqlServer.Connection.info]

:..>Database mirroring Transport is disabled in the endpoint configuration.
[Microsft SQL Server,Error: 1486]

If anyone have a solution on how to setup a database mirroring environment.Please send.

You must start up the sql service with trace flag 1400. It is not enough to use DBCC TRACE ON.

Thanks,

Mark

|||I've been encountering the same issue. I've set the trace flag on startup, and still have no luck.
I've gone through every step in the online help, verified that BOTH server instances are listening (the pids corresponds to the ports) and I cannot shake this message:

"Database Mirroring Transport is disabled in the endpoint configuration."

The error comes following the command:

alter database AdventureWorks SET PARTNER = 'TCP://10.0.25.72:5022'
go

It does not seem to matter what port I enter, and it doesn't matter what the IP address is. I've tried this on both the Mirror and on the Primary (ie - in every order).

The mirroring endpoints seem be created properly. I've explored all steps in the msdn "Troubleshooting Database Mirroring Setup" document, checking the various system tables for status, etc. but it is to no avail.

I disabled the 'VIA' protocol in the Configuartion Manager, one of the hints I found from the various newsgroups i've browsed.

I am trying to mirror (without a witness) between two instances on the same server. I am well aware that this is not supported, but I need to kick the tires in a testing playground.

Is this a common problem? The lack of postings with this issue indicate that it may not be, but honestly, i'm stymied.

If anyone has encountered and solved this, please respond, and hopefully it will help others as well.

Cheers,

brentj

|||Can you just please tell use how to start the sql service with trace flag 1400.|||

chanmm wrote:

Can you just please tell use how to start the sql service with trace flag 1400.

You don't need the trace flag if you install SP1 which has now released.

Otherwise if SP1 isn't yet an option (which it really should be if you want to use db mirroring), you can add -T1400 as a startup parameter via the SQL Configuration Manager, properties of the SQL Server service -> advanced tab ->Startup Parameters.

it's not particularly well indexed or cross-referenced but BOL has details here :

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/c82d19e5-5557-4235-9a70-37983607a1fd.htm

thx, Simon.

|||I'm wondering if the thread started for this post resolved this issue? I have set Trace Flag 1400 "-T1400;..." in startup configuration options, rebooted and restarted servers and still not able to mirror. Also given the error "Database Mirroring Transport is disabled."

Anyone figure this out? Next I install SQL 2005 SP1.|||To update on my experience:
I installed SP1 and interestingly it even strips the Trace Flag 1400 out of the startup options for you so you don't leave that remnant of a failed Mirroring Attempt - good work guys!

I got an asynchronous mirror working after installing SQL 2005 SP1 but have not fully tested it.|||Sample is there in the updated SQL BOL docs. No gotchas except the fact that security configuration is the MOST critical. If you get that done, the rest is a breeze.