Hello
I try to create a maintenance plan, but without success, having message
error : Error 8114: error converting datatype int to tinyint.
Please suggest workaround/solution if any
Thank youThis is normally "Error for converting data " you can search BOL for the
same,,,,
Did you get this error while creating maintenece plan for sure''
--
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"Elijah Bass" wrote:
> Hello
> I try to create a maintenance plan, but without success, having message
> error : Error 8114: error converting datatype int to tinyint.
> Please suggest workaround/solution if any
> Thank you
>
>
Showing posts with label message. Show all posts
Showing posts with label message. Show all posts
Wednesday, March 28, 2012
Friday, March 23, 2012
Maintenance Jobs Failed
Hi
Recently I have moved sql 2005 from one box to another with bigger hdd space and more memory. Since then I am getting the attached error message when I Execute all the job.Hey Common Gurus Help Me out... since 24 hours no reply
Thanks|||Resolved the issue.. thanks...|||Can you please post your resolution?|||Follow the link, has complete solution...
http://support.microsoft.com/kb/903205sql
Recently I have moved sql 2005 from one box to another with bigger hdd space and more memory. Since then I am getting the attached error message when I Execute all the job.Hey Common Gurus Help Me out... since 24 hours no reply
Thanks|||Resolved the issue.. thanks...|||Can you please post your resolution?|||Follow the link, has complete solution...
http://support.microsoft.com/kb/903205sql
Friday, March 9, 2012
mailto and picking a field for the subject line
I've put a hyperlink on a report to send a message to the support center
concerning service calls that are overdue for closure. How can I assign one
of the report fields as the subject of the mail message? For instance, if
the user clicks the 'Send Mail' link, the subject of the mail is "Call Number
"& "Field.svc00200.
Mail system is Exchange.
Many thanks
(BTW--I know 0 .net code, so keep that in mind, lol)Build the url string programmatically. I know you say you don't know
.Net but in RS a little knowledge goes a long way!
Where you would type the url, try
="mailto:" + Fields!email.Value + "&Subject=Call number" +
Fields!svc00200.Value
Chris
Jeff Metcalf wrote:
> I've put a hyperlink on a report to send a message to the support
> center concerning service calls that are overdue for closure. How
> can I assign one of the report fields as the subject of the mail
> message? For instance, if the user clicks the 'Send Mail' link, the
> subject of the mail is "Call Number "& "Field.svc00200.
> Mail system is Exchange.
> Many thanks
> (BTW--I know 0 .net code, so keep that in mind, lol)|||Nope, doesn't work. Gets Invalid URI: The hostname could not be parsed.
="Mailto:dispatch@.blah.com"+"&Subject=Call Number
"+Fields!svc00200.callnbr.Value
"Chris McGuigan" wrote:
> Build the url string programmatically. I know you say you don't know
> ..Net but in RS a little knowledge goes a long way!
> Where you would type the url, try
> ="mailto:" + Fields!email.Value + "&Subject=Call number" +
> Fields!svc00200.Value
> Chris
>
> Jeff Metcalf wrote:
> > I've put a hyperlink on a report to send a message to the support
> > center concerning service calls that are overdue for closure. How
> > can I assign one of the report fields as the subject of the mail
> > message? For instance, if the user clicks the 'Send Mail' link, the
> > subject of the mail is "Call Number "& "Field.svc00200.
> >
> > Mail system is Exchange.
> >
> > Many thanks
> > (BTW--I know 0 .net code, so keep that in mind, lol)
>|||I'm guessing it's a typo, but you have Fields!svc00200.callnbr.Value,
that doesn't look valid to me!
I have had this working, so it is possible. You probably haven't quite
got the expression right. Are there any characters in the returned
field that would effect the parsing, eg &
Chris
Jeff Metcalf wrote:
> Nope, doesn't work. Gets Invalid URI: The hostname could not be
> parsed.
> ="Mailto:dispatch@.blah.com"+"&Subject=Call Number
> "+Fields!svc00200.callnbr.Value
> "Chris McGuigan" wrote:
> > Build the url string programmatically. I know you say you don't know
> > ..Net but in RS a little knowledge goes a long way!
> > Where you would type the url, try
> > ="mailto:" + Fields!email.Value + "&Subject=Call number" +
> > Fields!svc00200.Value
> >
> > Chris
> >
> >
> > Jeff Metcalf wrote:
> >
> > > I've put a hyperlink on a report to send a message to the support
> > > center concerning service calls that are overdue for closure. How
> > > can I assign one of the report fields as the subject of the mail
> > > message? For instance, if the user clicks the 'Send Mail' link,
> > > the subject of the mail is "Call Number "& "Field.svc00200.
> > >
> > > Mail system is Exchange.
> > >
> > > Many thanks
> > > (BTW--I know 0 .net code, so keep that in mind, lol)
> >
> >
concerning service calls that are overdue for closure. How can I assign one
of the report fields as the subject of the mail message? For instance, if
the user clicks the 'Send Mail' link, the subject of the mail is "Call Number
"& "Field.svc00200.
Mail system is Exchange.
Many thanks
(BTW--I know 0 .net code, so keep that in mind, lol)Build the url string programmatically. I know you say you don't know
.Net but in RS a little knowledge goes a long way!
Where you would type the url, try
="mailto:" + Fields!email.Value + "&Subject=Call number" +
Fields!svc00200.Value
Chris
Jeff Metcalf wrote:
> I've put a hyperlink on a report to send a message to the support
> center concerning service calls that are overdue for closure. How
> can I assign one of the report fields as the subject of the mail
> message? For instance, if the user clicks the 'Send Mail' link, the
> subject of the mail is "Call Number "& "Field.svc00200.
> Mail system is Exchange.
> Many thanks
> (BTW--I know 0 .net code, so keep that in mind, lol)|||Nope, doesn't work. Gets Invalid URI: The hostname could not be parsed.
="Mailto:dispatch@.blah.com"+"&Subject=Call Number
"+Fields!svc00200.callnbr.Value
"Chris McGuigan" wrote:
> Build the url string programmatically. I know you say you don't know
> ..Net but in RS a little knowledge goes a long way!
> Where you would type the url, try
> ="mailto:" + Fields!email.Value + "&Subject=Call number" +
> Fields!svc00200.Value
> Chris
>
> Jeff Metcalf wrote:
> > I've put a hyperlink on a report to send a message to the support
> > center concerning service calls that are overdue for closure. How
> > can I assign one of the report fields as the subject of the mail
> > message? For instance, if the user clicks the 'Send Mail' link, the
> > subject of the mail is "Call Number "& "Field.svc00200.
> >
> > Mail system is Exchange.
> >
> > Many thanks
> > (BTW--I know 0 .net code, so keep that in mind, lol)
>|||I'm guessing it's a typo, but you have Fields!svc00200.callnbr.Value,
that doesn't look valid to me!
I have had this working, so it is possible. You probably haven't quite
got the expression right. Are there any characters in the returned
field that would effect the parsing, eg &
Chris
Jeff Metcalf wrote:
> Nope, doesn't work. Gets Invalid URI: The hostname could not be
> parsed.
> ="Mailto:dispatch@.blah.com"+"&Subject=Call Number
> "+Fields!svc00200.callnbr.Value
> "Chris McGuigan" wrote:
> > Build the url string programmatically. I know you say you don't know
> > ..Net but in RS a little knowledge goes a long way!
> > Where you would type the url, try
> > ="mailto:" + Fields!email.Value + "&Subject=Call number" +
> > Fields!svc00200.Value
> >
> > Chris
> >
> >
> > Jeff Metcalf wrote:
> >
> > > I've put a hyperlink on a report to send a message to the support
> > > center concerning service calls that are overdue for closure. How
> > > can I assign one of the report fields as the subject of the mail
> > > message? For instance, if the user clicks the 'Send Mail' link,
> > > the subject of the mail is "Call Number "& "Field.svc00200.
> > >
> > > Mail system is Exchange.
> > >
> > > Many thanks
> > > (BTW--I know 0 .net code, so keep that in mind, lol)
> >
> >
mail stored procedure- message -2147220975
i'm using a stored procedure that sends mail using the OA extended
procedures. it works fine on a number of servers.
Using Query analyzer, when executed the above message number shows up on the
messages tab. What's this? I've verified the stored procedure compiled and
the syntax check passes.
Using "xp_sendmail"
"Microsoft? SQL Server? provides a set of extended stored procedures that allow SQL Server to operate as a workgroup post office for a MAPI-enabled e-mail system."
Excuse me if this is not necessary, but have you tested the mail agent in SQL Server (SQL Mail) to determine if it is configured correctly and can send mail?
Another option is to cut and paste the sendmail in the stored procedure to find out if it for any syntac errors.
I use xp_sendmail in several stored procedures to alert me if a job fails and for other reasons. I haven't encountered this particular error message, but maybe my suggestions will help?
Jon
Message posted via http://www.sqlmonster.com
procedures. it works fine on a number of servers.
Using Query analyzer, when executed the above message number shows up on the
messages tab. What's this? I've verified the stored procedure compiled and
the syntax check passes.
Using "xp_sendmail"
"Microsoft? SQL Server? provides a set of extended stored procedures that allow SQL Server to operate as a workgroup post office for a MAPI-enabled e-mail system."
Excuse me if this is not necessary, but have you tested the mail agent in SQL Server (SQL Mail) to determine if it is configured correctly and can send mail?
Another option is to cut and paste the sendmail in the stored procedure to find out if it for any syntac errors.
I use xp_sendmail in several stored procedures to alert me if a job fails and for other reasons. I haven't encountered this particular error message, but maybe my suggestions will help?
Jon
Message posted via http://www.sqlmonster.com
mail stored procedure- message -2147220975
i'm using a stored procedure that sends mail using the OA extended
procedures. it works fine on a number of servers.
Using Query analyzer, when executed the above message number shows up on the
messages tab. What's this? I've verified the stored procedure compiled and
the syntax check passes.Using "xp_sendmail"
"Microsoft? SQL Server? provides a set of extended stored procedures that al
low SQL Server to operate as a workgroup post office for a MAPI-enabled e-ma
il system."
Excuse me if this is not necessary, but have you tested the mail agent in SQ
L Server (SQL Mail) to determine if it is configured correctly and can send
mail?
Another option is to cut and paste the sendmail in the stored procedure to f
ind out if it for any syntac errors.
I use xp_sendmail in several stored procedures to alert me if a job fails an
d for other reasons. I haven't encountered this particular error message, b
ut maybe my suggestions will help?
Jon
Message posted via http://www.droptable.com
procedures. it works fine on a number of servers.
Using Query analyzer, when executed the above message number shows up on the
messages tab. What's this? I've verified the stored procedure compiled and
the syntax check passes.Using "xp_sendmail"
"Microsoft? SQL Server? provides a set of extended stored procedures that al
low SQL Server to operate as a workgroup post office for a MAPI-enabled e-ma
il system."
Excuse me if this is not necessary, but have you tested the mail agent in SQ
L Server (SQL Mail) to determine if it is configured correctly and can send
mail?
Another option is to cut and paste the sendmail in the stored procedure to f
ind out if it for any syntac errors.
I use xp_sendmail in several stored procedures to alert me if a job fails an
d for other reasons. I haven't encountered this particular error message, b
ut maybe my suggestions will help?
Jon
Message posted via http://www.droptable.com
mail stored procedure- message -2147220975
i'm using a stored procedure that sends mail using the OA extended
procedures. it works fine on a number of servers.
Using Query analyzer, when executed the above message number shows up on the
messages tab. What's this? I've verified the stored procedure compiled and
the syntax check passes.Using "xp_sendmail"
"Microsoft? SQL Server? provides a set of extended stored procedures that allow SQL Server to operate as a workgroup post office for a MAPI-enabled e-mail system."
Excuse me if this is not necessary, but have you tested the mail agent in SQL Server (SQL Mail) to determine if it is configured correctly and can send mail?
Another option is to cut and paste the sendmail in the stored procedure to find out if it for any syntac errors.
I use xp_sendmail in several stored procedures to alert me if a job fails and for other reasons. I haven't encountered this particular error message, but maybe my suggestions will help?
Jon
--
Message posted via http://www.sqlmonster.com
procedures. it works fine on a number of servers.
Using Query analyzer, when executed the above message number shows up on the
messages tab. What's this? I've verified the stored procedure compiled and
the syntax check passes.Using "xp_sendmail"
"Microsoft? SQL Server? provides a set of extended stored procedures that allow SQL Server to operate as a workgroup post office for a MAPI-enabled e-mail system."
Excuse me if this is not necessary, but have you tested the mail agent in SQL Server (SQL Mail) to determine if it is configured correctly and can send mail?
Another option is to cut and paste the sendmail in the stored procedure to find out if it for any syntac errors.
I use xp_sendmail in several stored procedures to alert me if a job fails and for other reasons. I haven't encountered this particular error message, but maybe my suggestions will help?
Jon
--
Message posted via http://www.sqlmonster.com
Wednesday, March 7, 2012
mail notification of SQL shutdown
Hi,
Is it possible to config SQL mail send out a message when machine reboot or
SQL server shutdown?
Thanks,
Jack
Hi
You can't do it during the shutdown process as you may not be notified, if
it is a quick one, there is an OS shut down or crash.
For Startup, create a Stored Procedure. Then with sp_procoption, mark it for
startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds before
you send the mail. This gives the various MAPI components time to be loaded
by SQL Agent before you start to throw work their way.
If the SQL Server is really critical, it is best to get an external
monitoring tool to monitor the OS and SQL Server. Self monitoring on
software has its problems...It can't report on itself very well as it may
not be in a state to monitor itself.
Regards
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/
"Jack" <chongh.hc@.gmail.com> wrote in message
news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Is it possible to config SQL mail send out a message when machine reboot
> or SQL server shutdown?
> Thanks,
> Jack
>
|||Hi, Mike,
Thanks for your reply, I'll try your suggestion.
To help me better understand this question, I have to know "how SQL react if
OS send shutdown command to it?", if I can know any trigger force SQL
server/agent shutdown, can we apply a SP run first before SQL server/agent
proceed shutdown command that OS send to it.
Hope you can understand me , my English is not good.
Regards,
Chong
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uoHQEuaPFHA.3560@.TK2MSFTNGP14.phx.gbl...
> Hi
> You can't do it during the shutdown process as you may not be notified, if
> it is a quick one, there is an OS shut down or crash.
> For Startup, create a Stored Procedure. Then with sp_procoption, mark it
> for startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds
> before you send the mail. This gives the various MAPI components time to
> be loaded by SQL Agent before you start to throw work their way.
> If the SQL Server is really critical, it is best to get an external
> monitoring tool to monitor the OS and SQL Server. Self monitoring on
> software has its problems...It can't report on itself very well as it may
> not be in a state to monitor itself.
> Regards
> --
> 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/
> "Jack" <chongh.hc@.gmail.com> wrote in message
> news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
>
|||AFAIK, SQL behaves as any other service which is sent the STOP command - it
shuts down immediately. You would probably need to code your own WMI
application to trap service events, or use some 3rd-party monitoring
software.
One thing you might want to try is setting up a T-SQL job on another SQL
Server to try and connect (using osql.exe for example) and notify you if it
fails.
Adrian
"Jack" <chongh.hc@.gmail.com> wrote in message
news:%23biEK%23cPFHA.3336@.TK2MSFTNGP09.phx.gbl...
> Hi, Mike,
> Thanks for your reply, I'll try your suggestion.
> To help me better understand this question, I have to know "how SQL react
> if OS send shutdown command to it?", if I can know any trigger force SQL
> server/agent shutdown, can we apply a SP run first before SQL server/agent
> proceed shutdown command that OS send to it.
> Hope you can understand me , my English is not good.
> Regards,
> Chong
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uoHQEuaPFHA.3560@.TK2MSFTNGP14.phx.gbl...
>
Is it possible to config SQL mail send out a message when machine reboot or
SQL server shutdown?
Thanks,
Jack
Hi
You can't do it during the shutdown process as you may not be notified, if
it is a quick one, there is an OS shut down or crash.
For Startup, create a Stored Procedure. Then with sp_procoption, mark it for
startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds before
you send the mail. This gives the various MAPI components time to be loaded
by SQL Agent before you start to throw work their way.
If the SQL Server is really critical, it is best to get an external
monitoring tool to monitor the OS and SQL Server. Self monitoring on
software has its problems...It can't report on itself very well as it may
not be in a state to monitor itself.
Regards
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/
"Jack" <chongh.hc@.gmail.com> wrote in message
news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Is it possible to config SQL mail send out a message when machine reboot
> or SQL server shutdown?
> Thanks,
> Jack
>
|||Hi, Mike,
Thanks for your reply, I'll try your suggestion.
To help me better understand this question, I have to know "how SQL react if
OS send shutdown command to it?", if I can know any trigger force SQL
server/agent shutdown, can we apply a SP run first before SQL server/agent
proceed shutdown command that OS send to it.
Hope you can understand me , my English is not good.
Regards,
Chong
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uoHQEuaPFHA.3560@.TK2MSFTNGP14.phx.gbl...
> Hi
> You can't do it during the shutdown process as you may not be notified, if
> it is a quick one, there is an OS shut down or crash.
> For Startup, create a Stored Procedure. Then with sp_procoption, mark it
> for startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds
> before you send the mail. This gives the various MAPI components time to
> be loaded by SQL Agent before you start to throw work their way.
> If the SQL Server is really critical, it is best to get an external
> monitoring tool to monitor the OS and SQL Server. Self monitoring on
> software has its problems...It can't report on itself very well as it may
> not be in a state to monitor itself.
> Regards
> --
> 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/
> "Jack" <chongh.hc@.gmail.com> wrote in message
> news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
>
|||AFAIK, SQL behaves as any other service which is sent the STOP command - it
shuts down immediately. You would probably need to code your own WMI
application to trap service events, or use some 3rd-party monitoring
software.
One thing you might want to try is setting up a T-SQL job on another SQL
Server to try and connect (using osql.exe for example) and notify you if it
fails.
Adrian
"Jack" <chongh.hc@.gmail.com> wrote in message
news:%23biEK%23cPFHA.3336@.TK2MSFTNGP09.phx.gbl...
> Hi, Mike,
> Thanks for your reply, I'll try your suggestion.
> To help me better understand this question, I have to know "how SQL react
> if OS send shutdown command to it?", if I can know any trigger force SQL
> server/agent shutdown, can we apply a SP run first before SQL server/agent
> proceed shutdown command that OS send to it.
> Hope you can understand me , my English is not good.
> Regards,
> Chong
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uoHQEuaPFHA.3560@.TK2MSFTNGP14.phx.gbl...
>
mail notification of SQL shutdown
Hi,
Is it possible to config SQL mail send out a message when machine reboot or
SQL server shutdown?
Thanks,
JackHi
You can't do it during the shutdown process as you may not be notified, if
it is a quick one, there is an OS shut down or crash.
For Startup, create a Stored Procedure. Then with sp_procoption, mark it for
startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds before
you send the mail. This gives the various MAPI components time to be loaded
by SQL Agent before you start to throw work their way.
If the SQL Server is really critical, it is best to get an external
monitoring tool to monitor the OS and SQL Server. Self monitoring on
software has its problems...It can't report on itself very well as it may
not be in a state to monitor itself.
Regards
--
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/
"Jack" <chongh.hc@.gmail.com> wrote in message
news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Is it possible to config SQL mail send out a message when machine reboot
> or SQL server shutdown?
> Thanks,
> Jack
>|||Hi, Mike,
Thanks for your reply, I'll try your suggestion.
To help me better understand this question, I have to know "how SQL react if
OS send shutdown command to it?", if I can know any trigger force SQL
server/agent shutdown, can we apply a SP run first before SQL server/agent
proceed shutdown command that OS send to it.
Hope you can understand me , my English is not good.
Regards,
Chong
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uoHQEuaPFHA.3560@.TK2MSFTNGP14.phx.gbl...
> Hi
> You can't do it during the shutdown process as you may not be notified, if
> it is a quick one, there is an OS shut down or crash.
> For Startup, create a Stored Procedure. Then with sp_procoption, mark it
> for startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds
> before you send the mail. This gives the various MAPI components time to
> be loaded by SQL Agent before you start to throw work their way.
> If the SQL Server is really critical, it is best to get an external
> monitoring tool to monitor the OS and SQL Server. Self monitoring on
> software has its problems...It can't report on itself very well as it may
> not be in a state to monitor itself.
> Regards
> --
> 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/
> "Jack" <chongh.hc@.gmail.com> wrote in message
> news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
>|||AFAIK, SQL behaves as any other service which is sent the STOP command - it
shuts down immediately. You would probably need to code your own WMI
application to trap service events, or use some 3rd-party monitoring
software.
One thing you might want to try is setting up a T-SQL job on another SQL
Server to try and connect (using osql.exe for example) and notify you if it
fails.
Adrian
"Jack" <chongh.hc@.gmail.com> wrote in message
news:%23biEK%23cPFHA.3336@.TK2MSFTNGP09.phx.gbl...
> Hi, Mike,
> Thanks for your reply, I'll try your suggestion.
> To help me better understand this question, I have to know "how SQL react
> if OS send shutdown command to it?", if I can know any trigger force SQL
> server/agent shutdown, can we apply a SP run first before SQL server/agent
> proceed shutdown command that OS send to it.
> Hope you can understand me , my English is not good.
> Regards,
> Chong
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uoHQEuaPFHA.3560@.TK2MSFTNGP14.phx.gbl...
>
Is it possible to config SQL mail send out a message when machine reboot or
SQL server shutdown?
Thanks,
JackHi
You can't do it during the shutdown process as you may not be notified, if
it is a quick one, there is an OS shut down or crash.
For Startup, create a Stored Procedure. Then with sp_procoption, mark it for
startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds before
you send the mail. This gives the various MAPI components time to be loaded
by SQL Agent before you start to throw work their way.
If the SQL Server is really critical, it is best to get an external
monitoring tool to monitor the OS and SQL Server. Self monitoring on
software has its problems...It can't report on itself very well as it may
not be in a state to monitor itself.
Regards
--
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/
"Jack" <chongh.hc@.gmail.com> wrote in message
news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Is it possible to config SQL mail send out a message when machine reboot
> or SQL server shutdown?
> Thanks,
> Jack
>|||Hi, Mike,
Thanks for your reply, I'll try your suggestion.
To help me better understand this question, I have to know "how SQL react if
OS send shutdown command to it?", if I can know any trigger force SQL
server/agent shutdown, can we apply a SP run first before SQL server/agent
proceed shutdown command that OS send to it.
Hope you can understand me , my English is not good.
Regards,
Chong
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uoHQEuaPFHA.3560@.TK2MSFTNGP14.phx.gbl...
> Hi
> You can't do it during the shutdown process as you may not be notified, if
> it is a quick one, there is an OS shut down or crash.
> For Startup, create a Stored Procedure. Then with sp_procoption, mark it
> for startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds
> before you send the mail. This gives the various MAPI components time to
> be loaded by SQL Agent before you start to throw work their way.
> If the SQL Server is really critical, it is best to get an external
> monitoring tool to monitor the OS and SQL Server. Self monitoring on
> software has its problems...It can't report on itself very well as it may
> not be in a state to monitor itself.
> Regards
> --
> 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/
> "Jack" <chongh.hc@.gmail.com> wrote in message
> news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
>|||AFAIK, SQL behaves as any other service which is sent the STOP command - it
shuts down immediately. You would probably need to code your own WMI
application to trap service events, or use some 3rd-party monitoring
software.
One thing you might want to try is setting up a T-SQL job on another SQL
Server to try and connect (using osql.exe for example) and notify you if it
fails.
Adrian
"Jack" <chongh.hc@.gmail.com> wrote in message
news:%23biEK%23cPFHA.3336@.TK2MSFTNGP09.phx.gbl...
> Hi, Mike,
> Thanks for your reply, I'll try your suggestion.
> To help me better understand this question, I have to know "how SQL react
> if OS send shutdown command to it?", if I can know any trigger force SQL
> server/agent shutdown, can we apply a SP run first before SQL server/agent
> proceed shutdown command that OS send to it.
> Hope you can understand me , my English is not good.
> Regards,
> Chong
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uoHQEuaPFHA.3560@.TK2MSFTNGP14.phx.gbl...
>
mail notification of SQL shutdown
Hi,
Is it possible to config SQL mail send out a message when machine reboot or
SQL server shutdown?
Thanks,
JackHi
You can't do it during the shutdown process as you may not be notified, if
it is a quick one, there is an OS shut down or crash.
For Startup, create a Stored Procedure. Then with sp_procoption, mark it for
startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds before
you send the mail. This gives the various MAPI components time to be loaded
by SQL Agent before you start to throw work their way.
If the SQL Server is really critical, it is best to get an external
monitoring tool to monitor the OS and SQL Server. Self monitoring on
software has its problems...It can't report on itself very well as it may
not be in a state to monitor itself.
Regards
--
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/
"Jack" <chongh.hc@.gmail.com> wrote in message
news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Is it possible to config SQL mail send out a message when machine reboot
> or SQL server shutdown?
> Thanks,
> Jack
>|||Hi, Mike,
Thanks for your reply, I'll try your suggestion.
To help me better understand this question, I have to know "how SQL react if
OS send shutdown command to it?", if I can know any trigger force SQL
server/agent shutdown, can we apply a SP run first before SQL server/agent
proceed shutdown command that OS send to it.
Hope you can understand me , my English is not good.
Regards,
Chong
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uoHQEuaPFHA.3560@.TK2MSFTNGP14.phx.gbl...
> Hi
> You can't do it during the shutdown process as you may not be notified, if
> it is a quick one, there is an OS shut down or crash.
> For Startup, create a Stored Procedure. Then with sp_procoption, mark it
> for startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds
> before you send the mail. This gives the various MAPI components time to
> be loaded by SQL Agent before you start to throw work their way.
> If the SQL Server is really critical, it is best to get an external
> monitoring tool to monitor the OS and SQL Server. Self monitoring on
> software has its problems...It can't report on itself very well as it may
> not be in a state to monitor itself.
> Regards
> --
> 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/
> "Jack" <chongh.hc@.gmail.com> wrote in message
> news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
>> Hi,
>> Is it possible to config SQL mail send out a message when machine reboot
>> or SQL server shutdown?
>> Thanks,
>> Jack
>|||AFAIK, SQL behaves as any other service which is sent the STOP command - it
shuts down immediately. You would probably need to code your own WMI
application to trap service events, or use some 3rd-party monitoring
software.
One thing you might want to try is setting up a T-SQL job on another SQL
Server to try and connect (using osql.exe for example) and notify you if it
fails.
Adrian
"Jack" <chongh.hc@.gmail.com> wrote in message
news:%23biEK%23cPFHA.3336@.TK2MSFTNGP09.phx.gbl...
> Hi, Mike,
> Thanks for your reply, I'll try your suggestion.
> To help me better understand this question, I have to know "how SQL react
> if OS send shutdown command to it?", if I can know any trigger force SQL
> server/agent shutdown, can we apply a SP run first before SQL server/agent
> proceed shutdown command that OS send to it.
> Hope you can understand me , my English is not good.
> Regards,
> Chong
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uoHQEuaPFHA.3560@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> You can't do it during the shutdown process as you may not be notified,
>> if it is a quick one, there is an OS shut down or crash.
>> For Startup, create a Stored Procedure. Then with sp_procoption, mark it
>> for startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds
>> before you send the mail. This gives the various MAPI components time to
>> be loaded by SQL Agent before you start to throw work their way.
>> If the SQL Server is really critical, it is best to get an external
>> monitoring tool to monitor the OS and SQL Server. Self monitoring on
>> software has its problems...It can't report on itself very well as it
>> may not be in a state to monitor itself.
>> Regards
>> --
>> 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/
>> "Jack" <chongh.hc@.gmail.com> wrote in message
>> news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
>> Hi,
>> Is it possible to config SQL mail send out a message when machine reboot
>> or SQL server shutdown?
>> Thanks,
>> Jack
>>
>
Is it possible to config SQL mail send out a message when machine reboot or
SQL server shutdown?
Thanks,
JackHi
You can't do it during the shutdown process as you may not be notified, if
it is a quick one, there is an OS shut down or crash.
For Startup, create a Stored Procedure. Then with sp_procoption, mark it for
startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds before
you send the mail. This gives the various MAPI components time to be loaded
by SQL Agent before you start to throw work their way.
If the SQL Server is really critical, it is best to get an external
monitoring tool to monitor the OS and SQL Server. Self monitoring on
software has its problems...It can't report on itself very well as it may
not be in a state to monitor itself.
Regards
--
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/
"Jack" <chongh.hc@.gmail.com> wrote in message
news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Is it possible to config SQL mail send out a message when machine reboot
> or SQL server shutdown?
> Thanks,
> Jack
>|||Hi, Mike,
Thanks for your reply, I'll try your suggestion.
To help me better understand this question, I have to know "how SQL react if
OS send shutdown command to it?", if I can know any trigger force SQL
server/agent shutdown, can we apply a SP run first before SQL server/agent
proceed shutdown command that OS send to it.
Hope you can understand me , my English is not good.
Regards,
Chong
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uoHQEuaPFHA.3560@.TK2MSFTNGP14.phx.gbl...
> Hi
> You can't do it during the shutdown process as you may not be notified, if
> it is a quick one, there is an OS shut down or crash.
> For Startup, create a Stored Procedure. Then with sp_procoption, mark it
> for startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds
> before you send the mail. This gives the various MAPI components time to
> be loaded by SQL Agent before you start to throw work their way.
> If the SQL Server is really critical, it is best to get an external
> monitoring tool to monitor the OS and SQL Server. Self monitoring on
> software has its problems...It can't report on itself very well as it may
> not be in a state to monitor itself.
> Regards
> --
> 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/
> "Jack" <chongh.hc@.gmail.com> wrote in message
> news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
>> Hi,
>> Is it possible to config SQL mail send out a message when machine reboot
>> or SQL server shutdown?
>> Thanks,
>> Jack
>|||AFAIK, SQL behaves as any other service which is sent the STOP command - it
shuts down immediately. You would probably need to code your own WMI
application to trap service events, or use some 3rd-party monitoring
software.
One thing you might want to try is setting up a T-SQL job on another SQL
Server to try and connect (using osql.exe for example) and notify you if it
fails.
Adrian
"Jack" <chongh.hc@.gmail.com> wrote in message
news:%23biEK%23cPFHA.3336@.TK2MSFTNGP09.phx.gbl...
> Hi, Mike,
> Thanks for your reply, I'll try your suggestion.
> To help me better understand this question, I have to know "how SQL react
> if OS send shutdown command to it?", if I can know any trigger force SQL
> server/agent shutdown, can we apply a SP run first before SQL server/agent
> proceed shutdown command that OS send to it.
> Hope you can understand me , my English is not good.
> Regards,
> Chong
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uoHQEuaPFHA.3560@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> You can't do it during the shutdown process as you may not be notified,
>> if it is a quick one, there is an OS shut down or crash.
>> For Startup, create a Stored Procedure. Then with sp_procoption, mark it
>> for startup. But, in you SP, add a delay with "DELAY" for 20-30 seconds
>> before you send the mail. This gives the various MAPI components time to
>> be loaded by SQL Agent before you start to throw work their way.
>> If the SQL Server is really critical, it is best to get an external
>> monitoring tool to monitor the OS and SQL Server. Self monitoring on
>> software has its problems...It can't report on itself very well as it
>> may not be in a state to monitor itself.
>> Regards
>> --
>> 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/
>> "Jack" <chongh.hc@.gmail.com> wrote in message
>> news:u3WxXCaPFHA.2568@.TK2MSFTNGP14.phx.gbl...
>> Hi,
>> Is it possible to config SQL mail send out a message when machine reboot
>> or SQL server shutdown?
>> Thanks,
>> Jack
>>
>
mail error
Iam unable to send out emails since we changed the system
acount name...
when I test the email name I get the following message
'Errorr 22022:SQLServerAgent Error: The SQLServerAgent
session is not running; check the mail profile and or
SQLServerAgent service startup acount in SQLServerAgent
properties dialogue box'
the mail configeration test works ok and restarted
SQLServerAgent.. any ideasgrumy,
When you say you changed the "system account name", what exactly are you
referring to? The MSSQLServer service account name?
I am also not clear on whether your SQLServerAgent service is running or
not. The error message states that it is not running, but you are saying
that SQLServerAgent was restarted successfully. Could you clarify your
questions?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"grumy" <anonymous@.discussions.microsoft.com> wrote in message
news:2f5e01c4289b$d6d1eba0$a301280a@.phx.gbl...
> Iam unable to send out emails since we changed the system
> acount name...
> when I test the email name I get the following message
> 'Errorr 22022:SQLServerAgent Error: The SQLServerAgent
> session is not running; check the mail profile and or
> SQLServerAgent service startup acount in SQLServerAgent
> properties dialogue box'
> the mail configeration test works ok and restarted
> SQLServerAgent.. any ideas
acount name...
when I test the email name I get the following message
'Errorr 22022:SQLServerAgent Error: The SQLServerAgent
session is not running; check the mail profile and or
SQLServerAgent service startup acount in SQLServerAgent
properties dialogue box'
the mail configeration test works ok and restarted
SQLServerAgent.. any ideasgrumy,
When you say you changed the "system account name", what exactly are you
referring to? The MSSQLServer service account name?
I am also not clear on whether your SQLServerAgent service is running or
not. The error message states that it is not running, but you are saying
that SQLServerAgent was restarted successfully. Could you clarify your
questions?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"grumy" <anonymous@.discussions.microsoft.com> wrote in message
news:2f5e01c4289b$d6d1eba0$a301280a@.phx.gbl...
> Iam unable to send out emails since we changed the system
> acount name...
> when I test the email name I get the following message
> 'Errorr 22022:SQLServerAgent Error: The SQLServerAgent
> session is not running; check the mail profile and or
> SQLServerAgent service startup acount in SQLServerAgent
> properties dialogue box'
> the mail configeration test works ok and restarted
> SQLServerAgent.. any ideas
mail error
Iam unable to send out emails since we changed the system
acount name...
when I test the email name I get the following message
'Errorr 22022:SQLServerAgent Error: The SQLServerAgent
session is not running; check the mail profile and or
SQLServerAgent service startup acount in SQLServerAgent
properties dialogue box'
the mail configeration test works ok and restarted
SQLServerAgent.. any ideasgrumy,
When you say you changed the "system account name", what exactly are you
referring to? The MSSQLServer service account name?
I am also not clear on whether your SQLServerAgent service is running or
not. The error message states that it is not running, but you are saying
that SQLServerAgent was restarted successfully. Could you clarify your
questions?
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"grumy" <anonymous@.discussions.microsoft.com> wrote in message
news:2f5e01c4289b$d6d1eba0$a301280a@.phx.gbl...
> Iam unable to send out emails since we changed the system
> acount name...
> when I test the email name I get the following message
> 'Errorr 22022:SQLServerAgent Error: The SQLServerAgent
> session is not running; check the mail profile and or
> SQLServerAgent service startup acount in SQLServerAgent
> properties dialogue box'
> the mail configeration test works ok and restarted
> SQLServerAgent.. any ideas
acount name...
when I test the email name I get the following message
'Errorr 22022:SQLServerAgent Error: The SQLServerAgent
session is not running; check the mail profile and or
SQLServerAgent service startup acount in SQLServerAgent
properties dialogue box'
the mail configeration test works ok and restarted
SQLServerAgent.. any ideasgrumy,
When you say you changed the "system account name", what exactly are you
referring to? The MSSQLServer service account name?
I am also not clear on whether your SQLServerAgent service is running or
not. The error message states that it is not running, but you are saying
that SQLServerAgent was restarted successfully. Could you clarify your
questions?
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"grumy" <anonymous@.discussions.microsoft.com> wrote in message
news:2f5e01c4289b$d6d1eba0$a301280a@.phx.gbl...
> Iam unable to send out emails since we changed the system
> acount name...
> when I test the email name I get the following message
> 'Errorr 22022:SQLServerAgent Error: The SQLServerAgent
> session is not running; check the mail profile and or
> SQLServerAgent service startup acount in SQLServerAgent
> properties dialogue box'
> the mail configeration test works ok and restarted
> SQLServerAgent.. any ideas
Saturday, February 25, 2012
Macro
Has anyone ever tried to run a stored procedure through a macro before?? And If so do you get a message that says that the stored procedure exectuted successfully but a macro Halt macro message that says "Action Failed"?? Now the stored procedure executes just fine its just that the macro itself is having some trouble. Can anyone help me?? pleaseFrom where you're trying to execute, I've never come across in SQL server.|||Probably way off here but is it possible a return value that is expected but not given?|||This is the stored procedure I am using
CREATE PROCEDURE [InsertTerms]
AS
INSERT INTO [GamingCommissiondb].[dbo].[TERMINATION] ( [TM #],
[FirstName],
[LastName],
[SocialSecurityNumber],
[DateHired],
[Status],
[Title],
[DepartmentName])
SELECT a.TM#, a.FirstName, a.LASTNAME, a.SSN#, a.HIREDATE, a.STATUS, a.JOBTITLE, a.DEPT#
FROM EmployeeGamingLicense AS a
WHERE a.STATUS = 'TERMINATED'
IF @.@.Error <> '0'
RETURN
GO
this is the macro that executes it|||Why not just use a pass thu?|||IF @.@.Error <> '0'
RETURN
GO
In your case, 0 is always returned. Does the data get inserted? Does the macro always indicate "Action Failed"?|||Yes the data does get inserted, and yes the macro is always indicates failed action|||Access xp has no problems with this, access 2000 apparently has a problem|||Do the sprocs get listed in your macro drop down list?
I betcha it's a connectivity thing...
CREATE PROCEDURE [InsertTerms]
AS
INSERT INTO [GamingCommissiondb].[dbo].[TERMINATION] ( [TM #],
[FirstName],
[LastName],
[SocialSecurityNumber],
[DateHired],
[Status],
[Title],
[DepartmentName])
SELECT a.TM#, a.FirstName, a.LASTNAME, a.SSN#, a.HIREDATE, a.STATUS, a.JOBTITLE, a.DEPT#
FROM EmployeeGamingLicense AS a
WHERE a.STATUS = 'TERMINATED'
IF @.@.Error <> '0'
RETURN
GO
this is the macro that executes it|||Why not just use a pass thu?|||IF @.@.Error <> '0'
RETURN
GO
In your case, 0 is always returned. Does the data get inserted? Does the macro always indicate "Action Failed"?|||Yes the data does get inserted, and yes the macro is always indicates failed action|||Access xp has no problems with this, access 2000 apparently has a problem|||Do the sprocs get listed in your macro drop down list?
I betcha it's a connectivity thing...
MAC used as search index for Encrypted data: how secure?
I have read recommendations about searching encrypted data. Typically, they involve creating a MAC (message authentication code) table. One of the elements of that table is a HASH of the encrypted data (plus a Mac key) that is used as an index for searching. Is that HASH as secure as the encrypted data itself, or is this approach less secure? If it is less secure, then may I assume that approach is the only feasible way to search data encrypted by nondeterministic algorithms?
TIA,
Barkingdog
Is the hash as secure as the encrypted data? This is a difficult question, because the answer depends on what you are trying to secure against, and what algorithms you are using, and what vulnerabilities they develop over time. One thing that a hash would disclose, and that encryption would normally not disclose, is data identity. That is, you can encrypt the same piece of data and you won't be able to determine from the resulting blobs whether they are corresponding to identical data, but if you hash the data, the result will be identical.
Strictly speaking, the only way to search encrypted data (and I mean non-deterministic, although I should not need to specify this because encryption is always intended to be a non-deterministic operation) is to decrypt all data and search through the decrypted text. Using hashes is a workaround that allows you to search hashes instead of the encrypted data, to answer an equality search. You can probably devise other alternative search schemes, depending on what searches you want to allow and how much information you are willing to give away.
Thanks
Laurentiu
>>>Using hashes is a workaround
Yes, I agree with that. I'm just concerned that the creation of hashes (out of practical necessity) results in a workable solution because the hash codes are easier to "crack" than the encrypted data itself. Maybe "cracking" the hash can lead to cracking the encrypted data?
Barkingdog.
|||Strictly speaking, yes it is possible to user a rainbow attack against a pure hash on the data we are trying to protect, especially if the domain of the plaintext is finite and well defined (i.e. SSN, CCN, etc.). For example, I can easily create an offline rainbow table with all possible hashes (SHA1, MD5, etc.) for every possible SSN, once I find your hashed value I just need to find the corresponding value on the rainbow table.
This is the reason why I was suggesting using an HMAC, that way the domain of the plaintext is different and creating a dictionary is far more expensive that the example above. You are still giving away some information to the potential attacker, but the difference is that now there is a random bag of bits of arbitrary length (the HMAC key) combined with the data we want to protect, that way the hash input does not belong to the same domain as the original plaintext.
Assuming that the key is truly random, large enough and well protected, the previous attack is rendered useless, and to the best of our knowledge the attacker will need to brute force all possibilities (i.e. hash( ‘111-111-111’ + 0x00…001 ), hash( ‘111-111-111’ + 0x00…002 ) … hash( ‘999-999-999’ + 0xFF…FFF ), as you can see this is far more expensive, and the larger the key, the better.
Is this better or worse than trying to brute force a symmetric key? That is a really difficult question as Laurentiu mentioned. Hashes are less expensive (computational wise) than decryptions, but there are too many factors to consider (domain of your plaintext, domain of the key, reusing keys, new attack methods being discovered, etc.).
The best option if you want to create an index over the encrypted data may be to create a completely new identifier for it, i.e. a customer ID that is completely unrelated to the data being protected, but we understand this option is not always possible due to business reasons.
I would recommend defining what assets you are trying to protect and against what kind of threats. From there you need to evaluate what options you have to protect against such threats, as well as what mechanisms (preferably use defense in depth) you have to prevent, detect and halt a possible attack, as well as what are the steps to follow after the situation is back under control.
Thanks a lot,
-Raul Garcia
SDE/T
SQL Server Engine
Monday, February 20, 2012
LSN Error: 9003
Recently I encountered an error related to LSN. The error message was like
this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
scan in database 'model' is invalid.. I have to overwrite the model database
with a copy from another server before the server can start up.
Does anyone know what is the cause of this error and is there a way to
prevent this from happening? We are using SQL Server 2000 Standard with SP4
on Windows 2000 Standard Edition with SP4.
Thanks,
MP Wong
"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> Recently I encountered an error related to LSN. The error message was like
> this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
> scan in database 'model' is invalid.. I have to overwrite the model
> database
> with a copy from another server before the server can start up.
>
That doesn't sound good.
Sounds like a corrupt transaction log on the model database. And since the
model database should rarely change, it's even less likely you should see
this.
Does this continue to occur?
> Does anyone know what is the cause of this error and is there a way to
> prevent this from happening? We are using SQL Server 2000 Standard with
> SP4
> on Windows 2000 Standard Edition with SP4.
> Thanks,
> MP Wong
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Hi Greg,
This is the first time I have seen this error. We have about 30 servers and
this one is probably the oldest. Does it signal that the hardware is starting
to fail? We have checked the RAID log records and everything seems normal.
This error could have been caused by a server restart one day earlier.
Best Regards,
MP Wong
"Greg D. Moore (Strider)" wrote:
>
> "mpWong" <mpWong@.discussions.microsoft.com> wrote in message
> news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> That doesn't sound good.
> Sounds like a corrupt transaction log on the model database. And since the
> model database should rarely change, it's even less likely you should see
> this.
> Does this continue to occur?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>
|||"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:501B9B7B-05BD-43B7-93C3-7CF75355D6A9@.microsoft.com...
> Hi Greg,
> This is the first time I have seen this error. We have about 30 servers
> and
> this one is probably the oldest. Does it signal that the hardware is
> starting
> to fail? We have checked the RAID log records and everything seems normal.
> This error could have been caused by a server restart one day earlier.
If it happened the one time... and you can correlate it with the server
restart, I'd PROBABLY ignore it.
But if it's happening more than once, then yes, definitely look at your
hardware.
[vbcol=seagreen]
>
> Best Regards,
> MP Wong
> "Greg D. Moore (Strider)" wrote:
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
scan in database 'model' is invalid.. I have to overwrite the model database
with a copy from another server before the server can start up.
Does anyone know what is the cause of this error and is there a way to
prevent this from happening? We are using SQL Server 2000 Standard with SP4
on Windows 2000 Standard Edition with SP4.
Thanks,
MP Wong
"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> Recently I encountered an error related to LSN. The error message was like
> this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
> scan in database 'model' is invalid.. I have to overwrite the model
> database
> with a copy from another server before the server can start up.
>
That doesn't sound good.
Sounds like a corrupt transaction log on the model database. And since the
model database should rarely change, it's even less likely you should see
this.
Does this continue to occur?
> Does anyone know what is the cause of this error and is there a way to
> prevent this from happening? We are using SQL Server 2000 Standard with
> SP4
> on Windows 2000 Standard Edition with SP4.
> Thanks,
> MP Wong
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Hi Greg,
This is the first time I have seen this error. We have about 30 servers and
this one is probably the oldest. Does it signal that the hardware is starting
to fail? We have checked the RAID log records and everything seems normal.
This error could have been caused by a server restart one day earlier.
Best Regards,
MP Wong
"Greg D. Moore (Strider)" wrote:
>
> "mpWong" <mpWong@.discussions.microsoft.com> wrote in message
> news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> That doesn't sound good.
> Sounds like a corrupt transaction log on the model database. And since the
> model database should rarely change, it's even less likely you should see
> this.
> Does this continue to occur?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>
|||"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:501B9B7B-05BD-43B7-93C3-7CF75355D6A9@.microsoft.com...
> Hi Greg,
> This is the first time I have seen this error. We have about 30 servers
> and
> this one is probably the oldest. Does it signal that the hardware is
> starting
> to fail? We have checked the RAID log records and everything seems normal.
> This error could have been caused by a server restart one day earlier.
If it happened the one time... and you can correlate it with the server
restart, I'd PROBABLY ignore it.
But if it's happening more than once, then yes, definitely look at your
hardware.
[vbcol=seagreen]
>
> Best Regards,
> MP Wong
> "Greg D. Moore (Strider)" wrote:
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
LSN Error: 9003
Recently I encountered an error related to LSN. The error message was like
this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
scan in database 'model' is invalid.. I have to overwrite the model database
with a copy from another server before the server can start up.
Does anyone know what is the cause of this error and is there a way to
prevent this from happening? We are using SQL Server 2000 Standard with SP4
on Windows 2000 Standard Edition with SP4.
Thanks,
MP Wong"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> Recently I encountered an error related to LSN. The error message was like
> this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
> scan in database 'model' is invalid.. I have to overwrite the model
> database
> with a copy from another server before the server can start up.
>
That doesn't sound good.
Sounds like a corrupt transaction log on the model database. And since the
model database should rarely change, it's even less likely you should see
this.
Does this continue to occur?
> Does anyone know what is the cause of this error and is there a way to
> prevent this from happening? We are using SQL Server 2000 Standard with
> SP4
> on Windows 2000 Standard Edition with SP4.
> Thanks,
> MP Wong
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi Greg,
This is the first time I have seen this error. We have about 30 servers and
this one is probably the oldest. Does it signal that the hardware is starting
to fail? We have checked the RAID log records and everything seems normal.
This error could have been caused by a server restart one day earlier.
Best Regards,
MP Wong
"Greg D. Moore (Strider)" wrote:
>
> "mpWong" <mpWong@.discussions.microsoft.com> wrote in message
> news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> > Recently I encountered an error related to LSN. The error message was like
> > this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
> > scan in database 'model' is invalid.. I have to overwrite the model
> > database
> > with a copy from another server before the server can start up.
> >
> That doesn't sound good.
> Sounds like a corrupt transaction log on the model database. And since the
> model database should rarely change, it's even less likely you should see
> this.
> Does this continue to occur?
>
> > Does anyone know what is the cause of this error and is there a way to
> > prevent this from happening? We are using SQL Server 2000 Standard with
> > SP4
> > on Windows 2000 Standard Edition with SP4.
> >
> > Thanks,
> > MP Wong
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>|||"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:501B9B7B-05BD-43B7-93C3-7CF75355D6A9@.microsoft.com...
> Hi Greg,
> This is the first time I have seen this error. We have about 30 servers
> and
> this one is probably the oldest. Does it signal that the hardware is
> starting
> to fail? We have checked the RAID log records and everything seems normal.
> This error could have been caused by a server restart one day earlier.
If it happened the one time... and you can correlate it with the server
restart, I'd PROBABLY ignore it.
But if it's happening more than once, then yes, definitely look at your
hardware.
>
> Best Regards,
> MP Wong
> "Greg D. Moore (Strider)" wrote:
>>
>> "mpWong" <mpWong@.discussions.microsoft.com> wrote in message
>> news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
>> > Recently I encountered an error related to LSN. The error message was
>> > like
>> > this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to
>> > log
>> > scan in database 'model' is invalid.. I have to overwrite the model
>> > database
>> > with a copy from another server before the server can start up.
>> >
>> That doesn't sound good.
>> Sounds like a corrupt transaction log on the model database. And since
>> the
>> model database should rarely change, it's even less likely you should see
>> this.
>> Does this continue to occur?
>>
>> > Does anyone know what is the cause of this error and is there a way to
>> > prevent this from happening? We are using SQL Server 2000 Standard with
>> > SP4
>> > on Windows 2000 Standard Edition with SP4.
>> >
>> > Thanks,
>> > MP Wong
>> --
>> Greg Moore
>> SQL Server DBA Consulting Remote and Onsite available!
>> Email: sql (at) greenms.com
>> http://www.greenms.com/sqlserver.html
>>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
scan in database 'model' is invalid.. I have to overwrite the model database
with a copy from another server before the server can start up.
Does anyone know what is the cause of this error and is there a way to
prevent this from happening? We are using SQL Server 2000 Standard with SP4
on Windows 2000 Standard Edition with SP4.
Thanks,
MP Wong"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> Recently I encountered an error related to LSN. The error message was like
> this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
> scan in database 'model' is invalid.. I have to overwrite the model
> database
> with a copy from another server before the server can start up.
>
That doesn't sound good.
Sounds like a corrupt transaction log on the model database. And since the
model database should rarely change, it's even less likely you should see
this.
Does this continue to occur?
> Does anyone know what is the cause of this error and is there a way to
> prevent this from happening? We are using SQL Server 2000 Standard with
> SP4
> on Windows 2000 Standard Edition with SP4.
> Thanks,
> MP Wong
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi Greg,
This is the first time I have seen this error. We have about 30 servers and
this one is probably the oldest. Does it signal that the hardware is starting
to fail? We have checked the RAID log records and everything seems normal.
This error could have been caused by a server restart one day earlier.
Best Regards,
MP Wong
"Greg D. Moore (Strider)" wrote:
>
> "mpWong" <mpWong@.discussions.microsoft.com> wrote in message
> news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> > Recently I encountered an error related to LSN. The error message was like
> > this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
> > scan in database 'model' is invalid.. I have to overwrite the model
> > database
> > with a copy from another server before the server can start up.
> >
> That doesn't sound good.
> Sounds like a corrupt transaction log on the model database. And since the
> model database should rarely change, it's even less likely you should see
> this.
> Does this continue to occur?
>
> > Does anyone know what is the cause of this error and is there a way to
> > prevent this from happening? We are using SQL Server 2000 Standard with
> > SP4
> > on Windows 2000 Standard Edition with SP4.
> >
> > Thanks,
> > MP Wong
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>|||"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:501B9B7B-05BD-43B7-93C3-7CF75355D6A9@.microsoft.com...
> Hi Greg,
> This is the first time I have seen this error. We have about 30 servers
> and
> this one is probably the oldest. Does it signal that the hardware is
> starting
> to fail? We have checked the RAID log records and everything seems normal.
> This error could have been caused by a server restart one day earlier.
If it happened the one time... and you can correlate it with the server
restart, I'd PROBABLY ignore it.
But if it's happening more than once, then yes, definitely look at your
hardware.
>
> Best Regards,
> MP Wong
> "Greg D. Moore (Strider)" wrote:
>>
>> "mpWong" <mpWong@.discussions.microsoft.com> wrote in message
>> news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
>> > Recently I encountered an error related to LSN. The error message was
>> > like
>> > this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to
>> > log
>> > scan in database 'model' is invalid.. I have to overwrite the model
>> > database
>> > with a copy from another server before the server can start up.
>> >
>> That doesn't sound good.
>> Sounds like a corrupt transaction log on the model database. And since
>> the
>> model database should rarely change, it's even less likely you should see
>> this.
>> Does this continue to occur?
>>
>> > Does anyone know what is the cause of this error and is there a way to
>> > prevent this from happening? We are using SQL Server 2000 Standard with
>> > SP4
>> > on Windows 2000 Standard Edition with SP4.
>> >
>> > Thanks,
>> > MP Wong
>> --
>> Greg Moore
>> SQL Server DBA Consulting Remote and Onsite available!
>> Email: sql (at) greenms.com
>> http://www.greenms.com/sqlserver.html
>>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
LSN Error: 9003
Recently I encountered an error related to LSN. The error message was like
this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
scan in database 'model' is invalid.. I have to overwrite the model database
with a copy from another server before the server can start up.
Does anyone know what is the cause of this error and is there a way to
prevent this from happening? We are using SQL Server 2000 Standard with SP4
on Windows 2000 Standard Edition with SP4.
Thanks,
MP Wong"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> Recently I encountered an error related to LSN. The error message was like
> this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
> scan in database 'model' is invalid.. I have to overwrite the model
> database
> with a copy from another server before the server can start up.
>
That doesn't sound good.
Sounds like a corrupt transaction log on the model database. And since the
model database should rarely change, it's even less likely you should see
this.
Does this continue to occur?
> Does anyone know what is the cause of this error and is there a way to
> prevent this from happening? We are using SQL Server 2000 Standard with
> SP4
> on Windows 2000 Standard Edition with SP4.
> Thanks,
> MP Wong
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi Greg,
This is the first time I have seen this error. We have about 30 servers and
this one is probably the oldest. Does it signal that the hardware is startin
g
to fail? We have checked the RAID log records and everything seems normal.
This error could have been caused by a server restart one day earlier.
Best Regards,
MP Wong
"Greg D. Moore (Strider)" wrote:
>
> "mpWong" <mpWong@.discussions.microsoft.com> wrote in message
> news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> That doesn't sound good.
> Sounds like a corrupt transaction log on the model database. And since th
e
> model database should rarely change, it's even less likely you should see
> this.
> Does this continue to occur?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com [url]http://www.greenms.com/sqlserver.html[/ur
l]
>
>|||"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:501B9B7B-05BD-43B7-93C3-7CF75355D6A9@.microsoft.com...
> Hi Greg,
> This is the first time I have seen this error. We have about 30 servers
> and
> this one is probably the oldest. Does it signal that the hardware is
> starting
> to fail? We have checked the RAID log records and everything seems normal.
> This error could have been caused by a server restart one day earlier.
If it happened the one time... and you can correlate it with the server
restart, I'd PROBABLY ignore it.
But if it's happening more than once, then yes, definitely look at your
hardware.
[vbcol=seagreen]
>
> Best Regards,
> MP Wong
> "Greg D. Moore (Strider)" wrote:
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
scan in database 'model' is invalid.. I have to overwrite the model database
with a copy from another server before the server can start up.
Does anyone know what is the cause of this error and is there a way to
prevent this from happening? We are using SQL Server 2000 Standard with SP4
on Windows 2000 Standard Edition with SP4.
Thanks,
MP Wong"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> Recently I encountered an error related to LSN. The error message was like
> this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
> scan in database 'model' is invalid.. I have to overwrite the model
> database
> with a copy from another server before the server can start up.
>
That doesn't sound good.
Sounds like a corrupt transaction log on the model database. And since the
model database should rarely change, it's even less likely you should see
this.
Does this continue to occur?
> Does anyone know what is the cause of this error and is there a way to
> prevent this from happening? We are using SQL Server 2000 Standard with
> SP4
> on Windows 2000 Standard Edition with SP4.
> Thanks,
> MP Wong
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi Greg,
This is the first time I have seen this error. We have about 30 servers and
this one is probably the oldest. Does it signal that the hardware is startin
g
to fail? We have checked the RAID log records and everything seems normal.
This error could have been caused by a server restart one day earlier.
Best Regards,
MP Wong
"Greg D. Moore (Strider)" wrote:
>
> "mpWong" <mpWong@.discussions.microsoft.com> wrote in message
> news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> That doesn't sound good.
> Sounds like a corrupt transaction log on the model database. And since th
e
> model database should rarely change, it's even less likely you should see
> this.
> Does this continue to occur?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com [url]http://www.greenms.com/sqlserver.html[/ur
l]
>
>|||"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:501B9B7B-05BD-43B7-93C3-7CF75355D6A9@.microsoft.com...
> Hi Greg,
> This is the first time I have seen this error. We have about 30 servers
> and
> this one is probably the oldest. Does it signal that the hardware is
> starting
> to fail? We have checked the RAID log records and everything seems normal.
> This error could have been caused by a server restart one day earlier.
If it happened the one time... and you can correlate it with the server
restart, I'd PROBABLY ignore it.
But if it's happening more than once, then yes, definitely look at your
hardware.
[vbcol=seagreen]
>
> Best Regards,
> MP Wong
> "Greg D. Moore (Strider)" wrote:
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
LowLlevel Error
We see the below error from time to time as a popup message on the
desktop. The same error appears in the system event log as Source:
Application Popup Event ID: 26. We haven't been able to identify any
specific event which causes it to happen.
Start Error ----
Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
detected!
Program: C:\PROGRA~1\MICROS~1\MSSQL\binn\sqlservr.exe
A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
End Error ----
After the message appears, the running sqlservr.exe process is frozen
and clients can no longer access the database. Ending task from the
task manager doesn't even work and we have to reboot the server to get a
functioning SQL server service.
Anyone have ideas? I couldn't find much help with google. We are
running SQL Server 2000 with SP3.
~Jason
--No one has seen this error before? :(
~Jason
--
desktop. The same error appears in the system event log as Source:
Application Popup Event ID: 26. We haven't been able to identify any
specific event which causes it to happen.
Start Error ----
Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
detected!
Program: C:\PROGRA~1\MICROS~1\MSSQL\binn\sqlservr.exe
A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
End Error ----
After the message appears, the running sqlservr.exe process is frozen
and clients can no longer access the database. Ending task from the
task manager doesn't even work and we have to reboot the server to get a
functioning SQL server service.
Anyone have ideas? I couldn't find much help with google. We are
running SQL Server 2000 with SP3.
~Jason
--No one has seen this error before? :(
~Jason
--
Subscribe to:
Posts (Atom)