Showing posts with label message. Show all posts
Showing posts with label message. Show all posts

Thursday, March 29, 2012

Automating DBCC Checkdb

This is a multi-part message in MIME format.
--=_NextPart_000_0062_01C3E402.F8AADA80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sql Server 2000
If I ran a weekend job to perform a DBCC Checkdb on my databases, is = there an alert that I can monitor for which will inform me of any = problems discovered? Or is there a method to get the output of the DBCC = Checkdb to a text file? When running this command as a scheduled job, I = don't see the output I am in the habit of perusing for errors.
Please advise. Or tell me how you approach executing database = maintenance.
Thanx!
--=_NextPart_000_0062_01C3E402.F8AADA80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Sql Server 2000

If I ran a weekend job to perform a DBCC Checkdb on my databases, = is there an alert that I can monitor for which will inform me of any problems discovered? Or is there a method to get the output of the DBCC = Checkdb to a text file? When running this command as a scheduled job, I don't = see the output I am in the habit of perusing for errors.

Please advise. Or tell me how you approach executing database = maintenance.

Thanx!

--=_NextPart_000_0062_01C3E402.F8AADA80--Here's what I'd do:
Define two jobsteps, "at the end" of the job. One has subject "success", the
other "error". In these, you use xp_sendmail or xp_smtp_sendmail (I
recommend this: www.sqldev.net) In the "real" jobsteps, define "next step"
on success and on failure you go to the one where you send the email with
"failure".
In the DBCC jobstep, you define an output file, and in the mail jobsteps,
you specify that file as an attachment.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"JLS" <jlshoop@.hotmail.com> wrote in message
news:OiAUHxC5DHA.2776@.TK2MSFTNGP09.phx.gbl...
Sql Server 2000
If I ran a weekend job to perform a DBCC Checkdb on my databases, is there
an alert that I can monitor for which will inform me of any problems
discovered? Or is there a method to get the output of the DBCC Checkdb to a
text file? When running this command as a scheduled job, I don't see the
output I am in the habit of perusing for errors.
Please advise. Or tell me how you approach executing database maintenance.
Thanx!|||This is a multi-part message in MIME format.
--=_NextPart_000_0044_01C3E41D.ECAE0D40
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Use sqlmaint.exe utility as described in BOL. It can sends out put to a =file. The file could be in text and /or html format.
EXEC xp_sqlmaint '-S SQLSERVER -PlanName "DBMAINTPLAN 1" -CkDB -Rpt =D:\Dbmaint\DBCC.out -DelTxtRpt 2months -HtmlRpt =D:\Dbmaint\DBCC_result.htm'
Richard
"JLS" <jlshoop@.hotmail.com> wrote in message =news:OiAUHxC5DHA.2776@.TK2MSFTNGP09.phx.gbl...
Sql Server 2000
If I ran a weekend job to perform a DBCC Checkdb on my databases, is =there an alert that I can monitor for which will inform me of any =problems discovered? Or is there a method to get the output of the DBCC =Checkdb to a text file? When running this command as a scheduled job, I =don't see the output I am in the habit of perusing for errors.
Please advise. Or tell me how you approach executing database =maintenance.
Thanx!
--=_NextPart_000_0044_01C3E41D.ECAE0D40
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Use sqlmaint.exe utility as described =in BOL. It can sends out put to a file. The file could be in text and /or html format.
EXEC xp_sqlmaint ='-S SQLSERVER -PlanName "DBMAINTPLAN 1" -CkDB -Rpt D:\Dbmaint\DBCC.out =-DelTxtRpt 2months -HtmlRpt D:\Dbmaint\DBCC_result.htm'
Richard
"JLS" wrote =in message news:OiAUHxC5DHA.2776=@.TK2MSFTNGP09.phx.gbl...
Sql Server 2000

If I ran a weekend job to perform a DBCC Checkdb on my databases, =is there an alert that I can monitor for which will inform me of any =problems discovered? Or is there a method to get the output of the DBCC =Checkdb to a text file? When running this command as a scheduled job, I =don't see the output I am in the habit of perusing for errors.

Please advise. Or tell me how you approach executing =database maintenance.

Thanx!


--=_NextPart_000_0044_01C3E41D.ECAE0D40--|||This is a multi-part message in MIME format.
--=_NextPart_000_0012_01C3E4B6.7E0ABE80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thanx! Great advise, I like being pointed in the right direction =instead of spinning my wheels all over BOL.
"Richard Ding" <dingr@.cleanharbors.com> wrote in message =news:e8DcWfE5DHA.2432@.TK2MSFTNGP10.phx.gbl...
Use sqlmaint.exe utility as described in BOL. It can sends out put to =a file. The file could be in text and /or html format.
EXEC xp_sqlmaint '-S SQLSERVER -PlanName "DBMAINTPLAN 1" -CkDB -Rpt =D:\Dbmaint\DBCC.out -DelTxtRpt 2months -HtmlRpt =D:\Dbmaint\DBCC_result.htm'
Richard
"JLS" <jlshoop@.hotmail.com> wrote in message =news:OiAUHxC5DHA.2776@.TK2MSFTNGP09.phx.gbl...
Sql Server 2000
If I ran a weekend job to perform a DBCC Checkdb on my databases, is =there an alert that I can monitor for which will inform me of any =problems discovered? Or is there a method to get the output of the DBCC =Checkdb to a text file? When running this command as a scheduled job, I =don't see the output I am in the habit of perusing for errors.
Please advise. Or tell me how you approach executing database =maintenance.
Thanx!
--=_NextPart_000_0012_01C3E4B6.7E0ABE80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Thanx! Great advise, I like being pointed in the right =direction instead of spinning my wheels all over BOL.
"Richard Ding" =wrote in message news:e8DcWfE5DHA.2432=@.TK2MSFTNGP10.phx.gbl...
Use sqlmaint.exe utility as described =in BOL. It can sends out put to a file. The file could be in text and /or html format.
EXEC xp_sqlmaint ='-S SQLSERVER -PlanName "DBMAINTPLAN 1" -CkDB -Rpt D:\Dbmaint\DBCC.out =-DelTxtRpt 2months -HtmlRpt D:\Dbmaint\DBCC_result.htm'
Richard
"JLS" =wrote in message news:OiAUHxC5DHA.2776=@.TK2MSFTNGP09.phx.gbl...
Sql Server 2000

If I ran a weekend job to perform a DBCC Checkdb on my =databases, is there an alert that I can monitor for which will inform me of any =problems discovered? Or is there a method to get the output of the DBCC =Checkdb to a text file? When running this command as a scheduled job, =I don't see the output I am in the habit of perusing for errors.

Please advise. Or tell me how you approach executing =database maintenance.

Thanx!


--=_NextPart_000_0012_01C3E4B6.7E0ABE80--|||Thanx! Exactly the information I was looking for!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OCrGg$C5DHA.2344@.TK2MSFTNGP09.phx.gbl...
> Here's what I'd do:
> Define two jobsteps, "at the end" of the job. One has subject "success",
the
> other "error". In these, you use xp_sendmail or xp_smtp_sendmail (I
> recommend this: www.sqldev.net) In the "real" jobsteps, define "next step"
> on success and on failure you go to the one where you send the email with
> "failure".
> In the DBCC jobstep, you define an output file, and in the mail jobsteps,
> you specify that file as an attachment.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "JLS" <jlshoop@.hotmail.com> wrote in message
> news:OiAUHxC5DHA.2776@.TK2MSFTNGP09.phx.gbl...
> Sql Server 2000
> If I ran a weekend job to perform a DBCC Checkdb on my databases, is there
> an alert that I can monitor for which will inform me of any problems
> discovered? Or is there a method to get the output of the DBCC Checkdb to
a
> text file? When running this command as a scheduled job, I don't see the
> output I am in the habit of perusing for errors.
> Please advise. Or tell me how you approach executing database
maintenance.
> Thanx!
>
>

Thursday, March 22, 2012

Automatic Updates

OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
installed. I tell it to go ahead and install. It says it installed
successfully.
Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
I reboot just for the heck of it.
After I reboot I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
This has been going on for two weeks now. Any ideas?
Hi Mike
"Mike C#" wrote:

> OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
> installed. I tell it to go ahead and install. It says it installed
> successfully.
> Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> I reboot just for the heck of it.
> After I reboot I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> This has been going on for two weeks now. Any ideas?
>
What version is your SQL Server at? Do you have any other instances?
http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
explains the different versions and actions that should be taken including
not allowing Microsoft Update to apply SP2 if you have a hotfix that didn't
make SP2.
You could try applying http://support.microsoft.com/Default.aspx?Kbid=934459
John
|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:7A1CB953-70DF-4746-BCC5-11EF82180579@.microsoft.com...
> Hi Mike
> "Mike C#" wrote:
> What version is your SQL Server at? Do you have any other instances?
> http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
> explains the different versions and actions that should be taken including
> not allowing Microsoft Update to apply SP2 if you have a hotfix that
> didn't
> make SP2.
> You could try applying
> http://support.microsoft.com/Default.aspx?Kbid=934459
> John
Hi John,
9.00.3054. I'll check out the post, and let you know if it helps. Thanks!
Mike
|||Hi
"Mike C#" wrote:

> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:7A1CB953-70DF-4746-BCC5-11EF82180579@.microsoft.com...
> Hi John,
> 9.00.3054. I'll check out the post, and let you know if it helps. Thanks!
> Mike
>
If it doesn't work, you can tell windows update not to remind you of a patch
again, when you go through the custom installation, selecting the download
and checking the "Don't remind me again" checkbox.
Johm
|||"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:D6CFE0F8-8E64-4CD3-8004-7274A391A9C6@.microsoft.com...
> If it doesn't work, you can tell windows update not to remind you of a
> patch
> again, when you go through the custom installation, selecting the download
> and checking the "Don't remind me again" checkbox.
> Johm
I considered that, but decided against for now since I want to see if the
manual install actually works. I performed the manual install, and it
appears to have worked, but I want to give it a few more days to be sure.
Thanks
Mike

Automatic Updates

OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
installed. I tell it to go ahead and install. It says it installed
successfully.
Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
I reboot just for the heck of it.
After I reboot I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
This has been going on for two weeks now. Any ideas?Hi Mike
"Mike C#" wrote:
> OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
> installed. I tell it to go ahead and install. It says it installed
> successfully.
> Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> I reboot just for the heck of it.
> After I reboot I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> This has been going on for two weeks now. Any ideas?
>
What version is your SQL Server at? Do you have any other instances?
http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
explains the different versions and actions that should be taken including
not allowing Microsoft Update to apply SP2 if you have a hotfix that didn't
make SP2.
You could try applying http://support.microsoft.com/Default.aspx?Kbid=934459
John|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:7A1CB953-70DF-4746-BCC5-11EF82180579@.microsoft.com...
> Hi Mike
> "Mike C#" wrote:
>> OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
>> installed. I tell it to go ahead and install. It says it installed
>> successfully.
>> ...
> What version is your SQL Server at? Do you have any other instances?
> http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
> explains the different versions and actions that should be taken including
> not allowing Microsoft Update to apply SP2 if you have a hotfix that
> didn't
> make SP2.
> You could try applying
> http://support.microsoft.com/Default.aspx?Kbid=934459
> John
Hi John,
9.00.3054. I'll check out the post, and let you know if it helps. Thanks!
Mike|||Hi
"Mike C#" wrote:
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:7A1CB953-70DF-4746-BCC5-11EF82180579@.microsoft.com...
> > Hi Mike
> >
> > "Mike C#" wrote:
> >
> >> OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
> >> installed. I tell it to go ahead and install. It says it installed
> >> successfully.
> >> ...
> > What version is your SQL Server at? Do you have any other instances?
> >
> > http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
> > explains the different versions and actions that should be taken including
> > not allowing Microsoft Update to apply SP2 if you have a hotfix that
> > didn't
> > make SP2.
> >
> > You could try applying
> > http://support.microsoft.com/Default.aspx?Kbid=934459
> >
> > John
> Hi John,
> 9.00.3054. I'll check out the post, and let you know if it helps. Thanks!
> Mike
>
If it doesn't work, you can tell windows update not to remind you of a patch
again, when you go through the custom installation, selecting the download
and checking the "Don't remind me again" checkbox.
Johm|||"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:D6CFE0F8-8E64-4CD3-8004-7274A391A9C6@.microsoft.com...
> If it doesn't work, you can tell windows update not to remind you of a
> patch
> again, when you go through the custom installation, selecting the download
> and checking the "Don't remind me again" checkbox.
> Johm
I considered that, but decided against for now since I want to see if the
manual install actually works. I performed the manual install, and it
appears to have worked, but I want to give it a few more days to be sure.
Thanks
Mike

Tuesday, March 20, 2012

Automatic Updates

OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
installed. I tell it to go ahead and install. It says it installed
successfully.
Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
I reboot just for the heck of it.
After I reboot I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
This has been going on for two weeks now. Any ideas?Hi Mike
"Mike C#" wrote:

> OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
> installed. I tell it to go ahead and install. It says it installed
> successfully.
> Ten minutes later I get a message from Automatic Updates that SQL 2005 SP
2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> Ten minutes later I get a message from Automatic Updates that SQL 2005 SP
2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> I reboot just for the heck of it.
> After I reboot I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> This has been going on for two weeks now. Any ideas?
>
What version is your SQL Server at? Do you have any other instances?
http://blogs.msdn.com/psssql/archiv...-explained.aspx
explains the different versions and actions that should be taken including
not allowing Microsoft Update to apply SP2 if you have a hotfix that didn't
make SP2.
You could try applying http://support.microsoft.com/Default.aspx?Kbid=934459
John|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:7A1CB953-70DF-4746-BCC5-11EF82180579@.microsoft.com...
> Hi Mike
> "Mike C#" wrote:
>
> What version is your SQL Server at? Do you have any other instances?
> http://blogs.msdn.com/psssql/archiv...-explained.aspx
> explains the different versions and actions that should be taken including
> not allowing Microsoft Update to apply SP2 if you have a hotfix that
> didn't
> make SP2.
> You could try applying
> http://support.microsoft.com/Default.aspx?Kbid=934459
> John
Hi John,
9.00.3054. I'll check out the post, and let you know if it helps. Thanks!
Mike|||Hi
"Mike C#" wrote:

> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:7A1CB953-70DF-4746-BCC5-11EF82180579@.microsoft.com...
> Hi John,
> 9.00.3054. I'll check out the post, and let you know if it helps. Thanks
!
> Mike
>
If it doesn't work, you can tell windows update not to remind you of a patch
again, when you go through the custom installation, selecting the download
and checking the "Don't remind me again" checkbox.
Johm|||"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:D6CFE0F8-8E64-4CD3-8004-7274A391A9C6@.microsoft.com...
> If it doesn't work, you can tell windows update not to remind you of a
> patch
> again, when you go through the custom installation, selecting the download
> and checking the "Don't remind me again" checkbox.
> Johm
I considered that, but decided against for now since I want to see if the
manual install actually works. I performed the manual install, and it
appears to have worked, but I want to give it a few more days to be sure.
Thanks
Mikesql

Monday, March 19, 2012

Automatic Identity Range Handling warning message.

Ive implemented merge replication with SQL Server and an Access Database.
SQL Server is the publisher and Access database is the subscriber.
I have ONE table in the schema that can be updated in both the subscriber
side as well as the publisher side. I have an IDENTITY column in this table
and I have set the property "Automatic Identity Range Handling" ON for this
table.
Ive also created a script to create this publisher. Now, heres my problem.
When I create the publisher, I get a warning message thats stated below:
"Warning: only Subscribers running SQL Server 2000 can synchronize with
publication '<database>' because automatic identity ranges are being used."
OK, Ive done some resonable testing on this statement and it SEEMS that
synchronization with Automatic Identity Range Handing enabled DOES work for
Access databases as well even though the warning states otherwise! Im using
JET to connect to access and not the desktop engine. Once the threshold is
reached, and after the merge agent kicks in, the indentity seed is reset to
the appropriate values on both the access and the sql server side.
Appropriate check constraints are also placed.
I just want to make sure if this is correct - and this warning is just
bogus.
Thanks,
Girish
Hi Girish,
From your descriptions, I understood that you would like to know whether it
matters when warning is shown for "automatic identity ranges are being
used". Have I understood you? If there is anything I misunderstood, please
feel free to let me know.
Based on my scope, there are some known issues for us by using automatic
identity ranges. You could have a view on them
BUG: Unable to Change Identity Range of Publisher If You Use Auto Identity
Range
http://support.microsoft.com/default...b;en-us;310540
BUG: Identity Range Not Adjusted on Publisher When Merge Agent Runs
Continuously
http://support.microsoft.com/default...b;en-us;304706
Additionaly, there is a by design issue for automatic identity range based
on the descriptions in the following documents.
PRB: Automatic Identity Range Handling Is Not Correct If the Merge Agent
Runs an Insert Trigger
http://support.microsoft.com/default...b;en-us;324361
I am afraid the above all are why this warning is shown up.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Friday, February 24, 2012

Autogrow of log

I get this info message in my NT log:
Autogrow of file 'w2publish_Log' in database 'w2publish' was cancelled
by user or timed out after 546 milliseconds. Use ALTER DATABASE to
set a smaller FILEGROWTH value for this file or to explicitly set a
new file size.
This database is set to autogrow by 10%.
Searching the net, a few have suggested increasing the 10% to a larger
value. But it seems that the error is SQL Server failing to grow the
file in a timely manner. So moving from 10% to larger number will
only make matters worse. If I set it to a fixed size, what if that is
not enough?
What is the correct approach?
You don't want to set it larger you want to change it to a fixed size that
you know will grow in well under the timeout period. Once the files get
beyond 100MB or so you should change it to a fixed size of growth.
Andrew J. Kelly SQL MVP
"pbx" <pbeisel@.gmail.com> wrote in message
news:1183851948.581194.56800@.i38g2000prf.googlegro ups.com...
> I get this info message in my NT log:
> Autogrow of file 'w2publish_Log' in database 'w2publish' was cancelled
> by user or timed out after 546 milliseconds. Use ALTER DATABASE to
> set a smaller FILEGROWTH value for this file or to explicitly set a
> new file size.
> This database is set to autogrow by 10%.
> Searching the net, a few have suggested increasing the 10% to a larger
> value. But it seems that the error is SQL Server failing to grow the
> file in a timely manner. So moving from 10% to larger number will
> only make matters worse. If I set it to a fixed size, what if that is
> not enough?
> What is the correct approach?
>
|||Monitor how your database files grow. This will give you an idea on what
value to specify for autogrow increments. This is critical especially when
the files are very big (imagine 10% autogrow increments for 100GB database
files)
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%237Qq9gQwHHA.4640@.TK2MSFTNGP03.phx.gbl...
> You don't want to set it larger you want to change it to a fixed size that
> you know will grow in well under the timeout period. Once the files get
> beyond 100MB or so you should change it to a fixed size of growth.
> --
> Andrew J. Kelly SQL MVP
> "pbx" <pbeisel@.gmail.com> wrote in message
> news:1183851948.581194.56800@.i38g2000prf.googlegro ups.com...
>

Autogrow of log

I get this info message in my NT log:
Autogrow of file 'w2publish_Log' in database 'w2publish' was cancelled
by user or timed out after 546 milliseconds. Use ALTER DATABASE to
set a smaller FILEGROWTH value for this file or to explicitly set a
new file size.
This database is set to autogrow by 10%.
Searching the net, a few have suggested increasing the 10% to a larger
value. But it seems that the error is SQL Server failing to grow the
file in a timely manner. So moving from 10% to larger number will
only make matters worse. If I set it to a fixed size, what if that is
not enough?
What is the correct approach?You don't want to set it larger you want to change it to a fixed size that
you know will grow in well under the timeout period. Once the files get
beyond 100MB or so you should change it to a fixed size of growth.
Andrew J. Kelly SQL MVP
"pbx" <pbeisel@.gmail.com> wrote in message
news:1183851948.581194.56800@.i38g2000prf.googlegroups.com...
> I get this info message in my NT log:
> Autogrow of file 'w2publish_Log' in database 'w2publish' was cancelled
> by user or timed out after 546 milliseconds. Use ALTER DATABASE to
> set a smaller FILEGROWTH value for this file or to explicitly set a
> new file size.
> This database is set to autogrow by 10%.
> Searching the net, a few have suggested increasing the 10% to a larger
> value. But it seems that the error is SQL Server failing to grow the
> file in a timely manner. So moving from 10% to larger number will
> only make matters worse. If I set it to a fixed size, what if that is
> not enough?
> What is the correct approach?
>|||Monitor how your database files grow. This will give you an idea on what
value to specify for autogrow increments. This is critical especially when
the files are very big (imagine 10% autogrow increments for 100GB database
files)
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%237Qq9gQwHHA.4640@.TK2MSFTNGP03.phx.gbl...
> You don't want to set it larger you want to change it to a fixed size that
> you know will grow in well under the timeout period. Once the files get
> beyond 100MB or so you should change it to a fixed size of growth.
> --
> Andrew J. Kelly SQL MVP
> "pbx" <pbeisel@.gmail.com> wrote in message
> news:1183851948.581194.56800@.i38g2000prf.googlegroups.com...
>

Autogrow of log

I get this info message in my NT log:
Autogrow of file 'w2publish_Log' in database 'w2publish' was cancelled
by user or timed out after 546 milliseconds. Use ALTER DATABASE to
set a smaller FILEGROWTH value for this file or to explicitly set a
new file size.
This database is set to autogrow by 10%.
Searching the net, a few have suggested increasing the 10% to a larger
value. But it seems that the error is SQL Server failing to grow the
file in a timely manner. So moving from 10% to larger number will
only make matters worse. If I set it to a fixed size, what if that is
not enough?
What is the correct approach?You don't want to set it larger you want to change it to a fixed size that
you know will grow in well under the timeout period. Once the files get
beyond 100MB or so you should change it to a fixed size of growth.
--
Andrew J. Kelly SQL MVP
"pbx" <pbeisel@.gmail.com> wrote in message
news:1183851948.581194.56800@.i38g2000prf.googlegroups.com...
> I get this info message in my NT log:
> Autogrow of file 'w2publish_Log' in database 'w2publish' was cancelled
> by user or timed out after 546 milliseconds. Use ALTER DATABASE to
> set a smaller FILEGROWTH value for this file or to explicitly set a
> new file size.
> This database is set to autogrow by 10%.
> Searching the net, a few have suggested increasing the 10% to a larger
> value. But it seems that the error is SQL Server failing to grow the
> file in a timely manner. So moving from 10% to larger number will
> only make matters worse. If I set it to a fixed size, what if that is
> not enough?
> What is the correct approach?
>|||Monitor how your database files grow. This will give you an idea on what
value to specify for autogrow increments. This is critical especially when
the files are very big (imagine 10% autogrow increments for 100GB database
files)
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%237Qq9gQwHHA.4640@.TK2MSFTNGP03.phx.gbl...
> You don't want to set it larger you want to change it to a fixed size that
> you know will grow in well under the timeout period. Once the files get
> beyond 100MB or so you should change it to a fixed size of growth.
> --
> Andrew J. Kelly SQL MVP
> "pbx" <pbeisel@.gmail.com> wrote in message
> news:1183851948.581194.56800@.i38g2000prf.googlegroups.com...
>> I get this info message in my NT log:
>> Autogrow of file 'w2publish_Log' in database 'w2publish' was cancelled
>> by user or timed out after 546 milliseconds. Use ALTER DATABASE to
>> set a smaller FILEGROWTH value for this file or to explicitly set a
>> new file size.
>> This database is set to autogrow by 10%.
>> Searching the net, a few have suggested increasing the 10% to a larger
>> value. But it seems that the error is SQL Server failing to grow the
>> file in a timely manner. So moving from 10% to larger number will
>> only make matters worse. If I set it to a fixed size, what if that is
>> not enough?
>> What is the correct approach?
>

Autogenerate reply or ServerProc generated message............

Hello,

I got my sample application to work that I am building my proof of concept out of. I need to be able to auto generate a reply message that would normally be in the run routine. The only way I see to do this is pull it from a table but I do not want to do that. I have tried tests where I change the code to see if I can send a message back but I have to reinstall the assembly into the database which is not what I am looking for. I am looking for a way to change the message by either accessing the GUI and getting the string, calling another function to do this, or something like that. I want it so I can change the code in the run routine in VS 2005 but this does not work. I am sure their is a trick to do this but am not sure what that trick is. What is a good way to do this other than accessing a table in the database?

Thanks,

Scott Allison...

What do you mean by auto-generate a reply? A reply could either be static (i.e. independent of the request and state), a stateless (i.e. dependent only on the request) or stateful (i.e. dependent on both the request as well as some state... the state would normally be stored in the database, but may also be stored separately). I cannot see why you need to recompile and redeploy your app to meet any of the above patterns.

Rushi

|||

Hello Rushi,

It calls the ServiceProc in my code and that is loaded into the database. I am writing this for applications that will need to report the status of a current event. If this is not stored in the database then they would not want to write anything to the database. This means they will get the request then need to reply to that request with a text message that they generate. In the worst case situation it can come from the database but would rather just be retrieved from a function call. It seems as though from your message this can be done so I am sure I have a setting incorrect. What I have is currently static and I want the response dependent on the request. What I meant from Autogenerated is retrieved from another assembly or another part of that service.

Thanks,

Scott Allison...

|||If the function that generates a response from request is a method in a different assembly, you could deploy that assembly into the database and simply invoke the method from ServiceProc.|||

Hello Rushi,

This is a remote system and will not be able to deploy all of the assemblies to the database. It consists of several services and needs dynamic access to what the message. Are you telling me that the only way to get a dynamic message is to write it to a database and have the ServiceProc read it? This is a draw back beacuse it will slow things down but I want to make sure before I tell people that they have to do that.

Thanks,

Scott Allison...

AutoGenerate

Hi
I have set a field "MessageId" as primary in a Messages table. What I want is that whenever user inserts a message through my site, the MsSql should automatically generate MessageId for the new message inserted, but this is not happening. Any suggestions, advice are highly appreciated. Thank YouIs the column set as an IDENTITY column? If not, that explains the problem. In Enterprise Manager, go into Design mode for the table, and make sure in the properties window, Identity is True (or Yes, do not recall which is used).|||You've got to create a table in SQL with something like the below. As long as there is input in the column named "Message" then the MessageID will automatically increase.

CREATE TABLE Message
(
MessageID int IDENTITY(1,1) PRIMARY KEY,
Messagevarchar (2000)NOT NULL
)

Good luck!
-Gabian-|||Thanks to both of you gentleman.

One more thing, what enum of SqlDbtype should i keep for my actual Message(thats being recorded by the user) : "text" or "varChar" ?|||What are your needs:

Varchar will allow a maximum of 8000 bytes
Text will allow very large values ~ 2gb

Varchar will give you much more flexibility for searching and manipulating data though and if it is sufficient would be my recomendation.|||Depends on the size...

I usually use varchar (^_^)

Sunday, February 19, 2012

AUTOCLOSE

What does autoclose do ?
And why Starting up database message is repeated when autoclose is
true?"AMBROSE" <jeyaprabhu.j@.gmail.com> wrote in message
news:1172635162.065647.3570@.z35g2000cwz.googlegroups.com...
> What does autoclose do ?
> And why Starting up database message is repeated when autoclose is
> true?
>
If SQL Server doesn't detect usage of the said database in some interval
(can't recall what it is) it "closes" the database.
Then next time there's access, it reopens it, hence the startup up messages.
I recommend keeping autoclose turned OFF.
--
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||This database option "closes" the database file whenever the last users
disconnects from the database. The resources are freed up,
but when a new user connects to the server, the database is reopened and
takes up some resources. So it is good to make this option turned
off for all databases in a production server.
Thanks
Hari
"AMBROSE" <jeyaprabhu.j@.gmail.com> wrote in message
news:1172635162.065647.3570@.z35g2000cwz.googlegroups.com...
> What does autoclose do ?
> And why Starting up database message is repeated when autoclose is
> true?
>|||On Feb 28, 9:56 am, "Hari Prasad" <hari_prasa...@.hotmail.com> wrote:
> This database option "closes" the database file whenever the last users
> disconnects from the database. The resources are freed up,
> but when a new user connects to the server, the database is reopened and
> takes up some resources. So it is good to make this option turned
> off for all databases in a production server.
> Thanks
> Hari
> "AMBROSE" <jeyaprabh...@.gmail.com> wrote in message
> news:1172635162.065647.3570@.z35g2000cwz.googlegroups.com...
> > What does autoclose do ?
> > And why Starting up database message is repeated when autoclose is
> > true?
Will autoclose option set to true create any login problem?|||> Will autoclose option set to true create any login problem?
It shouldn't and I haven't heard of such.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"AMBROSE" <jeyaprabhu.j@.gmail.com> wrote in message
news:1172639991.878459.94420@.h3g2000cwc.googlegroups.com...
> On Feb 28, 9:56 am, "Hari Prasad" <hari_prasa...@.hotmail.com> wrote:
>> This database option "closes" the database file whenever the last users
>> disconnects from the database. The resources are freed up,
>> but when a new user connects to the server, the database is reopened and
>> takes up some resources. So it is good to make this option turned
>> off for all databases in a production server.
>> Thanks
>> Hari
>> "AMBROSE" <jeyaprabh...@.gmail.com> wrote in message
>> news:1172635162.065647.3570@.z35g2000cwz.googlegroups.com...
>> > What does autoclose do ?
>> > And why Starting up database message is repeated when autoclose is
>> > true?
> Will autoclose option set to true create any login problem?
>|||Hi
"AMBROSE" wrote:
> On Feb 28, 9:56 am, "Hari Prasad" <hari_prasa...@.hotmail.com> wrote:
> > This database option "closes" the database file whenever the last users
> > disconnects from the database. The resources are freed up,
> > but when a new user connects to the server, the database is reopened and
> > takes up some resources. So it is good to make this option turned
> > off for all databases in a production server.
> >
> > Thanks
> > Hari
> >
> > "AMBROSE" <jeyaprabh...@.gmail.com> wrote in message
> >
> > news:1172635162.065647.3570@.z35g2000cwz.googlegroups.com...
> >
> > > What does autoclose do ?
> >
> > > And why Starting up database message is repeated when autoclose is
> > > true?
> Will autoclose option set to true create any login problem?
>
If you have Anti-Virus software scanning your database files there can be
problems opening the database if a scan is occurring.
You may want to read http://support.microsoft.com/default.aspx/kb/309422
John|||On Feb 27, 11:19 pm, "AMBROSE" <jeyaprabh...@.gmail.com> wrote:
> Will autoclose option set to true create any login problem?
If the "default" database for a given login is "closed", and something
prevents it from being "opened", that login will fail.|||> Will autoclose option set to true create any login problem?
Sure, in addition to the other mentioned problems, if it takes a long time
to re-open the database, the login attempt may time out.
I strongly recommend NOT using autoclose.
--
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006

AUTOCLOSE

What does autoclose do ?
And why Starting up database message is repeated when autoclose is
true?
"AMBROSE" <jeyaprabhu.j@.gmail.com> wrote in message
news:1172635162.065647.3570@.z35g2000cwz.googlegrou ps.com...
> What does autoclose do ?
> And why Starting up database message is repeated when autoclose is
> true?
>
If SQL Server doesn't detect usage of the said database in some interval
(can't recall what it is) it "closes" the database.
Then next time there's access, it reopens it, hence the startup up messages.
I recommend keeping autoclose turned OFF.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
|||This database option "closes" the database file whenever the last users
disconnects from the database. The resources are freed up,
but when a new user connects to the server, the database is reopened and
takes up some resources. So it is good to make this option turned
off for all databases in a production server.
Thanks
Hari
"AMBROSE" <jeyaprabhu.j@.gmail.com> wrote in message
news:1172635162.065647.3570@.z35g2000cwz.googlegrou ps.com...
> What does autoclose do ?
> And why Starting up database message is repeated when autoclose is
> true?
>
|||On Feb 28, 9:56 am, "Hari Prasad" <hari_prasa...@.hotmail.com> wrote:[vbcol=seagreen]
> This database option "closes" the database file whenever the last users
> disconnects from the database. The resources are freed up,
> but when a new user connects to the server, the database is reopened and
> takes up some resources. So it is good to make this option turned
> off for all databases in a production server.
> Thanks
> Hari
> "AMBROSE" <jeyaprabh...@.gmail.com> wrote in message
> news:1172635162.065647.3570@.z35g2000cwz.googlegrou ps.com...
>
Will autoclose option set to true create any login problem?
|||Hi
"AMBROSE" wrote:

> On Feb 28, 9:56 am, "Hari Prasad" <hari_prasa...@.hotmail.com> wrote:
> Will autoclose option set to true create any login problem?
>
If you have Anti-Virus software scanning your database files there can be
problems opening the database if a scan is occurring.
You may want to read http://support.microsoft.com/default.aspx/kb/309422
John
|||On Feb 27, 11:19 pm, "AMBROSE" <jeyaprabh...@.gmail.com> wrote:
> Will autoclose option set to true create any login problem?
If the "default" database for a given login is "closed", and something
prevents it from being "opened", that login will fail.
|||> Will autoclose option set to true create any login problem?
Sure, in addition to the other mentioned problems, if it takes a long time
to re-open the database, the login attempt may time out.
I strongly recommend NOT using autoclose.
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006

AUTOCLOSE

What does autoclose do ?
And why Starting up database message is repeated when autoclose is
true?"AMBROSE" <jeyaprabhu.j@.gmail.com> wrote in message
news:1172635162.065647.3570@.z35g2000cwz.googlegroups.com...
> What does autoclose do ?
> And why Starting up database message is repeated when autoclose is
> true?
>
If SQL Server doesn't detect usage of the said database in some interval
(can't recall what it is) it "closes" the database.
Then next time there's access, it reopens it, hence the startup up messages.
I recommend keeping autoclose turned OFF.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||This database option "closes" the database file whenever the last users
disconnects from the database. The resources are freed up,
but when a new user connects to the server, the database is reopened and
takes up some resources. So it is good to make this option turned
off for all databases in a production server.
Thanks
Hari
"AMBROSE" <jeyaprabhu.j@.gmail.com> wrote in message
news:1172635162.065647.3570@.z35g2000cwz.googlegroups.com...
> What does autoclose do ?
> And why Starting up database message is repeated when autoclose is
> true?
>|||On Feb 28, 9:56 am, "Hari Prasad" <hari_prasa...@.hotmail.com> wrote:[vbcol=seagreen]
> This database option "closes" the database file whenever the last users
> disconnects from the database. The resources are freed up,
> but when a new user connects to the server, the database is reopened and
> takes up some resources. So it is good to make this option turned
> off for all databases in a production server.
> Thanks
> Hari
> "AMBROSE" <jeyaprabh...@.gmail.com> wrote in message
> news:1172635162.065647.3570@.z35g2000cwz.googlegroups.com...
>
>
Will autoclose option set to true create any login problem?|||> Will autoclose option set to true create any login problem?
It shouldn't and I haven't heard of such.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"AMBROSE" <jeyaprabhu.j@.gmail.com> wrote in message
news:1172639991.878459.94420@.h3g2000cwc.googlegroups.com...
> On Feb 28, 9:56 am, "Hari Prasad" <hari_prasa...@.hotmail.com> wrote:
> Will autoclose option set to true create any login problem?
>|||Hi
"AMBROSE" wrote:

> On Feb 28, 9:56 am, "Hari Prasad" <hari_prasa...@.hotmail.com> wrote:
> Will autoclose option set to true create any login problem?
>
If you have Anti-Virus software scanning your database files there can be
problems opening the database if a scan is occurring.
You may want to read http://support.microsoft.com/default.aspx/kb/309422
John|||On Feb 27, 11:19 pm, "AMBROSE" <jeyaprabh...@.gmail.com> wrote:
> Will autoclose option set to true create any login problem?
If the "default" database for a given login is "closed", and something
prevents it from being "opened", that login will fail.|||> Will autoclose option set to true create any login problem?
Sure, in addition to the other mentioned problems, if it takes a long time
to re-open the database, the login attempt may time out.
I strongly recommend NOT using autoclose.
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006