I have an instance of SQLServer which I would like to restart automatically
once a day due to memory leak issues. How can I best achieve this?
Thanks in advance for your help.rmuram wrote:
> I have an instance of SQLServer which I would like to restart
> automatically once a day due to memory leak issues. How can I best
> achieve this?
> Thanks in advance for your help.
I think before you go this route, we should discuss the memory issues. I
have not seen any reported memory leak issues with SQL Server. Some may
exist, but I have not seen them. What is often reported as a memory leak
issue is generally not a problem, but a SQL Server design. If what you're
seeing is that SQL Server gradually consumes more and more memory on the
server without returning that memory to the server, this is by design. If
you are finding that you require additional memory for other services on the
server, then you should set an upper memory limit for the server to prevent
it from consuming too much. If OTOH you are seeing a memory leak issue,
please let us know in more detail what you are seeing.
To start stop the server manually, you can look at "Starting SQL Server
Manually" and "Stopping SQL Server" in BOL.
David Gugick
Quest Software|||Hi,
>From SQL Server it is imposssible to schedule a restart of SQL
Server.But can create a BATCH file.
HTH
from
Killer
rmuram wrote:
> I have an instance of SQLServer which I would like to restart automaticall
y
> once a day due to memory leak issues. How can I best achieve this?
> Thanks in advance for your help.|||Thanks David for the reply.
My use of the descrition 'memory leak' was not not entirely correct and wh
at
I am seeing is as described you described below.
> If what you're seeing is that SQL Server gradually consumes more and more
> memory on the server without returning that memory to the server, this is
by
> design.
What happens if I set the upperlimit to the memory usage? Will it free up
memory to serve additional requests etc?
I would still like to know if there are ways to automate startup/shutdown if
anybody has any experience.
Thanks.
"David Gugick" wrote:
> rmuram wrote:
> I think before you go this route, we should discuss the memory issues. I
> have not seen any reported memory leak issues with SQL Server. Some may
> exist, but I have not seen them. What is often reported as a memory leak
> issue is generally not a problem, but a SQL Server design. If what you're
> seeing is that SQL Server gradually consumes more and more memory on the
> server without returning that memory to the server, this is by design. If
> you are finding that you require additional memory for other services on t
he
> server, then you should set an upper memory limit for the server to preven
t
> it from consuming too much. If OTOH you are seeing a memory leak issue,
> please let us know in more detail what you are seeing.
> To start stop the server manually, you can look at "Starting SQL Server
> Manually" and "Stopping SQL Server" in BOL.
>
> --
> David Gugick
> Quest Software
>
>|||Thanks for the reply.
Do you have a sample I can work from?
"doller" wrote:
> Hi,
>
> Server.But can create a BATCH file.
> HTH
> from
> Killer
> rmuram wrote:
>|||Hi rmura,
If u want to create a backfile to start and stop of sql server the u
have to follow these steps
open command prompt
write net stop mssqlsever
if will ask u to stop sql agent y/n : press y
then it will ask u to stop sql server y/n : press y
so u can create a backfile
like this
cd \
net stop mssqlserver
y
to start sql sever
add the code
net start mssqlserver
now u need to start sql agent
add these code
net start sqlserveragent
HTH
from
Killer|||Here's some info on SQL Server's memory usage:
INF: SQL Server Memory Usage
http://support.microsoft.com/defaul...b;en-us;q321363
http://www.mssqlserver.com/faq/trou...-memoryleak.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"rmuram" <rmuram@.discussions.microsoft.com> wrote in message
news:CCC09FAF-9647-4210-9C2A-779AF6FB760C@.microsoft.com...
>I have an instance of SQLServer which I would like to restart automatically
> once a day due to memory leak issues. How can I best achieve this?
> Thanks in advance for your help.
Showing posts with label due. Show all posts
Showing posts with label due. Show all posts
Friday, March 30, 2012
Scheduling SQL Server start/stop
I have an instance of SQLServer which I would like to restart automatically
once a day due to memory leak issues. How can I best achieve this?
Thanks in advance for your help.rmuram wrote:
> I have an instance of SQLServer which I would like to restart
> automatically once a day due to memory leak issues. How can I best
> achieve this?
> Thanks in advance for your help.
I think before you go this route, we should discuss the memory issues. I
have not seen any reported memory leak issues with SQL Server. Some may
exist, but I have not seen them. What is often reported as a memory leak
issue is generally not a problem, but a SQL Server design. If what you're
seeing is that SQL Server gradually consumes more and more memory on the
server without returning that memory to the server, this is by design. If
you are finding that you require additional memory for other services on the
server, then you should set an upper memory limit for the server to prevent
it from consuming too much. If OTOH you are seeing a memory leak issue,
please let us know in more detail what you are seeing.
To start stop the server manually, you can look at "Starting SQL Server
Manually" and "Stopping SQL Server" in BOL.
David Gugick
Quest Software|||Hi,
>From SQL Server it is imposssible to schedule a restart of SQL
Server.But can create a BATCH file.
HTH
from
Killer
rmuram wrote:
> I have an instance of SQLServer which I would like to restart automatically
> once a day due to memory leak issues. How can I best achieve this?
> Thanks in advance for your help.|||Thanks David for the reply.
My use of the descrition 'memory leak' was notã'not entirely correct and what
I am seeing is as described you described below.
> If what you're seeing is that SQL Server gradually consumes more and more
> memory on the server without returning that memory to the server, this is by
> design.
What happens if I set the upperlimit to the memory usage? Will it free up
memory to serve additional requests etc?
I would still like to know if there are ways to automate startup/shutdown if
anybody has any experience.
Thanks.
"David Gugick" wrote:
> rmuram wrote:
> > I have an instance of SQLServer which I would like to restart
> > automatically once a day due to memory leak issues. How can I best
> > achieve this?
> > Thanks in advance for your help.
> I think before you go this route, we should discuss the memory issues. I
> have not seen any reported memory leak issues with SQL Server. Some may
> exist, but I have not seen them. What is often reported as a memory leak
> issue is generally not a problem, but a SQL Server design. If what you're
> seeing is that SQL Server gradually consumes more and more memory on the
> server without returning that memory to the server, this is by design. If
> you are finding that you require additional memory for other services on the
> server, then you should set an upper memory limit for the server to prevent
> it from consuming too much. If OTOH you are seeing a memory leak issue,
> please let us know in more detail what you are seeing.
> To start stop the server manually, you can look at "Starting SQL Server
> Manually" and "Stopping SQL Server" in BOL.
>
> --
> David Gugick
> Quest Software
>
>|||Thanks for the reply.
Do you have a sample I can work from?
"doller" wrote:
> Hi,
> >From SQL Server it is imposssible to schedule a restart of SQL
> Server.But can create a BATCH file.
> HTH
> from
> Killer
> rmuram wrote:
> > I have an instance of SQLServer which I would like to restart automatically
> > once a day due to memory leak issues. How can I best achieve this?
> > Thanks in advance for your help.
>|||Hi rmura,
If u want to create a backfile to start and stop of sql server the u
have to follow these steps
open command prompt
write net stop mssqlsever
if will ask u to stop sql agent y/n : press y
then it will ask u to stop sql server y/n : press y
so u can create a backfile
like this
cd \
net stop mssqlserver
y
to start sql sever
add the code
net start mssqlserver
now u need to start sql agent
add these code
net start sqlserveragent
HTH
from
Killer|||Here's some info on SQL Server's memory usage:
INF: SQL Server Memory Usage
http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"rmuram" <rmuram@.discussions.microsoft.com> wrote in message
news:CCC09FAF-9647-4210-9C2A-779AF6FB760C@.microsoft.com...
>I have an instance of SQLServer which I would like to restart automatically
> once a day due to memory leak issues. How can I best achieve this?
> Thanks in advance for your help.
once a day due to memory leak issues. How can I best achieve this?
Thanks in advance for your help.rmuram wrote:
> I have an instance of SQLServer which I would like to restart
> automatically once a day due to memory leak issues. How can I best
> achieve this?
> Thanks in advance for your help.
I think before you go this route, we should discuss the memory issues. I
have not seen any reported memory leak issues with SQL Server. Some may
exist, but I have not seen them. What is often reported as a memory leak
issue is generally not a problem, but a SQL Server design. If what you're
seeing is that SQL Server gradually consumes more and more memory on the
server without returning that memory to the server, this is by design. If
you are finding that you require additional memory for other services on the
server, then you should set an upper memory limit for the server to prevent
it from consuming too much. If OTOH you are seeing a memory leak issue,
please let us know in more detail what you are seeing.
To start stop the server manually, you can look at "Starting SQL Server
Manually" and "Stopping SQL Server" in BOL.
David Gugick
Quest Software|||Hi,
>From SQL Server it is imposssible to schedule a restart of SQL
Server.But can create a BATCH file.
HTH
from
Killer
rmuram wrote:
> I have an instance of SQLServer which I would like to restart automatically
> once a day due to memory leak issues. How can I best achieve this?
> Thanks in advance for your help.|||Thanks David for the reply.
My use of the descrition 'memory leak' was notã'not entirely correct and what
I am seeing is as described you described below.
> If what you're seeing is that SQL Server gradually consumes more and more
> memory on the server without returning that memory to the server, this is by
> design.
What happens if I set the upperlimit to the memory usage? Will it free up
memory to serve additional requests etc?
I would still like to know if there are ways to automate startup/shutdown if
anybody has any experience.
Thanks.
"David Gugick" wrote:
> rmuram wrote:
> > I have an instance of SQLServer which I would like to restart
> > automatically once a day due to memory leak issues. How can I best
> > achieve this?
> > Thanks in advance for your help.
> I think before you go this route, we should discuss the memory issues. I
> have not seen any reported memory leak issues with SQL Server. Some may
> exist, but I have not seen them. What is often reported as a memory leak
> issue is generally not a problem, but a SQL Server design. If what you're
> seeing is that SQL Server gradually consumes more and more memory on the
> server without returning that memory to the server, this is by design. If
> you are finding that you require additional memory for other services on the
> server, then you should set an upper memory limit for the server to prevent
> it from consuming too much. If OTOH you are seeing a memory leak issue,
> please let us know in more detail what you are seeing.
> To start stop the server manually, you can look at "Starting SQL Server
> Manually" and "Stopping SQL Server" in BOL.
>
> --
> David Gugick
> Quest Software
>
>|||Thanks for the reply.
Do you have a sample I can work from?
"doller" wrote:
> Hi,
> >From SQL Server it is imposssible to schedule a restart of SQL
> Server.But can create a BATCH file.
> HTH
> from
> Killer
> rmuram wrote:
> > I have an instance of SQLServer which I would like to restart automatically
> > once a day due to memory leak issues. How can I best achieve this?
> > Thanks in advance for your help.
>|||Hi rmura,
If u want to create a backfile to start and stop of sql server the u
have to follow these steps
open command prompt
write net stop mssqlsever
if will ask u to stop sql agent y/n : press y
then it will ask u to stop sql server y/n : press y
so u can create a backfile
like this
cd \
net stop mssqlserver
y
to start sql sever
add the code
net start mssqlserver
now u need to start sql agent
add these code
net start sqlserveragent
HTH
from
Killer|||Here's some info on SQL Server's memory usage:
INF: SQL Server Memory Usage
http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"rmuram" <rmuram@.discussions.microsoft.com> wrote in message
news:CCC09FAF-9647-4210-9C2A-779AF6FB760C@.microsoft.com...
>I have an instance of SQLServer which I would like to restart automatically
> once a day due to memory leak issues. How can I best achieve this?
> Thanks in advance for your help.
Scheduling SQL Server start/stop
I have an instance of SQLServer which I would like to restart automatically
once a day due to memory leak issues. How can I best achieve this?
Thanks in advance for your help.
rmuram wrote:
> I have an instance of SQLServer which I would like to restart
> automatically once a day due to memory leak issues. How can I best
> achieve this?
> Thanks in advance for your help.
I think before you go this route, we should discuss the memory issues. I
have not seen any reported memory leak issues with SQL Server. Some may
exist, but I have not seen them. What is often reported as a memory leak
issue is generally not a problem, but a SQL Server design. If what you're
seeing is that SQL Server gradually consumes more and more memory on the
server without returning that memory to the server, this is by design. If
you are finding that you require additional memory for other services on the
server, then you should set an upper memory limit for the server to prevent
it from consuming too much. If OTOH you are seeing a memory leak issue,
please let us know in more detail what you are seeing.
To start stop the server manually, you can look at "Starting SQL Server
Manually" and "Stopping SQL Server" in BOL.
David Gugick
Quest Software
|||Hi,
>From SQL Server it is imposssible to schedule a restart of SQL
Server.But can create a BATCH file.
HTH
from
Killer
rmuram wrote:
> I have an instance of SQLServer which I would like to restart automatically
> once a day due to memory leak issues. How can I best achieve this?
> Thanks in advance for your help.
|||Thanks David for the reply.
My use of the descrition 'memory leak' was not not entirely correct and what
I am seeing is as described you described below.
> If what you're seeing is that SQL Server gradually consumes more and more
> memory on the server without returning that memory to the server, this is by
> design.
What happens if I set the upperlimit to the memory usage? Will it free up
memory to serve additional requests etc?
I would still like to know if there are ways to automate startup/shutdown if
anybody has any experience.
Thanks.
"David Gugick" wrote:
> rmuram wrote:
> I think before you go this route, we should discuss the memory issues. I
> have not seen any reported memory leak issues with SQL Server. Some may
> exist, but I have not seen them. What is often reported as a memory leak
> issue is generally not a problem, but a SQL Server design. If what you're
> seeing is that SQL Server gradually consumes more and more memory on the
> server without returning that memory to the server, this is by design. If
> you are finding that you require additional memory for other services on the
> server, then you should set an upper memory limit for the server to prevent
> it from consuming too much. If OTOH you are seeing a memory leak issue,
> please let us know in more detail what you are seeing.
> To start stop the server manually, you can look at "Starting SQL Server
> Manually" and "Stopping SQL Server" in BOL.
>
> --
> David Gugick
> Quest Software
>
>
|||Thanks for the reply.
Do you have a sample I can work from?
"doller" wrote:
> Hi,
> Server.But can create a BATCH file.
> HTH
> from
> Killer
> rmuram wrote:
>
|||Hi rmura,
If u want to create a backfile to start and stop of sql server the u
have to follow these steps
open command prompt
write net stop mssqlsever
if will ask u to stop sql agent y/n : press y
then it will ask u to stop sql server y/n : press y
so u can create a backfile
like this
cd \
net stop mssqlserver
y
to start sql sever
add the code
net start mssqlserver
now u need to start sql agent
add these code
net start sqlserveragent
HTH
from
Killer
|||Here's some info on SQL Server's memory usage:
INF: SQL Server Memory Usage
http://support.microsoft.com/default...;en-us;q321363
http://www.mssqlserver.com/faq/troub...memoryleak.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"rmuram" <rmuram@.discussions.microsoft.com> wrote in message
news:CCC09FAF-9647-4210-9C2A-779AF6FB760C@.microsoft.com...
>I have an instance of SQLServer which I would like to restart automatically
> once a day due to memory leak issues. How can I best achieve this?
> Thanks in advance for your help.
once a day due to memory leak issues. How can I best achieve this?
Thanks in advance for your help.
rmuram wrote:
> I have an instance of SQLServer which I would like to restart
> automatically once a day due to memory leak issues. How can I best
> achieve this?
> Thanks in advance for your help.
I think before you go this route, we should discuss the memory issues. I
have not seen any reported memory leak issues with SQL Server. Some may
exist, but I have not seen them. What is often reported as a memory leak
issue is generally not a problem, but a SQL Server design. If what you're
seeing is that SQL Server gradually consumes more and more memory on the
server without returning that memory to the server, this is by design. If
you are finding that you require additional memory for other services on the
server, then you should set an upper memory limit for the server to prevent
it from consuming too much. If OTOH you are seeing a memory leak issue,
please let us know in more detail what you are seeing.
To start stop the server manually, you can look at "Starting SQL Server
Manually" and "Stopping SQL Server" in BOL.
David Gugick
Quest Software
|||Hi,
>From SQL Server it is imposssible to schedule a restart of SQL
Server.But can create a BATCH file.
HTH
from
Killer
rmuram wrote:
> I have an instance of SQLServer which I would like to restart automatically
> once a day due to memory leak issues. How can I best achieve this?
> Thanks in advance for your help.
|||Thanks David for the reply.
My use of the descrition 'memory leak' was not not entirely correct and what
I am seeing is as described you described below.
> If what you're seeing is that SQL Server gradually consumes more and more
> memory on the server without returning that memory to the server, this is by
> design.
What happens if I set the upperlimit to the memory usage? Will it free up
memory to serve additional requests etc?
I would still like to know if there are ways to automate startup/shutdown if
anybody has any experience.
Thanks.
"David Gugick" wrote:
> rmuram wrote:
> I think before you go this route, we should discuss the memory issues. I
> have not seen any reported memory leak issues with SQL Server. Some may
> exist, but I have not seen them. What is often reported as a memory leak
> issue is generally not a problem, but a SQL Server design. If what you're
> seeing is that SQL Server gradually consumes more and more memory on the
> server without returning that memory to the server, this is by design. If
> you are finding that you require additional memory for other services on the
> server, then you should set an upper memory limit for the server to prevent
> it from consuming too much. If OTOH you are seeing a memory leak issue,
> please let us know in more detail what you are seeing.
> To start stop the server manually, you can look at "Starting SQL Server
> Manually" and "Stopping SQL Server" in BOL.
>
> --
> David Gugick
> Quest Software
>
>
|||Thanks for the reply.
Do you have a sample I can work from?
"doller" wrote:
> Hi,
> Server.But can create a BATCH file.
> HTH
> from
> Killer
> rmuram wrote:
>
|||Hi rmura,
If u want to create a backfile to start and stop of sql server the u
have to follow these steps
open command prompt
write net stop mssqlsever
if will ask u to stop sql agent y/n : press y
then it will ask u to stop sql server y/n : press y
so u can create a backfile
like this
cd \
net stop mssqlserver
y
to start sql sever
add the code
net start mssqlserver
now u need to start sql agent
add these code
net start sqlserveragent
HTH
from
Killer
|||Here's some info on SQL Server's memory usage:
INF: SQL Server Memory Usage
http://support.microsoft.com/default...;en-us;q321363
http://www.mssqlserver.com/faq/troub...memoryleak.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"rmuram" <rmuram@.discussions.microsoft.com> wrote in message
news:CCC09FAF-9647-4210-9C2A-779AF6FB760C@.microsoft.com...
>I have an instance of SQLServer which I would like to restart automatically
> once a day due to memory leak issues. How can I best achieve this?
> Thanks in advance for your help.
Tuesday, February 21, 2012
Schedule a report to run at a particular time with user filled parameters
I have a report that I would like to run in the evening due to high database usage that required a user to fill in selected parameters. Is there anyway to allow a user to fill in the report parameters and have it scheduled to run at 3:00 AM.
Thanks,
Chris
You could use a data driven subscription, which relies on a table you create to store the parameters for the report. Then provide the user with a simple interface to set the parameters in the table.
Or you could let them create a linked report in their My Reports folder, and set up their own subscription from there, which allows them to specify parameters values.
|||Would you mind elaborating on this technique, or pass along some documentation/samples for this? I am most interested in how you setup this 'table' that stores the parameters for the report and of course how you configure the report to use the values in the table.Thanks!|||
I never did find a great solution to this problem. Please let me know if you do find one.
Thanks,
|||What part of the solutions that you were offered didn't you like? I thought they were both good, depending on business requirements, and I wasn't too sure from what you described which one would meet yours... but didn't expect to hear that you used neither <s>.
So... what was the issue in your case?
>L<
PS. You can also roll your own. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2022350&SiteID=1. But I'm not (yet) convinced you need to, in your case...
|||Neither of the above options worked for you?
Schedule a report to run at a particular time with user filled parameters
I have a report that I would like to run in the evening due to high database usage that required a user to fill in selected parameters. Is there anyway to allow a user to fill in the report parameters and have it scheduled to run at 3:00 AM.
Thanks,
Chris
You could use a data driven subscription, which relies on a table you create to store the parameters for the report. Then provide the user with a simple interface to set the parameters in the table.
Or you could let them create a linked report in their My Reports folder, and set up their own subscription from there, which allows them to specify parameters values.
|||Would you mind elaborating on this technique, or pass along some documentation/samples for this? I am most interested in how you setup this 'table' that stores the parameters for the report and of course how you configure the report to use the values in the table.Thanks!
|||
I never did find a great solution to this problem. Please let me know if you do find one.
Thanks,
|||What part of the solutions that you were offered didn't you like? I thought they were both good, depending on business requirements, and I wasn't too sure from what you described which one would meet yours... but didn't expect to hear that you used neither <s>.
So... what was the issue in your case?
>L<
PS. You can also roll your own. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2022350&SiteID=1. But I'm not (yet) convinced you need to, in your case...
|||Neither of the above options worked for you?Schedule a report to run at a particular time with user filled parameters
I have a report that I would like to run in the evening due to high database usage that required a user to fill in selected parameters. Is there anyway to allow a user to fill in the report parameters and have it scheduled to run at 3:00 AM.
Thanks,
Chris
You could use a data driven subscription, which relies on a table you create to store the parameters for the report. Then provide the user with a simple interface to set the parameters in the table.
Or you could let them create a linked report in their My Reports folder, and set up their own subscription from there, which allows them to specify parameters values.
|||Would you mind elaborating on this technique, or pass along some documentation/samples for this? I am most interested in how you setup this 'table' that stores the parameters for the report and of course how you configure the report to use the values in the table.Thanks!
|||
I never did find a great solution to this problem. Please let me know if you do find one.
Thanks,
|||What part of the solutions that you were offered didn't you like? I thought they were both good, depending on business requirements, and I wasn't too sure from what you described which one would meet yours... but didn't expect to hear that you used neither <s>.
So... what was the issue in your case?
>L<
PS. You can also roll your own. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2022350&SiteID=1. But I'm not (yet) convinced you need to, in your case...
|||Neither of the above options worked for you?
Subscribe to:
Posts (Atom)