I need to scheduling a query to update some records.
I have to use a script in windows task manager or there is another way?
Many ThanksThe SQL Agent is a wonderful wat to schedule a query. Create a job and out
your query in a step.
"Simone" wrote:
> I need to scheduling a query to update some records.
> I have to use a script in windows task manager or there is another way?
> Many Thanks
>
>|||If you are using an edition of SQL Server which has an enterprise
manager and therefor a UI for SQL Server Agent, you can just create a
job with your query. Add a new job, add a new step (Transact SQL
Execution), paste your statement in there and add a schedule for it and
voil=E1, you=B4re done. iof you do=B4n=B4t have a GUI, you can use the
goold old fashioned AT to do your jobs. Just schedule your job by the
Windows Scheduler or AT, suing OSQL to run the query: OSQL -SServername
-UUsername -PPassword -Q"Here is my query".
HTH, jens Suessmeyer.|||you can create a job and schedule that
Jobs are under management-->Sql Server agent-->Jobs
make it a one step job paste your query or proc call in the step
command window and schedule the job
http://sqlservercode.blogspot.com/
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Monday, March 26, 2012
scheduling a query
I need to scheduling a query to update some records.
I have to use a script in windows task manager or there is another way?
Many ThanksIf you are using an edition of SQL Server which has an enterprise
manager and therefor a UI for SQL Server Agent, you can just create a
job with your query. Add a new job, add a new step (Transact SQL
Execution), paste your statement in there and add a schedule for it and
voil=E1, you=B4re done. iof you do=B4n=B4t have a GUI, you can use the
goold old fashioned AT to do your jobs. Just schedule your job by the
Windows Scheduler or AT, suing OSQL to run the query: OSQL -SServername
-UUsername -PPassword -Q"Here is my query".
HTH, jens Suessmeyer.|||The SQL Agent is a wonderful wat to schedule a query. Create a job and out
your query in a step.
"Simone" wrote:
> I need to scheduling a query to update some records.
> I have to use a script in windows task manager or there is another way?
> Many Thanks
>
>|||you can create a job and schedule that
Jobs are under management-->Sql Server agent-->Jobs
make it a one step job paste your query or proc call in the step
command window and schedule the job
http://sqlservercode.blogspot.com/
I have to use a script in windows task manager or there is another way?
Many ThanksIf you are using an edition of SQL Server which has an enterprise
manager and therefor a UI for SQL Server Agent, you can just create a
job with your query. Add a new job, add a new step (Transact SQL
Execution), paste your statement in there and add a schedule for it and
voil=E1, you=B4re done. iof you do=B4n=B4t have a GUI, you can use the
goold old fashioned AT to do your jobs. Just schedule your job by the
Windows Scheduler or AT, suing OSQL to run the query: OSQL -SServername
-UUsername -PPassword -Q"Here is my query".
HTH, jens Suessmeyer.|||The SQL Agent is a wonderful wat to schedule a query. Create a job and out
your query in a step.
"Simone" wrote:
> I need to scheduling a query to update some records.
> I have to use a script in windows task manager or there is another way?
> Many Thanks
>
>|||you can create a job and schedule that
Jobs are under management-->Sql Server agent-->Jobs
make it a one step job paste your query or proc call in the step
command window and schedule the job
http://sqlservercode.blogspot.com/
scheduling a query
I need to scheduling a query to update some records.
I have to use a script in windows task manager or there is another way?
Many Thanks
The SQL Agent is a wonderful wat to schedule a query. Create a job and out
your query in a step.
"Simone" wrote:
> I need to scheduling a query to update some records.
> I have to use a script in windows task manager or there is another way?
> Many Thanks
>
>
|||If you are using an edition of SQL Server which has an enterprise
manager and therefor a UI for SQL Server Agent, you can just create a
job with your query. Add a new job, add a new step (Transact SQL
Execution), paste your statement in there and add a schedule for it and
voil=E1, you=B4re done. iof you do=B4n=B4t have a GUI, you can use the
goold old fashioned AT to do your jobs. Just schedule your job by the
Windows Scheduler or AT, suing OSQL to run the query: OSQL -SServername
-UUsername -PPassword -Q"Here is my query".
HTH, jens Suessmeyer.
|||you can create a job and schedule that
Jobs are under management-->Sql Server agent-->Jobs
make it a one step job paste your query or proc call in the step
command window and schedule the job
http://sqlservercode.blogspot.com/
I have to use a script in windows task manager or there is another way?
Many Thanks
The SQL Agent is a wonderful wat to schedule a query. Create a job and out
your query in a step.
"Simone" wrote:
> I need to scheduling a query to update some records.
> I have to use a script in windows task manager or there is another way?
> Many Thanks
>
>
|||If you are using an edition of SQL Server which has an enterprise
manager and therefor a UI for SQL Server Agent, you can just create a
job with your query. Add a new job, add a new step (Transact SQL
Execution), paste your statement in there and add a schedule for it and
voil=E1, you=B4re done. iof you do=B4n=B4t have a GUI, you can use the
goold old fashioned AT to do your jobs. Just schedule your job by the
Windows Scheduler or AT, suing OSQL to run the query: OSQL -SServername
-UUsername -PPassword -Q"Here is my query".
HTH, jens Suessmeyer.
|||you can create a job and schedule that
Jobs are under management-->Sql Server agent-->Jobs
make it a one step job paste your query or proc call in the step
command window and schedule the job
http://sqlservercode.blogspot.com/
Friday, March 23, 2012
Scheduler appears to be hung
Hi,
I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
two databases that are used continously about two months back to this server
and since then I have noticed this error coming up every 10 to 15 days.
The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
Error: 17883, Severity: 1, State: 0
The SQL Server just freezes and becomes non-responsive. The above error was
present for almost 8 minutes before it started responding. At one time, I
wasn't even able to do a Remote Desktop to the server to check why the server
is not responding and later on I found that it had the same error. Any
information regarding this will be highly appreciated.How many processors do you have running? This implies two, or at least one
with hyperthreading. You might try turning one off completely.
"sharman" wrote:
> Hi,
> I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
> two databases that are used continously about two months back to this server
> and since then I have noticed this error coming up every 10 to 15 days.
> The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
> Error: 17883, Severity: 1, State: 0
> The SQL Server just freezes and becomes non-responsive. The above error was
> present for almost 8 minutes before it started responding. At one time, I
> wasn't even able to do a Remote Desktop to the server to check why the server
> is not responding and later on I found that it had the same error. Any
> information regarding this will be highly appreciated.|||For starters, just set SQL Server to use a single processor under the
instance properties. Also, you might want to apply SP4...
"sharman" wrote:
> Thanks for the information. It has 2 processors. How do I turn off
> hyperthreading and what are the implications of turning it off? Thanks.
> "James Luetkehoelter" wrote:
> > How many processors do you have running? This implies two, or at least one
> > with hyperthreading. You might try turning one off completely.
> >
> > "sharman" wrote:
> >
> > > Hi,
> > >
> > > I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
> > > two databases that are used continously about two months back to this server
> > > and since then I have noticed this error coming up every 10 to 15 days.
> > >
> > > The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
> > > Error: 17883, Severity: 1, State: 0
> > > The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
> > > Error: 17883, Severity: 1, State: 0
> > >
> > > The SQL Server just freezes and becomes non-responsive. The above error was
> > > present for almost 8 minutes before it started responding. At one time, I
> > > wasn't even able to do a Remote Desktop to the server to check why the server
> > > is not responding and later on I found that it had the same error. Any
> > > information regarding this will be highly appreciated.|||Thanks for the information. It has 2 processors. How do I turn off
hyperthreading and what are the implications of turning it off? Thanks.
"James Luetkehoelter" wrote:
> How many processors do you have running? This implies two, or at least one
> with hyperthreading. You might try turning one off completely.
> "sharman" wrote:
> > Hi,
> >
> > I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
> > two databases that are used continously about two months back to this server
> > and since then I have noticed this error coming up every 10 to 15 days.
> >
> > The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
> > Error: 17883, Severity: 1, State: 0
> > The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
> > Error: 17883, Severity: 1, State: 0
> >
> > The SQL Server just freezes and becomes non-responsive. The above error was
> > present for almost 8 minutes before it started responding. At one time, I
> > wasn't even able to do a Remote Desktop to the server to check why the server
> > is not responding and later on I found that it had the same error. Any
> > information regarding this will be highly appreciated.|||Hyperthreading can be diabled at the BIOS level. Most database applications
will experience an increase in performance with HT disabled. Test in your
environment.
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:0AEF20A0-A529-42BE-888B-C86BD6957F88@.microsoft.com...
> Thanks for the information. It has 2 processors. How do I turn off
> hyperthreading and what are the implications of turning it off? Thanks.
> "James Luetkehoelter" wrote:
>> How many processors do you have running? This implies two, or at least
>> one
>> with hyperthreading. You might try turning one off completely.
>> "sharman" wrote:
>> > Hi,
>> >
>> > I have a SQL Server 2000 SP3 running on Windows Server 2000. I have
>> > moved
>> > two databases that are used continously about two months back to this
>> > server
>> > and since then I have noticed this error coming up every 10 to 15 days.
>> >
>> > The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context
>> > 0x023339C0.
>> > Error: 17883, Severity: 1, State: 0
>> > The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context
>> > 0x0233C8D8.
>> > Error: 17883, Severity: 1, State: 0
>> >
>> > The SQL Server just freezes and becomes non-responsive. The above error
>> > was
>> > present for almost 8 minutes before it started responding. At one time,
>> > I
>> > wasn't even able to do a Remote Desktop to the server to check why the
>> > server
>> > is not responding and later on I found that it had the same error. Any
>> > information regarding this will be highly appreciated.|||Take a look at this excellent MS whitepaper:
http://www.microsoft.com/technet/prodtechnol/sql/2005/diagandcorrecterrs.mspx
Linchi
"sharman" wrote:
> Hi,
> I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
> two databases that are used continously about two months back to this server
> and since then I have noticed this error coming up every 10 to 15 days.
> The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
> Error: 17883, Severity: 1, State: 0
> The SQL Server just freezes and becomes non-responsive. The above error was
> present for almost 8 minutes before it started responding. At one time, I
> wasn't even able to do a Remote Desktop to the server to check why the server
> is not responding and later on I found that it had the same error. Any
> information regarding this will be highly appreciated.
I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
two databases that are used continously about two months back to this server
and since then I have noticed this error coming up every 10 to 15 days.
The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
Error: 17883, Severity: 1, State: 0
The SQL Server just freezes and becomes non-responsive. The above error was
present for almost 8 minutes before it started responding. At one time, I
wasn't even able to do a Remote Desktop to the server to check why the server
is not responding and later on I found that it had the same error. Any
information regarding this will be highly appreciated.How many processors do you have running? This implies two, or at least one
with hyperthreading. You might try turning one off completely.
"sharman" wrote:
> Hi,
> I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
> two databases that are used continously about two months back to this server
> and since then I have noticed this error coming up every 10 to 15 days.
> The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
> Error: 17883, Severity: 1, State: 0
> The SQL Server just freezes and becomes non-responsive. The above error was
> present for almost 8 minutes before it started responding. At one time, I
> wasn't even able to do a Remote Desktop to the server to check why the server
> is not responding and later on I found that it had the same error. Any
> information regarding this will be highly appreciated.|||For starters, just set SQL Server to use a single processor under the
instance properties. Also, you might want to apply SP4...
"sharman" wrote:
> Thanks for the information. It has 2 processors. How do I turn off
> hyperthreading and what are the implications of turning it off? Thanks.
> "James Luetkehoelter" wrote:
> > How many processors do you have running? This implies two, or at least one
> > with hyperthreading. You might try turning one off completely.
> >
> > "sharman" wrote:
> >
> > > Hi,
> > >
> > > I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
> > > two databases that are used continously about two months back to this server
> > > and since then I have noticed this error coming up every 10 to 15 days.
> > >
> > > The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
> > > Error: 17883, Severity: 1, State: 0
> > > The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
> > > Error: 17883, Severity: 1, State: 0
> > >
> > > The SQL Server just freezes and becomes non-responsive. The above error was
> > > present for almost 8 minutes before it started responding. At one time, I
> > > wasn't even able to do a Remote Desktop to the server to check why the server
> > > is not responding and later on I found that it had the same error. Any
> > > information regarding this will be highly appreciated.|||Thanks for the information. It has 2 processors. How do I turn off
hyperthreading and what are the implications of turning it off? Thanks.
"James Luetkehoelter" wrote:
> How many processors do you have running? This implies two, or at least one
> with hyperthreading. You might try turning one off completely.
> "sharman" wrote:
> > Hi,
> >
> > I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
> > two databases that are used continously about two months back to this server
> > and since then I have noticed this error coming up every 10 to 15 days.
> >
> > The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
> > Error: 17883, Severity: 1, State: 0
> > The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
> > Error: 17883, Severity: 1, State: 0
> >
> > The SQL Server just freezes and becomes non-responsive. The above error was
> > present for almost 8 minutes before it started responding. At one time, I
> > wasn't even able to do a Remote Desktop to the server to check why the server
> > is not responding and later on I found that it had the same error. Any
> > information regarding this will be highly appreciated.|||Hyperthreading can be diabled at the BIOS level. Most database applications
will experience an increase in performance with HT disabled. Test in your
environment.
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:0AEF20A0-A529-42BE-888B-C86BD6957F88@.microsoft.com...
> Thanks for the information. It has 2 processors. How do I turn off
> hyperthreading and what are the implications of turning it off? Thanks.
> "James Luetkehoelter" wrote:
>> How many processors do you have running? This implies two, or at least
>> one
>> with hyperthreading. You might try turning one off completely.
>> "sharman" wrote:
>> > Hi,
>> >
>> > I have a SQL Server 2000 SP3 running on Windows Server 2000. I have
>> > moved
>> > two databases that are used continously about two months back to this
>> > server
>> > and since then I have noticed this error coming up every 10 to 15 days.
>> >
>> > The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context
>> > 0x023339C0.
>> > Error: 17883, Severity: 1, State: 0
>> > The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context
>> > 0x0233C8D8.
>> > Error: 17883, Severity: 1, State: 0
>> >
>> > The SQL Server just freezes and becomes non-responsive. The above error
>> > was
>> > present for almost 8 minutes before it started responding. At one time,
>> > I
>> > wasn't even able to do a Remote Desktop to the server to check why the
>> > server
>> > is not responding and later on I found that it had the same error. Any
>> > information regarding this will be highly appreciated.|||Take a look at this excellent MS whitepaper:
http://www.microsoft.com/technet/prodtechnol/sql/2005/diagandcorrecterrs.mspx
Linchi
"sharman" wrote:
> Hi,
> I have a SQL Server 2000 SP3 running on Windows Server 2000. I have moved
> two databases that are used continously about two months back to this server
> and since then I have noticed this error coming up every 10 to 15 days.
> The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
> Error: 17883, Severity: 1, State: 0
> The SQL Server just freezes and becomes non-responsive. The above error was
> present for almost 8 minutes before it started responding. At one time, I
> wasn't even able to do a Remote Desktop to the server to check why the server
> is not responding and later on I found that it had the same error. Any
> information regarding this will be highly appreciated.
Scheduled Tasks on Windows 2000/2003
I'm trying to use scheduled tasks to copy over transaction logs from one server to another.
Can I schedule a task to run hourly? I have it set to repeat the task every hour, but it's not working. It does it once and then the next run date is tomorrow.
Please let me know if I'm missing something.
Thanks
Susan
Figured it out..
I had the repeat task selected, but had the duration at an hour and a half.
Once I modified the duration to 24 hours it worked great!!
Thanks
Susan
Wednesday, March 21, 2012
Scheduled reboot of SQL Server on Windows 2000
I am descerning whether it is a good idea (or necessary) to reboot our SQL
Server 2000 servers on a regular basis (E.g., monthly or quarterly). Are
there any performance benefits in doing this? Does this help to defragment
memory?
There's no real benefit. However, you will likely incur a performance
penalty each time, since it will have to repopulate the data cache.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Cajun" <Cajun@.discussions.microsoft.com> wrote in message
news:FECF4E55-A44B-42CE-86E0-9D0915BD6490@.microsoft.com...
I am descerning whether it is a good idea (or necessary) to reboot our SQL
Server 2000 servers on a regular basis (E.g., monthly or quarterly). Are
there any performance benefits in doing this? Does this help to defragment
memory?
|||Hi -
Experts says :-
"This is a fairly common question, and the answer is fairly straight
forward, no. Assuming you are using Windows NT Server 4.0 SP6a, or Windows
2000 Server SP4, or Windows 2003 Server, and are running SQL Server 7.0 or
2000 (any service packs), there is no reason to automatically reboot your
server. Doing so will not offer you any performance benefits or enhance
reliability.
There is a common myth among many IS people that Windows Server software
needs to be rebooted regularly for it to work efficiently. There may have
been a grain of truth to this in previous versions of Windows NT Server
(before 4.0), but since 4.0, there has not been any need to reboot Windows
Server on a regular basis.
I have seen many, many Windows servers that are virtually never rebooted,
and they never have any problems due to the OS.
On the other hand, I have seen poorly written applications written for
Windows Server that have memory leaks that have force the need to reboot the
server on a regular basis. But this problem is the fault of the application,
not the OS. It is very possible that less knowledgeable IS staff in general
have improperly diagnosed the cause of a server's problem and blamed it on
the OS, and not the application as they should, which is perpetuating this
myth.
Since your SQL Server is not having any problems, leave it alone, and tell
the other people on your staff to stop listening to urban legends."
"Cajun" wrote:
> I am descerning whether it is a good idea (or necessary) to reboot our SQL
> Server 2000 servers on a regular basis (E.g., monthly or quarterly). Are
> there any performance benefits in doing this? Does this help to defragment
> memory?
Server 2000 servers on a regular basis (E.g., monthly or quarterly). Are
there any performance benefits in doing this? Does this help to defragment
memory?
There's no real benefit. However, you will likely incur a performance
penalty each time, since it will have to repopulate the data cache.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Cajun" <Cajun@.discussions.microsoft.com> wrote in message
news:FECF4E55-A44B-42CE-86E0-9D0915BD6490@.microsoft.com...
I am descerning whether it is a good idea (or necessary) to reboot our SQL
Server 2000 servers on a regular basis (E.g., monthly or quarterly). Are
there any performance benefits in doing this? Does this help to defragment
memory?
|||Hi -
Experts says :-
"This is a fairly common question, and the answer is fairly straight
forward, no. Assuming you are using Windows NT Server 4.0 SP6a, or Windows
2000 Server SP4, or Windows 2003 Server, and are running SQL Server 7.0 or
2000 (any service packs), there is no reason to automatically reboot your
server. Doing so will not offer you any performance benefits or enhance
reliability.
There is a common myth among many IS people that Windows Server software
needs to be rebooted regularly for it to work efficiently. There may have
been a grain of truth to this in previous versions of Windows NT Server
(before 4.0), but since 4.0, there has not been any need to reboot Windows
Server on a regular basis.
I have seen many, many Windows servers that are virtually never rebooted,
and they never have any problems due to the OS.
On the other hand, I have seen poorly written applications written for
Windows Server that have memory leaks that have force the need to reboot the
server on a regular basis. But this problem is the fault of the application,
not the OS. It is very possible that less knowledgeable IS staff in general
have improperly diagnosed the cause of a server's problem and blamed it on
the OS, and not the application as they should, which is perpetuating this
myth.
Since your SQL Server is not having any problems, leave it alone, and tell
the other people on your staff to stop listening to urban legends."
"Cajun" wrote:
> I am descerning whether it is a good idea (or necessary) to reboot our SQL
> Server 2000 servers on a regular basis (E.g., monthly or quarterly). Are
> there any performance benefits in doing this? Does this help to defragment
> memory?
Scheduled reboot of SQL Server on Windows 2000
I am descerning whether it is a good idea (or necessary) to reboot our SQL
Server 2000 servers on a regular basis (E.g., monthly or quarterly). Are
there any performance benefits in doing this? Does this help to defragment
memory?There's no real benefit. However, you will likely incur a performance
penalty each time, since it will have to repopulate the data cache.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Cajun" <Cajun@.discussions.microsoft.com> wrote in message
news:FECF4E55-A44B-42CE-86E0-9D0915BD6490@.microsoft.com...
I am descerning whether it is a good idea (or necessary) to reboot our SQL
Server 2000 servers on a regular basis (E.g., monthly or quarterly). Are
there any performance benefits in doing this? Does this help to defragment
memory?|||Hi -
Experts says :-
"This is a fairly common question, and the answer is fairly straight
forward, no. Assuming you are using Windows NT Server 4.0 SP6a, or Windows
2000 Server SP4, or Windows 2003 Server, and are running SQL Server 7.0 or
2000 (any service packs), there is no reason to automatically reboot your
server. Doing so will not offer you any performance benefits or enhance
reliability.
There is a common myth among many IS people that Windows Server software
needs to be rebooted regularly for it to work efficiently. There may have
been a grain of truth to this in previous versions of Windows NT Server
(before 4.0), but since 4.0, there has not been any need to reboot Windows
Server on a regular basis.
I have seen many, many Windows servers that are virtually never rebooted,
and they never have any problems due to the OS.
On the other hand, I have seen poorly written applications written for
Windows Server that have memory leaks that have force the need to reboot the
server on a regular basis. But this problem is the fault of the application,
not the OS. It is very possible that less knowledgeable IS staff in general
have improperly diagnosed the cause of a server's problem and blamed it on
the OS, and not the application as they should, which is perpetuating this
myth.
Since your SQL Server is not having any problems, leave it alone, and tell
the other people on your staff to stop listening to urban legends."
"Cajun" wrote:
> I am descerning whether it is a good idea (or necessary) to reboot our SQL
> Server 2000 servers on a regular basis (E.g., monthly or quarterly). Are
> there any performance benefits in doing this? Does this help to defragmen
t
> memory?sql
Server 2000 servers on a regular basis (E.g., monthly or quarterly). Are
there any performance benefits in doing this? Does this help to defragment
memory?There's no real benefit. However, you will likely incur a performance
penalty each time, since it will have to repopulate the data cache.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Cajun" <Cajun@.discussions.microsoft.com> wrote in message
news:FECF4E55-A44B-42CE-86E0-9D0915BD6490@.microsoft.com...
I am descerning whether it is a good idea (or necessary) to reboot our SQL
Server 2000 servers on a regular basis (E.g., monthly or quarterly). Are
there any performance benefits in doing this? Does this help to defragment
memory?|||Hi -
Experts says :-
"This is a fairly common question, and the answer is fairly straight
forward, no. Assuming you are using Windows NT Server 4.0 SP6a, or Windows
2000 Server SP4, or Windows 2003 Server, and are running SQL Server 7.0 or
2000 (any service packs), there is no reason to automatically reboot your
server. Doing so will not offer you any performance benefits or enhance
reliability.
There is a common myth among many IS people that Windows Server software
needs to be rebooted regularly for it to work efficiently. There may have
been a grain of truth to this in previous versions of Windows NT Server
(before 4.0), but since 4.0, there has not been any need to reboot Windows
Server on a regular basis.
I have seen many, many Windows servers that are virtually never rebooted,
and they never have any problems due to the OS.
On the other hand, I have seen poorly written applications written for
Windows Server that have memory leaks that have force the need to reboot the
server on a regular basis. But this problem is the fault of the application,
not the OS. It is very possible that less knowledgeable IS staff in general
have improperly diagnosed the cause of a server's problem and blamed it on
the OS, and not the application as they should, which is perpetuating this
myth.
Since your SQL Server is not having any problems, leave it alone, and tell
the other people on your staff to stop listening to urban legends."
"Cajun" wrote:
> I am descerning whether it is a good idea (or necessary) to reboot our SQL
> Server 2000 servers on a regular basis (E.g., monthly or quarterly). Are
> there any performance benefits in doing this? Does this help to defragmen
t
> memory?sql
Scheduled jobs suddenly failing
I have MS SQL Server 2000 sp? on Windows 2000.
I have various jobs set up to run with the SQL Server Agent. I have a
job that imports data from an Access database located on the same
server. Then later, a job runs that updates some rows.
I have various jobs set up to run with the SQL Server Agent. I have a
job that imports data from an Access database located on the same
server. Then later, a job runs that updates some rows.
The import job fails with an error saying the source data is opened
exclusively by someone else, or I don't have permission. I have
verifed through various tests that no one else is using the source
Access database. I have even tried this import from excel files and
csv text files.
The job which updates a few rows will run with no problem.
This is a newly created job (actually a DTS package that was saved and
scheduled to run as a job)
Recently though, the server was renamed, and I feel this is the cause.
I have checked the msdb.sysjobs table and some of the jobs with the
new server name work, and some of them don't. The DTS jobs don't seem
to work.
I have maintenace jobs that used to run successfully, but now fail.
I have also tried to run the job with various users as well as SA.
Any ideas would greatly be appreciated.<OakRogbak_erPine@.yahoo.com> wrote in message
news:13fdc9b4.0408100537.1b66cbec@.posting.google.c om...
> I have MS SQL Server 2000 sp? on Windows 2000.
> I have various jobs set up to run with the SQL Server Agent. I have a
> job that imports data from an Access database located on the same
> server. Then later, a job runs that updates some rows.
> The import job fails with an error saying the source data is opened
> exclusively by someone else, or I don't have permission. I have
> verifed through various tests that no one else is using the source
> Access database. I have even tried this import from excel files and
> csv text files.
> The job which updates a few rows will run with no problem.
> This is a newly created job (actually a DTS package that was saved and
> scheduled to run as a job)
> Recently though, the server was renamed, and I feel this is the cause.
> I have checked the msdb.sysjobs table and some of the jobs with the
> new server name work, and some of them don't. The DTS jobs don't seem
> to work.
> I have maintenace jobs that used to run successfully, but now fail.
> I have also tried to run the job with various users as well as SA.
> Any ideas would greatly be appreciated.
You might want to investigate if the server name was changed correctly - did
you follow the steps in Books Online exactly?
http://support.microsoft.com/defaul...4&Product=sql2k
You might also want to check if sp_helpserver and select @.@.servername return
the correct output. If you have data sources in DTS packages which reference
the old name, then they will need to be updated in each package also (unless
you set the name dynamically at runtime of course).
If this doesn't help, please post the precise error messages, as well as the
version of MSSQL/Excel.
Simon
Monday, March 12, 2012
Scheduled DTS job to run a cmd file not working
Hi,
I have created a DTS job that contains one 'Execute SQL Task' job. This SQL task runs a cmd file. The cmd file runs a few windows commands and then runs a Micorosoft Access Macro. Once finished both access and the cmd screen close down.
If I open up the DTS job and execute it manually, it works fine (takes about 1/2 an hour to run). My problem is that when I schedule the DTS job, the job starts up at the correct time but it never actually starts running the cmd file and it gives no error. It says Executing until I actually stop the job manually.
The Job details are:
Type: Operating System Command [CmdExec]
Command: DTSRun /~Z0x2F3FF84472BB6E7FF356EB006BA1AEC62C95AB3BF506F3 4A241F228CE148AB09DBC66B8651A450B725E6C4E6A1D328E4 EC2F2C0F8E323F1C7D501FD5B8FD00E25656514AF2224407DB 1C569163CBE383A8E7D8BE4974A0911F5CEB
The DTS details are:
C:\Batches\DTSrunofUpdatesqlpmi.cmd
The cmd program details are:
echo on
:Start
if not exist "c:\apps\CI_Databases\pmi\pmiload.mdb" exit
rem cleanup unfinsihed runs
if exist "c:\apps\CI_Databases\pmi\pmiload.mdb" if exist "c:\apps\CI_Databases\pmi\pmiloadold.mdb" del "c:\apps\CI_Databases\pmi\pmiloadold.mdb"
rem main file locked assume its being work on so don't run this job.
if exist "c:\apps\CI_Databases\pmi\pmiload.ldb" exit
rem if a tmp exits then the last job never completed - continue to add to tmp file
if exist "c:\apps\CI_Databases\pmi\pmiloadtmp.mdb" goto Load
copy "c:\apps\CI_Databases\pmi\pmiload.mdb" "c:\apps\CI_Databases\pmi\pmiloadtmp.mdb"
:Load
"C:\Program Files\microsoft office 2003\OFFICE11\msaccess.exe" "c:\apps\CI_Databases\pmi\pmiloadtmp.mdb"/x updatedata
rem Compact databases
"C:\Program Files\microsoft office 2003\OFFICE11\msaccess.exe" "c:\apps\CI_Databases\pmi\pmiloadtmp.mdb"/compact
ren "c:\apps\CI_Databases\pmi\pmiload.mdb" "pmiloadold.mdb"
ren "c:\apps\CI_Databases\pmi\pmiloadtmp.mdb" "pmiload.mdb"
if exist "c:\apps\CI_Databases\pmi\pmiload.mdb" if exist "c:\apps\CI_Databases\pmi\pmiloadold.mdb" del "c:\apps\CI_Databases\pmi\pmiloadold.mdb"
All help is greatly appreciated as this has been bugging me for some time now.
Thanks
SamIf all your DTS package is doing is running a .cmd (batch) file, why not run it instead from a scheduled task. In the schedule task step, select task type of Operating system command and type in the path and name of the batch file.
This may not resolve the problem, however. I suspect that the problem lies within permissions. What account is the SQL Agent user set up to run under? Then think about what permissions your account has that the SQL Agent account might not have.
Regards,
hmscott|||Thanks hmscott.
That works when i change the SQL Server Agent startup account username and password.
I have created a DTS job that contains one 'Execute SQL Task' job. This SQL task runs a cmd file. The cmd file runs a few windows commands and then runs a Micorosoft Access Macro. Once finished both access and the cmd screen close down.
If I open up the DTS job and execute it manually, it works fine (takes about 1/2 an hour to run). My problem is that when I schedule the DTS job, the job starts up at the correct time but it never actually starts running the cmd file and it gives no error. It says Executing until I actually stop the job manually.
The Job details are:
Type: Operating System Command [CmdExec]
Command: DTSRun /~Z0x2F3FF84472BB6E7FF356EB006BA1AEC62C95AB3BF506F3 4A241F228CE148AB09DBC66B8651A450B725E6C4E6A1D328E4 EC2F2C0F8E323F1C7D501FD5B8FD00E25656514AF2224407DB 1C569163CBE383A8E7D8BE4974A0911F5CEB
The DTS details are:
C:\Batches\DTSrunofUpdatesqlpmi.cmd
The cmd program details are:
echo on
:Start
if not exist "c:\apps\CI_Databases\pmi\pmiload.mdb" exit
rem cleanup unfinsihed runs
if exist "c:\apps\CI_Databases\pmi\pmiload.mdb" if exist "c:\apps\CI_Databases\pmi\pmiloadold.mdb" del "c:\apps\CI_Databases\pmi\pmiloadold.mdb"
rem main file locked assume its being work on so don't run this job.
if exist "c:\apps\CI_Databases\pmi\pmiload.ldb" exit
rem if a tmp exits then the last job never completed - continue to add to tmp file
if exist "c:\apps\CI_Databases\pmi\pmiloadtmp.mdb" goto Load
copy "c:\apps\CI_Databases\pmi\pmiload.mdb" "c:\apps\CI_Databases\pmi\pmiloadtmp.mdb"
:Load
"C:\Program Files\microsoft office 2003\OFFICE11\msaccess.exe" "c:\apps\CI_Databases\pmi\pmiloadtmp.mdb"/x updatedata
rem Compact databases
"C:\Program Files\microsoft office 2003\OFFICE11\msaccess.exe" "c:\apps\CI_Databases\pmi\pmiloadtmp.mdb"/compact
ren "c:\apps\CI_Databases\pmi\pmiload.mdb" "pmiloadold.mdb"
ren "c:\apps\CI_Databases\pmi\pmiloadtmp.mdb" "pmiload.mdb"
if exist "c:\apps\CI_Databases\pmi\pmiload.mdb" if exist "c:\apps\CI_Databases\pmi\pmiloadold.mdb" del "c:\apps\CI_Databases\pmi\pmiloadold.mdb"
All help is greatly appreciated as this has been bugging me for some time now.
Thanks
SamIf all your DTS package is doing is running a .cmd (batch) file, why not run it instead from a scheduled task. In the schedule task step, select task type of Operating system command and type in the path and name of the batch file.
This may not resolve the problem, however. I suspect that the problem lies within permissions. What account is the SQL Agent user set up to run under? Then think about what permissions your account has that the SQL Agent account might not have.
Regards,
hmscott|||Thanks hmscott.
That works when i change the SQL Server Agent startup account username and password.
Friday, March 9, 2012
Scheduled backup
I just loaded SQL 2000 sp3a on a Windows 2003 server and
copied a 7.0 database over from another server to test.
I scheduled a backup for everyday at 1:00 am and noticed
that it did not do it last night.
It looks like the SQL server agent is set up and waiting
to run but it didn't.
What am I missing?In EM, Management, Jobs ensure Enabled = Yes, Scheduled = Yes , Runnable =Yes
--
HTH
Ryan Waight, MCDBA, MCSE
"Paul" <anonymous@.discussions.microsoft.com> wrote in message
news:11c001c3b435$12c0fdd0$a301280a@.phx.gbl...
> I just loaded SQL 2000 sp3a on a Windows 2003 server and
> copied a 7.0 database over from another server to test.
> I scheduled a backup for everyday at 1:00 am and noticed
> that it did not do it last night.
> It looks like the SQL server agent is set up and waiting
> to run but it didn't.
> What am I missing?
>|||Paul
A few ideas.
Most obvious, is SQL Agent running?
If it is have you checked the time on the server. If the
time is incorrect you may find your job kicking off any
time. Or have you changed the time on the server since
setting up the job. If you have re-create the job.
Have you looked in the Windows event log? If there are any
permissions problems you will see them there.
Hope this helps
John
copied a 7.0 database over from another server to test.
I scheduled a backup for everyday at 1:00 am and noticed
that it did not do it last night.
It looks like the SQL server agent is set up and waiting
to run but it didn't.
What am I missing?In EM, Management, Jobs ensure Enabled = Yes, Scheduled = Yes , Runnable =Yes
--
HTH
Ryan Waight, MCDBA, MCSE
"Paul" <anonymous@.discussions.microsoft.com> wrote in message
news:11c001c3b435$12c0fdd0$a301280a@.phx.gbl...
> I just loaded SQL 2000 sp3a on a Windows 2003 server and
> copied a 7.0 database over from another server to test.
> I scheduled a backup for everyday at 1:00 am and noticed
> that it did not do it last night.
> It looks like the SQL server agent is set up and waiting
> to run but it didn't.
> What am I missing?
>|||Paul
A few ideas.
Most obvious, is SQL Agent running?
If it is have you checked the time on the server. If the
time is incorrect you may find your job kicking off any
time. Or have you changed the time on the server since
setting up the job. If you have re-create the job.
Have you looked in the Windows event log? If there are any
permissions problems you will see them there.
Hope this helps
John
Wednesday, March 7, 2012
Schedule Restart Windows 2003 Server.
Hello,
I would like to know on how to SCHEDULE restart a server
which is running on a Windows 2003 Server platform at
anytime we desire.
thank you.
Try http://www.budja.com/shutdown/
You might want to try Windows newsgroups in the future as well!!!
Regards
Jamie Thomson
http://www.conchango.com
"Hadri" wrote:
> Hello,
> I would like to know on how to SCHEDULE restart a server
> which is running on a Windows 2003 Server platform at
> anytime we desire.
> thank you.
>
|||you can just use some command line.. i think that it comes with the Win2k3
resource kit.
Don't install 3rd party tools like that EVER
just use a batch file and command line argument, schedule it with the AT
command or windows scheduler, etc
"Hadri" <anonymous@.discussions.microsoft.com> wrote in message
news:3cdf01c4aaa0$a2736fa0$a401280a@.phx.gbl...
> Hello,
> I would like to know on how to SCHEDULE restart a server
> which is running on a Windows 2003 Server platform at
> anytime we desire.
> thank you.
I would like to know on how to SCHEDULE restart a server
which is running on a Windows 2003 Server platform at
anytime we desire.
thank you.
Try http://www.budja.com/shutdown/
You might want to try Windows newsgroups in the future as well!!!
Regards
Jamie Thomson
http://www.conchango.com
"Hadri" wrote:
> Hello,
> I would like to know on how to SCHEDULE restart a server
> which is running on a Windows 2003 Server platform at
> anytime we desire.
> thank you.
>
|||you can just use some command line.. i think that it comes with the Win2k3
resource kit.
Don't install 3rd party tools like that EVER
just use a batch file and command line argument, schedule it with the AT
command or windows scheduler, etc
"Hadri" <anonymous@.discussions.microsoft.com> wrote in message
news:3cdf01c4aaa0$a2736fa0$a401280a@.phx.gbl...
> Hello,
> I would like to know on how to SCHEDULE restart a server
> which is running on a Windows 2003 Server platform at
> anytime we desire.
> thank you.
Schedule problem with remote SQL instance.
Im running RS on Windows 2003 server, connecting to a remote instance of SQL.
When I try to set up a schedule for any report, i get...
"The SQL Agent service is not running. This operation requires the SQL Agent
service. (rsSchedulerNotResponding)"
I know its not finding any local sql agent on the server RS is running on,
what im wondering is if there is a way to hack it to use the SQL agent on a
remote SQL server to schedule these reports.
Thanks!i have the same problem..Did u find any solution?
"Jason Brinkley" wrote:
> Im running RS on Windows 2003 server, connecting to a remote instance of SQL.
> When I try to set up a schedule for any report, i get...
> "The SQL Agent service is not running. This operation requires the SQL Agent
> service. (rsSchedulerNotResponding)"
> I know its not finding any local sql agent on the server RS is running on,
> what im wondering is if there is a way to hack it to use the SQL agent on a
> remote SQL server to schedule these reports.
> Thanks!|||I am pretty sure the SQL Agent message IS talking about the server with the
database.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chitra" <Chitra@.discussions.microsoft.com> wrote in message
news:CAB5BEB8-36DD-490E-8AC5-15E57C19AC7B@.microsoft.com...
>i have the same problem..Did u find any solution?
> "Jason Brinkley" wrote:
>> Im running RS on Windows 2003 server, connecting to a remote instance of
>> SQL.
>> When I try to set up a schedule for any report, i get...
>> "The SQL Agent service is not running. This operation requires the SQL
>> Agent
>> service. (rsSchedulerNotResponding)"
>> I know its not finding any local sql agent on the server RS is running
>> on,
>> what im wondering is if there is a way to hack it to use the SQL agent on
>> a
>> remote SQL server to schedule these reports.
>> Thanks!
When I try to set up a schedule for any report, i get...
"The SQL Agent service is not running. This operation requires the SQL Agent
service. (rsSchedulerNotResponding)"
I know its not finding any local sql agent on the server RS is running on,
what im wondering is if there is a way to hack it to use the SQL agent on a
remote SQL server to schedule these reports.
Thanks!i have the same problem..Did u find any solution?
"Jason Brinkley" wrote:
> Im running RS on Windows 2003 server, connecting to a remote instance of SQL.
> When I try to set up a schedule for any report, i get...
> "The SQL Agent service is not running. This operation requires the SQL Agent
> service. (rsSchedulerNotResponding)"
> I know its not finding any local sql agent on the server RS is running on,
> what im wondering is if there is a way to hack it to use the SQL agent on a
> remote SQL server to schedule these reports.
> Thanks!|||I am pretty sure the SQL Agent message IS talking about the server with the
database.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chitra" <Chitra@.discussions.microsoft.com> wrote in message
news:CAB5BEB8-36DD-490E-8AC5-15E57C19AC7B@.microsoft.com...
>i have the same problem..Did u find any solution?
> "Jason Brinkley" wrote:
>> Im running RS on Windows 2003 server, connecting to a remote instance of
>> SQL.
>> When I try to set up a schedule for any report, i get...
>> "The SQL Agent service is not running. This operation requires the SQL
>> Agent
>> service. (rsSchedulerNotResponding)"
>> I know its not finding any local sql agent on the server RS is running
>> on,
>> what im wondering is if there is a way to hack it to use the SQL agent on
>> a
>> remote SQL server to schedule these reports.
>> Thanks!
Tuesday, February 21, 2012
Schedule and Delivery Processor errors
Hi all,
We're running into some random errors on our reporting server (Windows Server 2003, SQL Server 2000 Enterprise). In the application logs, we're seeing several Schedule and Delivery Processor errors (ID 108)...one for each processing extension (FileShare, Excel, HTML, etc.). In the security logs, at the same time of day, are several failure audits with the following info:
EventID: 680
User: NT AUTHORITY\SYSTEM
Description: Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0. Logon account: sqluser.
The odd thing is that the schedules that are failing run perfectly about 98% of the time. Once every few weeks we have a situation like this and all of our reports (approximately 200 of them...mostly Excel, all of them sent via E-Mail) fail.
Any ideas as to what might be causing this, and why it would only happen occasionally? Any help would be appreciated! Thanks!
-Brian
http://searchwindowssecurity.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid45_gci1007131_tax299886,00.html?bucket=ETA&topic=299886|||Thanks Greg, however this link seems to relate to making sure the ASP.NET account has the appropriate permissions on both the web server and the database. In my situation, the account (sqluser) has the correct permissions for the database. The database and report server/IIS are both on the same box if that matters.
In fact, and this is what is really confusing me, everything works just fine for weeks on end...then without warning I start getting these errors and the jobs fail. Same account, same reports, same schedules, same recipients...nothing has changed, yet something has caused these errors. Any other thoughts?
|||
Do you think it could be a DOS attack?
Is it happening the same day of the week? Same time of day?
How many "accounts" are accessing the server? Some versions of SQL have a max amount of connections before it denies access.
Subscribe to:
Posts (Atom)