Mapi profile generator...

Any suggestions on a Profile generator for my SQL servers? I don't want to
install Outlook...thxs.
Are you looking for an email solution without using SQL Mail? Try XPSMTP.
XPSMTP.DLL - SQL Server SMTP Mail XP
http://sqldev.net/xp/xpsmtp.htm
Keith
"Jesse Verdin" <jv@.hotmail.com> wrote in message
news:eyy4cSEuEHA.3788@.TK2MSFTNGP09.phx.gbl...
> Any suggestions on a Profile generator for my SQL servers? I don't want to
> install Outlook...thxs.
>
sql

Mapi profile generator...

Any suggestions on a Profile generator for my SQL servers? I don't want to
install Outlook...thxs.Are you looking for an email solution without using SQL Mail? Try XPSMTP.
XPSMTP.DLL - SQL Server SMTP Mail XP
http://sqldev.net/xp/xpsmtp.htm
--
Keith
"Jesse Verdin" <jv@.hotmail.com> wrote in message
news:eyy4cSEuEHA.3788@.TK2MSFTNGP09.phx.gbl...
> Any suggestions on a Profile generator for my SQL servers? I don't want to
> install Outlook...thxs.
>

Mapi profile generator...

Any suggestions on a Profile generator for my SQL servers? I don't want to
install Outlook...thxs.Are you looking for an email solution without using SQL Mail? Try XPSMTP.
XPSMTP.DLL - SQL Server SMTP Mail XP
http://sqldev.net/xp/xpsmtp.htm
Keith
"Jesse Verdin" <jv@.hotmail.com> wrote in message
news:eyy4cSEuEHA.3788@.TK2MSFTNGP09.phx.gbl...
> Any suggestions on a Profile generator for my SQL servers? I don't want to
> install Outlook...thxs.
>

MAPI Error 22022 in SQL Server 2000

When I try to test the ability to send e-mail to an operator on one of my servers by opening up the properties for the operator and clicking the "test" button, I get the following error:

"Error 22022: SQLServerAgent Error: MAPI error: Table too big."

Has anyone encountered this? What's the resolution?

Can you log in to the server using the same account that the SQL Server Agent is using and send emails that way? If so, try deleting and recreating the pst file for that user.

BTW - you'll likely receive more feedback from another group. This one is dedicated to Notification Services, which despite the similar sounding name, is a completely different technology.

HTH...

Joesql

MAPI Error 22022 in SQL Server 2000

When I try to test the ability to send e-mail to an operator on one of my servers by opening up the properties for the operator and clicking the "test" button, I get the following error:

"Error 22022: SQLServerAgent Error: MAPI error: Table too big."

Has anyone encountered this? What's the resolution?

Can you log in to the server using the same account that the SQL Server Agent is using and send emails that way? If so, try deleting and recreating the pst file for that user.

BTW - you'll likely receive more feedback from another group. This one is dedicated to Notification Services, which despite the similar sounding name, is a completely different technology.

HTH...

Joe

MAPI client for SQL Mail and SNMP Integration

We are trying avoid installing MAPI client, Outlook 2000, on our production
database servers. My boss thinks there is a security threat by installing
Outlook on production servers? Are you all aware of any security issues with
this?
I heard about SNMP integration wiith SQL Server which enables monitoring
database status and sending alerts to pager or email. Did anyone use this?
Using this, can I send alerts regarding SQL Server errors with severity
greater than 19? Any poniters on this topic will be appreciated.I am unaware of any security issues. I have run into some stability and
usability issues woth Outlook and MAPI mail from SQL and SQL agent.
You might want to look at xp_smtp_sendmail from www.sqldev.net. It doesn't
have the seamless integration, but with a little extra work it can do most
everything you will need. It is also much more stable than Outlook on a SQL
console.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Prasad Koukuntla" <prasad.koukuntla@.scapromo.com> wrote in message
news:eoBRa99%23DHA.684@.tk2msftngp13.phx.gbl...
> We are trying avoid installing MAPI client, Outlook 2000, on our
production
> database servers. My boss thinks there is a security threat by installing
> Outlook on production servers? Are you all aware of any security issues
with
> this?
> I heard about SNMP integration wiith SQL Server which enables monitoring
> database status and sending alerts to pager or email. Did anyone use this?
> Using this, can I send alerts regarding SQL Server errors with severity
> greater than 19? Any poniters on this topic will be appreciated.
>
>|||Thank you Geoff.
I too feel that there are no security issues.
I have used xp_smtp_sendmail before, however, this one may require custom
programming to capture the errors and then sending the alerts which we may
not want to do. Thanks.
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23FlnFC%23%23DHA.3220@.TK2MSFTNGP10.phx.gbl...
> I am unaware of any security issues. I have run into some stability and
> usability issues woth Outlook and MAPI mail from SQL and SQL agent.
> You might want to look at xp_smtp_sendmail from www.sqldev.net. It
doesn't
> have the seamless integration, but with a little extra work it can do most
> everything you will need. It is also much more stable than Outlook on a
SQL
> console.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Prasad Koukuntla" <prasad.koukuntla@.scapromo.com> wrote in message
> news:eoBRa99%23DHA.684@.tk2msftngp13.phx.gbl...
> production
installing
> with
this?
>|||Prasad,
To add to the other comments:
You can use xp_smtp_sendmail for event alerts without creating jobs for each
alert, check out http://www.dbmaint.com/SmtpAlerter.asp.
As for the SNMP support: As of 7.0 there are no longer support for SNMP
alerts in SQL Server (I'm far away from an SNMP expert, but I think they
call it Alerts in the SNMP world), only monitoring. IMO, SNMP alerts are
probably more useful than what monitoring is...
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Prasad Koukuntla" <prasad.koukuntla@.scapromo.com> wrote in message
news:eoBRa99%23DHA.684@.tk2msftngp13.phx.gbl...
> We are trying avoid installing MAPI client, Outlook 2000, on our
production
> database servers. My boss thinks there is a security threat by installing
> Outlook on production servers? Are you all aware of any security issues
with
> this?
> I heard about SNMP integration wiith SQL Server which enables monitoring
> database status and sending alerts to pager or email. Did anyone use this?
> Using this, can I send alerts regarding SQL Server errors with severity
> greater than 19? Any poniters on this topic will be appreciated.
>
>|||Thanks Tibor,
I will check it out.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eB1kG7%23%23DHA.2476@.TK2MSFTNGP12.phx.gbl...
> Prasad,
> To add to the other comments:
> You can use xp_smtp_sendmail for event alerts without creating jobs for
each
> alert, check out http://www.dbmaint.com/SmtpAlerter.asp.
> As for the SNMP support: As of 7.0 there are no longer support for SNMP
> alerts in SQL Server (I'm far away from an SNMP expert, but I think they
> call it Alerts in the SNMP world), only monitoring. IMO, SNMP alerts are
> probably more useful than what monitoring is...
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=...ublic.sqlserver
>
> "Prasad Koukuntla" <prasad.koukuntla@.scapromo.com> wrote in message
> news:eoBRa99%23DHA.684@.tk2msftngp13.phx.gbl...
> production
installing
> with
this?
>

MAPI client for SQL Mail and SNMP Integration

We are trying avoid installing MAPI client, Outlook 2000, on our production
database servers. My boss thinks there is a security threat by installing
Outlook on production servers? Are you all aware of any security issues with
this?
I heard about SNMP integration wiith SQL Server which enables monitoring
database status and sending alerts to pager or email. Did anyone use this?
Using this, can I send alerts regarding SQL Server errors with severity
greater than 19? Any poniters on this topic will be appreciated.I am unaware of any security issues. I have run into some stability and
usability issues woth Outlook and MAPI mail from SQL and SQL agent.
You might want to look at xp_smtp_sendmail from www.sqldev.net. It doesn't
have the seamless integration, but with a little extra work it can do most
everything you will need. It is also much more stable than Outlook on a SQL
console.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Prasad Koukuntla" <prasad.koukuntla@.scapromo.com> wrote in message
news:eoBRa99%23DHA.684@.tk2msftngp13.phx.gbl...
> We are trying avoid installing MAPI client, Outlook 2000, on our
production
> database servers. My boss thinks there is a security threat by installing
> Outlook on production servers? Are you all aware of any security issues
with
> this?
> I heard about SNMP integration wiith SQL Server which enables monitoring
> database status and sending alerts to pager or email. Did anyone use this?
> Using this, can I send alerts regarding SQL Server errors with severity
> greater than 19? Any poniters on this topic will be appreciated.
>
>|||Thank you Geoff.
I too feel that there are no security issues.
I have used xp_smtp_sendmail before, however, this one may require custom
programming to capture the errors and then sending the alerts which we may
not want to do. Thanks.
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23FlnFC%23%23DHA.3220@.TK2MSFTNGP10.phx.gbl...
> I am unaware of any security issues. I have run into some stability and
> usability issues woth Outlook and MAPI mail from SQL and SQL agent.
> You might want to look at xp_smtp_sendmail from www.sqldev.net. It
doesn't
> have the seamless integration, but with a little extra work it can do most
> everything you will need. It is also much more stable than Outlook on a
SQL
> console.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Prasad Koukuntla" <prasad.koukuntla@.scapromo.com> wrote in message
> news:eoBRa99%23DHA.684@.tk2msftngp13.phx.gbl...
> > We are trying avoid installing MAPI client, Outlook 2000, on our
> production
> > database servers. My boss thinks there is a security threat by
installing
> > Outlook on production servers? Are you all aware of any security issues
> with
> > this?
> >
> > I heard about SNMP integration wiith SQL Server which enables monitoring
> > database status and sending alerts to pager or email. Did anyone use
this?
> > Using this, can I send alerts regarding SQL Server errors with severity
> > greater than 19? Any poniters on this topic will be appreciated.
> >
> >
> >
>|||search for xpsmtp mail for sql server on internet, its
much more stable and reliable and you can download it for
free. You use to monitor sql jobs, error logs and send any
kind of emails from sql server.
to send alerts, create a job and in step text enter
something like following, don't create a schedule for this
job:
exec master.dbo.xp_smtp_sendmail
@.from = 'MSSQLServer@.server.com',
@.to = '<you@.yourdomain.com>',
@.subject = 'SQL Server errors with
severity greater than 19 occurred',
@.message = '<message>',
@.server = '<YOUR SMPT SERVER>'
Define your alerts for severity greater than 19, and
response to the alert Execute the above job.
hth.
>--Original Message--
>We are trying avoid installing MAPI client, Outlook 2000,
on our production
>database servers. My boss thinks there is a security
threat by installing
>Outlook on production servers? Are you all aware of any
security issues with
>this?
>I heard about SNMP integration wiith SQL Server which
enables monitoring
>database status and sending alerts to pager or email. Did
anyone use this?
>Using this, can I send alerts regarding SQL Server errors
with severity
>greater than 19? Any poniters on this topic will be
appreciated.
>
>.
>|||Okay, I will try this approach. Thanks Guru.
"Guru" <gss20@.hotmail.com> wrote in message
news:192d01c3fbe3$85760c80$a001280a@.phx.gbl...
> search for xpsmtp mail for sql server on internet, its
> much more stable and reliable and you can download it for
> free. You use to monitor sql jobs, error logs and send any
> kind of emails from sql server.
> to send alerts, create a job and in step text enter
> something like following, don't create a schedule for this
> job:
> exec master.dbo.xp_smtp_sendmail
> @.from = 'MSSQLServer@.server.com',
> @.to = '<you@.yourdomain.com>',
> @.subject = 'SQL Server errors with
> severity greater than 19 occurred',
> @.message = '<message>',
> @.server = '<YOUR SMPT SERVER>'
> Define your alerts for severity greater than 19, and
> response to the alert Execute the above job.
> hth.
> >--Original Message--
> >We are trying avoid installing MAPI client, Outlook 2000,
> on our production
> >database servers. My boss thinks there is a security
> threat by installing
> >Outlook on production servers? Are you all aware of any
> security issues with
> >this?
> >
> >I heard about SNMP integration wiith SQL Server which
> enables monitoring
> >database status and sending alerts to pager or email. Did
> anyone use this?
> >Using this, can I send alerts regarding SQL Server errors
> with severity
> >greater than 19? Any poniters on this topic will be
> appreciated.
> >
> >
> >
> >.
> >|||Prasad,
To add to the other comments:
You can use xp_smtp_sendmail for event alerts without creating jobs for each
alert, check out http://www.dbmaint.com/SmtpAlerter.asp.
As for the SNMP support: As of 7.0 there are no longer support for SNMP
alerts in SQL Server (I'm far away from an SNMP expert, but I think they
call it Alerts in the SNMP world), only monitoring. IMO, SNMP alerts are
probably more useful than what monitoring is...
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Prasad Koukuntla" <prasad.koukuntla@.scapromo.com> wrote in message
news:eoBRa99%23DHA.684@.tk2msftngp13.phx.gbl...
> We are trying avoid installing MAPI client, Outlook 2000, on our
production
> database servers. My boss thinks there is a security threat by installing
> Outlook on production servers? Are you all aware of any security issues
with
> this?
> I heard about SNMP integration wiith SQL Server which enables monitoring
> database status and sending alerts to pager or email. Did anyone use this?
> Using this, can I send alerts regarding SQL Server errors with severity
> greater than 19? Any poniters on this topic will be appreciated.
>
>|||Thanks Tibor,
I will check it out.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eB1kG7%23%23DHA.2476@.TK2MSFTNGP12.phx.gbl...
> Prasad,
> To add to the other comments:
> You can use xp_smtp_sendmail for event alerts without creating jobs for
each
> alert, check out http://www.dbmaint.com/SmtpAlerter.asp.
> As for the SNMP support: As of 7.0 there are no longer support for SNMP
> alerts in SQL Server (I'm far away from an SNMP expert, but I think they
> call it Alerts in the SNMP world), only monitoring. IMO, SNMP alerts are
> probably more useful than what monitoring is...
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Prasad Koukuntla" <prasad.koukuntla@.scapromo.com> wrote in message
> news:eoBRa99%23DHA.684@.tk2msftngp13.phx.gbl...
> > We are trying avoid installing MAPI client, Outlook 2000, on our
> production
> > database servers. My boss thinks there is a security threat by
installing
> > Outlook on production servers? Are you all aware of any security issues
> with
> > this?
> >
> > I heard about SNMP integration wiith SQL Server which enables monitoring
> > database status and sending alerts to pager or email. Did anyone use
this?
> > Using this, can I send alerts regarding SQL Server errors with severity
> > greater than 19? Any poniters on this topic will be appreciated.
> >
> >
> >
>sql

Many databases on one or multiple SQL2000 servers

Hi there. We currently have an application which requires separate database
s
for each "project" we work on. We are in the process of replacing our 2 SQL
2000 servers and are unsure whether to purchase 1 or 2 servers. Previously,
we implemented with 2 servers due to performance reasons. That was back on
SQL 7 though.
We have approximately 400 databases which range in size from .5GB to about
3GB. These cannot be collapsed into fewer databases. SQL2005 is not an
option at this time (gotta love software companies that don't keep up with
the times!
So, do I get 2 servers or a single (larger in processor and memory) server?
--John J. Berlo
Lend Lease Corportation
Collaboration TechnologiesHi John,
I have found that there are more variables involved in a decision such as
this. How many users, the number of concurrent queries, the design of the
queries, etc., all play a big factor in how much processing power will be
required.
The number of databases is higher than normal, but not unheard of. Our
accounting system currently requires us to operate a server with over 900
databases. I am running this on a single server without issue. The
databases, though numerous, are well designed and support our 200 users with
an acceptable level of performance. The hardware is a 4-way server with 6GB
of RAM and SQL 2000 Enterprise Edition. The disk array is an IBM SAN via 2G
B
fiber.
My guess would be that disk and RAM could be your biggest true enemy in such
an implementation. If you can buy a decent server with 6GB or so of RAM and
a good disk array with quite a few spindles, say 20, you should be able to
support up to 200 - 300 users fairly well.
Hope this helps... also remember, there are a lot of variables and this is
just my "professional" opinion based on the limited information you gave us.
Bryan
"John J. Berlo" wrote:

> Hi there. We currently have an application which requires separate databa
ses
> for each "project" we work on. We are in the process of replacing our 2 S
QL
> 2000 servers and are unsure whether to purchase 1 or 2 servers. Previousl
y,
> we implemented with 2 servers due to performance reasons. That was back o
n
> SQL 7 though.
> We have approximately 400 databases which range in size from .5GB to about
> 3GB. These cannot be collapsed into fewer databases. SQL2005 is not an
> option at this time (gotta love software companies that don't keep up with
> the times!
> So, do I get 2 servers or a single (larger in processor and memory) server
?
> --John J. Berlo
> Lend Lease Corportation
> Collaboration Technologies|||Brian,
Thanks for the information. On our current servers, we are seeing
approximately 650 concurrent users. Not an enourmous amount, but one that
concerns us whether a single server is the best way to go.
If money was no object, I would do a 2-server active-active cluster, but SQL
Enterprise is a large jump in price than standard. So, the situation as I
see it leaves us with 2 choices:
1) Move to a single 2003 Server Enterprise server with 6-8GB RAM and 2-dual
core processors
-or-
2) Stay on 2 2003 Server standard servers with 4GB RAM and a single
dual-core processor
(both with SQL standard licenses and hooked to a very robust SAN).
Thoughts?
--John J. Berlo
Lend Lease Corportation
Collaboration Technologies
"Bryan Ivie" wrote:
[vbcol=seagreen]
> Hi John,
> I have found that there are more variables involved in a decision such as
> this. How many users, the number of concurrent queries, the design of the
> queries, etc., all play a big factor in how much processing power will be
> required.
> The number of databases is higher than normal, but not unheard of. Our
> accounting system currently requires us to operate a server with over 900
> databases. I am running this on a single server without issue. The
> databases, though numerous, are well designed and support our 200 users wi
th
> an acceptable level of performance. The hardware is a 4-way server with 6
GB
> of RAM and SQL 2000 Enterprise Edition. The disk array is an IBM SAN via
2GB
> fiber.
> My guess would be that disk and RAM could be your biggest true enemy in su
ch
> an implementation. If you can buy a decent server with 6GB or so of RAM a
nd
> a good disk array with quite a few spindles, say 20, you should be able to
> support up to 200 - 300 users fairly well.
> Hope this helps... also remember, there are a lot of variables and this i
s
> just my "professional" opinion based on the limited information you gave u
s.
> Bryan
>
> "John J. Berlo" wrote:
>

Many databases on one or multiple SQL2000 servers

Hi there. We currently have an application which requires separate databases
for each "project" we work on. We are in the process of replacing our 2 SQL
2000 servers and are unsure whether to purchase 1 or 2 servers. Previously,
we implemented with 2 servers due to performance reasons. That was back on
SQL 7 though.
We have approximately 400 databases which range in size from .5GB to about
3GB. These cannot be collapsed into fewer databases. SQL2005 is not an
option at this time (gotta love software companies that don't keep up with
the times! :)
So, do I get 2 servers or a single (larger in processor and memory) server?
--John J. Berlo
Lend Lease Corportation
Collaboration TechnologiesHi John,
I have found that there are more variables involved in a decision such as
this. How many users, the number of concurrent queries, the design of the
queries, etc., all play a big factor in how much processing power will be
required.
The number of databases is higher than normal, but not unheard of. Our
accounting system currently requires us to operate a server with over 900
databases. I am running this on a single server without issue. The
databases, though numerous, are well designed and support our 200 users with
an acceptable level of performance. The hardware is a 4-way server with 6GB
of RAM and SQL 2000 Enterprise Edition. The disk array is an IBM SAN via 2GB
fiber.
My guess would be that disk and RAM could be your biggest true enemy in such
an implementation. If you can buy a decent server with 6GB or so of RAM and
a good disk array with quite a few spindles, say 20, you should be able to
support up to 200 - 300 users fairly well.
Hope this helps... also remember, there are a lot of variables and this is
just my "professional" opinion based on the limited information you gave us.
Bryan
"John J. Berlo" wrote:
> Hi there. We currently have an application which requires separate databases
> for each "project" we work on. We are in the process of replacing our 2 SQL
> 2000 servers and are unsure whether to purchase 1 or 2 servers. Previously,
> we implemented with 2 servers due to performance reasons. That was back on
> SQL 7 though.
> We have approximately 400 databases which range in size from .5GB to about
> 3GB. These cannot be collapsed into fewer databases. SQL2005 is not an
> option at this time (gotta love software companies that don't keep up with
> the times! :)
> So, do I get 2 servers or a single (larger in processor and memory) server?
> --John J. Berlo
> Lend Lease Corportation
> Collaboration Technologies|||Brian,
Thanks for the information. On our current servers, we are seeing
approximately 650 concurrent users. Not an enourmous amount, but one that
concerns us whether a single server is the best way to go.
If money was no object, I would do a 2-server active-active cluster, but SQL
Enterprise is a large jump in price than standard. So, the situation as I
see it leaves us with 2 choices:
1) Move to a single 2003 Server Enterprise server with 6-8GB RAM and 2-dual
core processors
-or-
2) Stay on 2 2003 Server standard servers with 4GB RAM and a single
dual-core processor
(both with SQL standard licenses and hooked to a very robust SAN).
Thoughts?
--John J. Berlo
Lend Lease Corportation
Collaboration Technologies
"Bryan Ivie" wrote:
> Hi John,
> I have found that there are more variables involved in a decision such as
> this. How many users, the number of concurrent queries, the design of the
> queries, etc., all play a big factor in how much processing power will be
> required.
> The number of databases is higher than normal, but not unheard of. Our
> accounting system currently requires us to operate a server with over 900
> databases. I am running this on a single server without issue. The
> databases, though numerous, are well designed and support our 200 users with
> an acceptable level of performance. The hardware is a 4-way server with 6GB
> of RAM and SQL 2000 Enterprise Edition. The disk array is an IBM SAN via 2GB
> fiber.
> My guess would be that disk and RAM could be your biggest true enemy in such
> an implementation. If you can buy a decent server with 6GB or so of RAM and
> a good disk array with quite a few spindles, say 20, you should be able to
> support up to 200 - 300 users fairly well.
> Hope this helps... also remember, there are a lot of variables and this is
> just my "professional" opinion based on the limited information you gave us.
> Bryan
>
> "John J. Berlo" wrote:
> > Hi there. We currently have an application which requires separate databases
> > for each "project" we work on. We are in the process of replacing our 2 SQL
> > 2000 servers and are unsure whether to purchase 1 or 2 servers. Previously,
> > we implemented with 2 servers due to performance reasons. That was back on
> > SQL 7 though.
> >
> > We have approximately 400 databases which range in size from .5GB to about
> > 3GB. These cannot be collapsed into fewer databases. SQL2005 is not an
> > option at this time (gotta love software companies that don't keep up with
> > the times! :)
> >
> > So, do I get 2 servers or a single (larger in processor and memory) server?
> >
> > --John J. Berlo
> > Lend Lease Corportation
> > Collaboration Technologies

Manually transfer of merge data

I need to replicate data between two servers through modem. The
problem is that the modem always disconnect in the middle of the
process.
This is not the initial replication. There were some success until the
last days, and there are data changes in both publisher and subscriber
that need to be merged.
Is it possible to transfer the merge data manually?
Thanks
You can't do this manually. You could change the merge agent properties to
optimize for an unreliable link - eg reduce the '...GenerationsPerBatch'
counters, and force it to restart after a network failure (3rd step -> 1st
step).
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Manual to configure snapshot replication between two SQL 2000 Servers

Is there anywhere an easy guide available how to install and configure a snapshot replication between two SQL 2000 servers? What important points have to be checked etc.
Thanks
mipohttp://www.mssqlserver.com/

managing ssis behind a firewall

Just a comment for people who are experiencing problems.

We are managing our ssis servers from a subnet that is blocked off from our production network via a firewall as I'm sure many people do. The problem we were facing was that when we tried to connect to an ssis instance we could get to dcom through port 135 which BOL states should be open. What BOL does not say is that dcom then arbitrarily assigns a high numbered port for the management interface to connect to. This was not very desirable since we would have had to open a gaping hole in our firewall.

The solution we have come up with is in windows 2003 you can map a static port to a com server through a registry key.

First you must find the applicationid (guid) of MsDtsServer in the HKEY_CLASSES_ROOT\AppID\ registry hive. From what I can tell this is always {F38B7F09-979B-4241-80D9-2EADED02954F}.

You then need to specify a new REG_MULTI_SZ value named Endpoints with the value of ncacn_ip_tcp,0,<port number>. You can only set one port, not a range.

Now you should be able to restart SSIS and connect through the port you specified (you still need port 135 for dcom though).

The specific process is detailed in more in http://support.microsoft.com/default.aspx?scid=kb;en-us;Q312960

Let me know what you guys think, we haven't put this through the testing gauntlet yet

This was very helpful - wish MS provided this kind of answer. Thanks!

managing SQL server 2000 servers with 2K5 management studio

For some reason when I try to use sql 2005 management studio to manage a sql server 2000 server and attempt to use activity monitor to view processes I get an error (see below) (BTW I love being able to copy the message text). I can perform this operation from enterprise manager without issue. Is this a problem with management studio?

TITLE: Microsoft SQL Server Management Studio

Cannot show requested dialog.

ADDITIONAL INFORMATION:

Unable to execute requested command.

Unable to launch Activity Monitor. You may not have sufficient permissions. (ActivityMonitor)

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)

Could you please confirm that you can connect to the server otherwise and run a query (say select * from sysprocesses) and only activity monitor is not working.

What are the versions of Management Tools and SQL Server you have? What is the configuration? Are you doing it on the same machine or going over network? Was it this way from the beginning?

Boris.

|||That query worked fine. It was being accessed over a network. I was able to run querys on databases. However the server did have an issue with 1 database not being accessable. Now that the server issue has been corrected (the drive repaired). It seems to work fine from management studio. I am going to try to recreate the original server in a lab to see if this is some sort of bug in 2k5.|||

I do this all the time, but as the DBA I have the luxury of logging into the 2K box as 'sa'. I would guess the permissions issue is the root here... what account are you using to login? What roles/permissions does the account have?

More info could help us all help you.

|||

You can connect a profiler to your SQL Server 2000 instance and see what is going on when you double click on Activity Monitor in Management Studio. Since you are getting a timeout error and you had a suspect database, one of the queries did not return result in time and thus the message.

If you are able to reproduce the problem in your lab environment, please post the results here.

Thank you,

Boris.

managing SQL server 2000 servers with 2K5 management studio

For some reason when I try to use sql 2005 management studio to manage a sql server 2000 server and attempt to use activity monitor to view processes I get an error (see below) (BTW I love being able to copy the message text). I can perform this operation from enterprise manager without issue. Is this a problem with management studio?

TITLE: Microsoft SQL Server Management Studio

Cannot show requested dialog.

ADDITIONAL INFORMATION:

Unable to execute requested command.

Unable to launch Activity Monitor. You may not have sufficient permissions. (ActivityMonitor)

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)

Could you please confirm that you can connect to the server otherwise and run a query (say select * from sysprocesses) and only activity monitor is not working.

What are the versions of Management Tools and SQL Server you have? What is the configuration? Are you doing it on the same machine or going over network? Was it this way from the beginning?

Boris.

|||That query worked fine. It was being accessed over a network. I was able to run querys on databases. However the server did have an issue with 1 database not being accessable. Now that the server issue has been corrected (the drive repaired). It seems to work fine from management studio. I am going to try to recreate the original server in a lab to see if this is some sort of bug in 2k5.|||

I do this all the time, but as the DBA I have the luxury of logging into the 2K box as 'sa'. I would guess the permissions issue is the root here... what account are you using to login? What roles/permissions does the account have?

More info could help us all help you.

|||

You can connect a profiler to your SQL Server 2000 instance and see what is going on when you double click on Activity Monitor in Management Studio. Since you are getting a timeout error and you had a suspect database, one of the queries did not return result in time and thus the message.

If you are able to reproduce the problem in your lab environment, please post the results here.

Thank you,

Boris.

Managing SQL 2000 and 2005

I currently use Enterprise Manager 8.0 with several SQL 2000 servers. I'm ready to work with my first SQL Server v 2005. Can I use EM 8.0 along side the new Management Console until I'm through the learning curve? I understand you cannot register a 2005 server with EM 8.0, but I assume you can register a 2000 server from the new Management Console without any problem.

Use new Sql Server Management Console. It is very friendly than the EM.

Yes you can Management Console to register 2000 server. But You can't register 2005 server on EM.

Managing Scheduled Jobs from Management Studio Express

I'm working on a backup solution for my company. Right now we have three servers in three locations running SQL Server 2000. For testing purposes, I created a scheduled job on one of these servers. It worked fine but I'd like to tweak the job some, tinker with the timing and save locations. I'm using Management Studio Express on my laptop to remotely work with these databases but I can't seem to find a decent way to work with existing jobs. Am I missing something or does SSMSE lack the "manage jobs" functionality?

SSMSE only exposes functionality that is available in SQL Express. Since Express doesn't include Agent, SSMSE doesn't include the ability to manage Agent jobs.

The SQL 2005 Feature Pack includes some DTS 2000 add-in that may meet your needs. I've not worked with them, but they may work for you.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

Managing multiple SQL Server databases

Hi,

I have to manage many SQL Server databases on several servers. How can I manage the jobs, backups and the space on the disc without going to each and every server and database and job? Is there any script to run this? It will be very helpful if you can provide me the sample script or point me to any web site where I can get the info/script for this. Thanks in advance...

My preferable way to do this is to create the job on the server, script it out, parameterize it and deploy it with changed parameters on the other servers, this is also very helpful as you can tweak the paths to the log files, as they can differ from server to server as well as in the drive location as in the path.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

When running scripts to manage the system you are going to have to run them on the server they are needed on... Even if they are stored on the one server. I would start by looking at Linked Servers so that you can run your queries and scripts on the remote machines from the one server. In regards to monitoring the servers you could also look at MOM (Microsoft Operations Manager) and have the agents installed on each of your SQL Servers. This way the MOM System can monitor the OS Level parameters as well as some of the SQL Systems (Using the SQL Management Packs). At the same time you can also create custom scripts and tasks that MOM Can run that can be targeted to use the different servers.

With SSIS You should be able to also confugre your SQL Jobs to run from the one server and execute the different commands on the different servers.

|||

For Multiserver administration u need to create

Master server

Target Server

Enlist Traget server ................

See http://msdn2.microsoft.com/en-us/library/ms191305.aspx

I hope this helps

|||Thank you Jens, Glenn and admindba for your valuable inputs...

Managing DB updates to client DB servers

I'm looking for ideas on how to write SQL scripts for updates that are
pushed out to clients for product updates. Obviously, We could just
keep track of the changes on a pad or write a database that requires
us to input those changes and eventually hand write the update
scripts. I was wondering if anybody has any solutions that may help
automate this process.

Is there a way to write an application that will compare a current
(updated) database structure against the last realease that will give
us the fields that need to be changed?

As far as creating the scripts for the initial install, thats easy. We
can do that right from the SQL Enterprise Manager.

Call me lazy! Any ideas?

ThanksDuncan (duncan.loxton@.gmail.com) writes:
> I'm looking for ideas on how to write SQL scripts for updates that are
> pushed out to clients for product updates. Obviously, We could just
> keep track of the changes on a pad or write a database that requires
> us to input those changes and eventually hand write the update
> scripts. I was wondering if anybody has any solutions that may help
> automate this process.
> Is there a way to write an application that will compare a current
> (updated) database structure against the last realease that will give
> us the fields that need to be changed?
> As far as creating the scripts for the initial install, thats easy. We
> can do that right from the SQL Enterprise Manager.

There a couple of products on the market. SQLCompare from Red Gate does
indeed compare two databases. DBGhost likes to tout itself as being
good for this. I have not use any of them.

Whatever method, you should keep all your code under version control,
and all your update scripts should have their foundation in the
version-control system. Basically a shipment is all changes between
the label for the previous shipment and this one. With some files added,
like triggers or indexes for changed tables.

In fact, once you have a good version control system up and running,
composing your scripts manually is not daunting task - but admittedly
it becomes boring after a while. The flip side is that you learn to
understand your process.

In fact, I started in our shop with something like this many years
ago. This has now evolved to a versatile toolset that we use. It is
available as freeware for anyone who want to try, see
http://www.abaris.se/abaperls/index.html.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Managing backup files using SQL Agent

My client has about 3 servers with several databases on each. These databases
are backed up to disk using maintenance plans. This client wants to copy SQL
backup files on the disks of these servers to an additional server with a
tape drive to do consolidated backup to tape.
Is the best way to copy backup files already on disk to a network share to
use a DOS copy command through SQL Agent?
If so, is it best to run SQL Agent using a domain account with substantial
rights to ensure that SQL agent has appropriate file permissions both locally
and on network paths? When SQL agent runs under the local system account,
file copy operations fail with "Access denied" messages.
Does anyone have suggestions on how to do this task?
Larry Menzin
American Techsystems Corp.
I run my SQL Agent using a Domain User account that is local administrator
on the server.
In your case, just add a step to the jobs that the maintenance plans created
that calls XP_Cmdshell to do a DOS copy of the files after the backup is
complete.
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.
|||Hi
Do it as a OperatingSystemCommand (cmdExec) in SQL Agent.
Something like:
xcopy *.bak \\servername\sharename\*.* /E /Y
SQL Server has to use a domain account to run under, otherwise it does not
have a way to authenticate itself with the other server.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.

Managing backup files using SQL Agent

My client has about 3 servers with several databases on each. These database
s
are backed up to disk using maintenance plans. This client wants to copy SQL
backup files on the disks of these servers to an additional server with a
tape drive to do consolidated backup to tape.
Is the best way to copy backup files already on disk to a network share to
use a DOS copy command through SQL Agent?
If so, is it best to run SQL Agent using a domain account with substantial
rights to ensure that SQL agent has appropriate file permissions both locall
y
and on network paths? When SQL agent runs under the local system account,
file copy operations fail with "Access denied" messages.
Does anyone have suggestions on how to do this task?
Larry Menzin
American Techsystems Corp.I run my SQL Agent using a Domain User account that is local administrator
on the server.
In your case, just add a step to the jobs that the maintenance plans created
that calls XP_Cmdshell to do a DOS copy of the files after the backup is
complete.
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.|||Hi
Do it as a OperatingSystemCommand (cmdExec) in SQL Agent.
Something like:
xcopy *.bak \\servername\sharename\*.* /E /Y
SQL Server has to use a domain account to run under, otherwise it does not
have a way to authenticate itself with the other server.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.