Scheduling sp_updatestats

Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
Is there a better way to schedule that outside of a maintenance plan ?I prefer to use a SQL Agent Job. Using DTS isn't really necessary (and is
the wrong tool) in 'most' cases.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"J1C" <just1coder@.yahoo.ca> wrote in message
news:1164670349.026026.226980@.l39g2000cwd.googlegroups.com...
> Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> Is there a better way to schedule that outside of a maintenance plan ?
>|||Hello,
Why do you need DTS for this. All you have to do is:-
1. Open Enterprise Manager
2. Connect to SQL Server
3. Expand Management, Select Jobs and create new job.
4. In the job step give sp_updatestats and choose database
5. Provide a schedule to execute
6. Save the job
Based on the schedule.. SQL Server agent will trigger this job
Thanks
Hari
"J1C" <just1coder@.yahoo.ca> wrote in message
news:1164670349.026026.226980@.l39g2000cwd.googlegroups.com...
> Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> Is there a better way to schedule that outside of a maintenance plan ?
>|||Hari Prasad wrote:[vbcol=seagreen]
> Hello,
> Why do you need DTS for this. All you have to do is:-
> 1. Open Enterprise Manager
> 2. Connect to SQL Server
> 3. Expand Management, Select Jobs and create new job.
> 4. In the job step give sp_updatestats and choose database
> 5. Provide a schedule to execute
> 6. Save the job
> Based on the schedule.. SQL Server agent will trigger this job
> Thanks
> Hari
> "J1C" <just1coder@.yahoo.ca> wrote in message
> news:1164670349.026026.226980@.l39g2000cwd.googlegroups.com...
Thanks - that is what I ended up doing rather than DTS.

Scheduling sp_updatestats

Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
Is there a better way to schedule that outside of a maintenance plan ?I prefer to use a SQL Agent Job. Using DTS isn't really necessary (and is
the wrong tool) in 'most' cases.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"J1C" <just1coder@.yahoo.ca> wrote in message
news:1164670349.026026.226980@.l39g2000cwd.googlegroups.com...
> Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> Is there a better way to schedule that outside of a maintenance plan ?
>|||Hello,
Why do you need DTS for this. All you have to do is:-
1. Open Enterprise Manager
2. Connect to SQL Server
3. Expand Management, Select Jobs and create new job.
4. In the job step give sp_updatestats and choose database
5. Provide a schedule to execute
6. Save the job
Based on the schedule.. SQL Server agent will trigger this job
Thanks
Hari
"J1C" <just1coder@.yahoo.ca> wrote in message
news:1164670349.026026.226980@.l39g2000cwd.googlegroups.com...
> Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> Is there a better way to schedule that outside of a maintenance plan ?
>|||Hari Prasad wrote:
> Hello,
> Why do you need DTS for this. All you have to do is:-
> 1. Open Enterprise Manager
> 2. Connect to SQL Server
> 3. Expand Management, Select Jobs and create new job.
> 4. In the job step give sp_updatestats and choose database
> 5. Provide a schedule to execute
> 6. Save the job
> Based on the schedule.. SQL Server agent will trigger this job
> Thanks
> Hari
> "J1C" <just1coder@.yahoo.ca> wrote in message
> news:1164670349.026026.226980@.l39g2000cwd.googlegroups.com...
> > Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> > Is there a better way to schedule that outside of a maintenance plan ?
> >
Thanks - that is what I ended up doing rather than DTS.

Scheduling sp_updatestats

Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
Is there a better way to schedule that outside of a maintenance plan ?
I prefer to use a SQL Agent Job. Using DTS isn't really necessary (and is
the wrong tool) in 'most' cases.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"J1C" <just1coder@.yahoo.ca> wrote in message
news:1164670349.026026.226980@.l39g2000cwd.googlegr oups.com...
> Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> Is there a better way to schedule that outside of a maintenance plan ?
>
|||Hello,
Why do you need DTS for this. All you have to do is:-
1. Open Enterprise Manager
2. Connect to SQL Server
3. Expand Management, Select Jobs and create new job.
4. In the job step give sp_updatestats and choose database
5. Provide a schedule to execute
6. Save the job
Based on the schedule.. SQL Server agent will trigger this job
Thanks
Hari
"J1C" <just1coder@.yahoo.ca> wrote in message
news:1164670349.026026.226980@.l39g2000cwd.googlegr oups.com...
> Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> Is there a better way to schedule that outside of a maintenance plan ?
>
|||Hari Prasad wrote:[vbcol=seagreen]
> Hello,
> Why do you need DTS for this. All you have to do is:-
> 1. Open Enterprise Manager
> 2. Connect to SQL Server
> 3. Expand Management, Select Jobs and create new job.
> 4. In the job step give sp_updatestats and choose database
> 5. Provide a schedule to execute
> 6. Save the job
> Based on the schedule.. SQL Server agent will trigger this job
> Thanks
> Hari
> "J1C" <just1coder@.yahoo.ca> wrote in message
> news:1164670349.026026.226980@.l39g2000cwd.googlegr oups.com...
Thanks - that is what I ended up doing rather than DTS.

scheduled TRN backups failing (sql2000)

I have created a backup that does once weekly BAK and every night it does TRN backup. This is in the same maintaince plan, the jobs appear as seprate jobs as they should. I have noticed my TRN is always failing, after looking into the event logs i see this.

please note this is lastest time to early:

4:22pm
this is the warning that the event log gives:

SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan 'xxxxxxxx TRN'' (0xB87B2FA07E4FB74CA01A1D38134C9C4F) - Status: Failed - Invoked on: 2007-03-09 16:19:40 - Message: The job failed. The Job was invoked by User domain\Administrator. The last step to run was step 1 (Step 1).

the next is
4:22pm
18265 :
Log backed up: Database: Staging, creation date(time): 2007/01/30(09:35:34), first LSN: 24624:14008:1, last LSN: 24624:14021:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'f:\program files\microsoft sql server\MSSQL\BACKUP\Staging\Staging_tlog_200703091622.TRN'}).

last is 4:21pm
18264 :
Database backed up: Database: Staging, creation date(time): 2007/01/30(09:35:34), pages dumped: 93982, first LSN: 24624:14008:2, last LSN: 24624:14018:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'f:\program files\microsoft sql server\MSSQL\BACKUP\Staging\Staging_db_200703091618.BAK'}).

So for some very strange reason its running a full backup then a Transactional, for this reason i would say its failing but why is it even doing this backup? the job is only for TRN?

A manual TRN backup works like a treat

Thanks

BRAD

CHECK what is the recovery model of your database... make sure it is not Simple... If it is simple it is normal to have this behaviour

Madhu

|||

ran sp_helpdb all of my databases are at full recovery apart from the tmpdb and another system DB but these are not in the backup plan only user databases are.

any other ideas?

|||

never mind you were right there was the northwind database still active (by default set to simple) this is classed as a user DB.

Thanks

Brad

Scheduled Restore DB in EM?

Dear All,
We all know that we can schedule backup DB & Log in EM using Database Maintenance Plan.
Is there a way we can schedule Restore DB using EM?
Anyone?
Thanks.Yup ... write the sql code to do so and schedule as a job.|||Thanks Enigma... seems like that's the only option.

rgds|||I presume you will know better if you read thru BOL as a first hand help.|||Thanks Satya... your prevision is true.

I managed to get the job done... writing the script and scheduled as job.

Scheduled backups won't run

I have one of my SQL Server 2000 machines that will not run scheduled
backups either as a backup job or a maintenance plan. Running the backup by
hand works fine.
Any help is greatly appreciated.
Are you getting any errors? What id are you running this under?
-- Greg Smith wrote: --
I have one of my SQL Server 2000 machines that will not run scheduled
backups either as a backup job or a maintenance plan. Running the backup by
hand works fine.
Any help is greatly appreciated.

Scheduled backup silently fails

I am running a SQL Server 2000 installation with several databases. Each
database and log is backed-up using a maintenance plan.

The scheduled maintance plan for the latest database does not run, but
displays no error. There is no entry in the job history. The same thing
happens when I try to run the individual jobs from Enterprise Manager.

I've checked the database recovery model (full), the location of the backup
files (same as the other databases), and just about everything else I can
think of. The scheduled maintenance plan for every other database runs as
it should.

What am I missing?

Thanks

Iain"Iain Hosking" <iimfedupwithspamhosking@.thespamfreeweather.com.au> wrote in
message news:401e53e7$0$79389$7b628d20@.titanium.syd.ntt.ne t.au...
> I am running a SQL Server 2000 installation with several databases. Each
> database and log is backed-up using a maintenance plan.
> The scheduled maintance plan for the latest database does not run, but
> displays no error. There is no entry in the job history. The same thing
> happens when I try to run the individual jobs from Enterprise Manager.
> I've checked the database recovery model (full), the location of the
backup
> files (same as the other databases), and just about everything else I can
> think of. The scheduled maintenance plan for every other database runs as
> it should.
> What am I missing?

Is SQL Agent service running? This service is required
to be running for the above automation.

Additionally, I would disassociate the backups and the
maintenance plans by creating each as separate tasks,
the former being far more critical than the latter.

Pete Brown
Winluck P/L
Falls Creek
Australia|||Hi,

A wild guess is you're looking at the job history via EM. You're
right clicking on the sql agent jobs and select view history. The
view history says job successful. But when you check the view step
details, you see that some of the job steps failed?? If that is the
case you'll need to query the system tables. A script to do that is
located at http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=30388.|||Mountain Man

Thanks for the answer. Yes, SQL Server Agent is running. Every other
database is being backed up according to the plan.

I was hoping there was just one thing I missed with this database, but as I
say, I've checked the obvious (data recovery model, backup file names).

Do you advocate setting up a manual backup plan rather than using
Microsoft's Maintenance Plan wizard? The attraction of the wizard was that
it timestamped the files, and was basically quick to set up (there are 13
databases so far). I attended a 1-week DBA course and this seemed to be the
approved procedure. It's worked fine up to this point.

Cheers

Iain

"mountain man" <hobbit@.southern_seaweed.com.op> wrote in message
news:iGyTb.40024$Wa.4755@.news-server.bigpond.net.au...
> "Iain Hosking" <iimfedupwithspamhosking@.thespamfreeweather.com.au> wrote
in
> message news:401e53e7$0$79389$7b628d20@.titanium.syd.ntt.ne t.au...
> > I am running a SQL Server 2000 installation with several databases. Each
> > database and log is backed-up using a maintenance plan.
> > The scheduled maintance plan for the latest database does not run, but
> > displays no error. There is no entry in the job history. The same thing
> > happens when I try to run the individual jobs from Enterprise Manager.
> > I've checked the database recovery model (full), the location of the
> backup
> > files (same as the other databases), and just about everything else I
can
> > think of. The scheduled maintenance plan for every other database runs
as
> > it should.
> > What am I missing?
>
> Is SQL Agent service running? This service is required
> to be running for the above automation.
> Additionally, I would disassociate the backups and the
> maintenance plans by creating each as separate tasks,
> the former being far more critical than the latter.
>
>
> Pete Brown
> Winluck P/L
> Falls Creek
> Australia
>
>
>|||Iain Hosking (iimfedupwithspamhosking@.thespamfreeweather.com.au ) writes:
> I am running a SQL Server 2000 installation with several databases. Each
> database and log is backed-up using a maintenance plan.
> The scheduled maintance plan for the latest database does not run, but
> displays no error. There is no entry in the job history. The same thing
> happens when I try to run the individual jobs from Enterprise Manager.
> I've checked the database recovery model (full), the location of the
> backup files (same as the other databases), and just about everything
> else I can think of. The scheduled maintenance plan for every other
> database runs as it should.

Well, these may be really stupid suggestions, but check that the job
is enabled, and that the schedule is enabled.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||"Iain Hosking" <iimfedupwithspamhosking@.thespamfreeweather.com.au> wrote in
message news:401ed1e6$0$79387$7b628d20@.titanium.syd.ntt.ne t.au...

...[trim]...

> Do you advocate setting up a manual backup plan rather than using
> Microsoft's Maintenance Plan wizard?

Generally yes, for a number of reasons:

1) Although the maintenance tasks can be very important
the backup is super-critical and should have IMO a dedicated
separate task in the production task queue.

2) Generally the schedules for maintenance and backups
are different cycles and thus they need to separately scheduled.

OTOH the maintenance wizard is fine for most production
sites in their early phases of operations -- prior to any
full automation. (ie: large task queue)

Good luck,

Pete Brown
Falls Creek
Australia

> "mountain man" <hobbit@.southern_seaweed.com.op> wrote in message
> news:iGyTb.40024$Wa.4755@.news-server.bigpond.net.au...
> > "Iain Hosking" <iimfedupwithspamhosking@.thespamfreeweather.com.au> wrote
> in
> > message news:401e53e7$0$79389$7b628d20@.titanium.syd.ntt.ne t.au...
> > > I am running a SQL Server 2000 installation with several databases.
Each
> > > database and log is backed-up using a maintenance plan.
> > > > The scheduled maintance plan for the latest database does not run, but
> > > displays no error. There is no entry in the job history. The same
thing
> > > happens when I try to run the individual jobs from Enterprise Manager.
> > > > I've checked the database recovery model (full), the location of the
> > backup
> > > files (same as the other databases), and just about everything else I
> can
> > > think of. The scheduled maintenance plan for every other database
runs
> as
> > > it should.
> > > > What am I missing?
> > Is SQL Agent service running? This service is required
> > to be running for the above automation.
> > Additionally, I would disassociate the backups and the
> > maintenance plans by creating each as separate tasks,
> > the former being far more critical than the latter.
> > Pete Brown
> > Winluck P/L
> > Falls Creek
> > Australia|||What user is SQL Server running under?
What user is SQL Agent running under?
Who is the owner of the database?
Are all of the above the same?
If not, check the other databases for this information and change this
one to match.
If so, does the user have permissions at the location of the backup
files?

On Tue, 3 Feb 2004 00:42:59 +1100, "Iain Hosking"
<iimfedupwithspamhosking@.thespamfreeweather.com.au> wrote:

>I am running a SQL Server 2000 installation with several databases. Each
>database and log is backed-up using a maintenance plan.
>The scheduled maintance plan for the latest database does not run, but
>displays no error. There is no entry in the job history. The same thing
>happens when I try to run the individual jobs from Enterprise Manager.
>I've checked the database recovery model (full), the location of the backup
>files (same as the other databases), and just about everything else I can
>think of. The scheduled maintenance plan for every other database runs as
>it should.
>What am I missing?
>Thanks
>Iain

Schedule backup SQL Server 2000

Hi all,

How can I schedule backup in SQL Server 2000 for ALL databases?
With SQL Server 2005 I can create maintenance plan to do this,
but in the 2000 version I don′t know.

thanks!!!!You can do the same thing in SQL Server 2000. Create a new maintenance plan, select All databases, specify backup options and a schedule, complete the wizard. It will create a job that will backup all of the databases using the options that you specified.|||

Have you tried one of the many different online backup solutions for sql server? there's one from

4backuponline.com that works with sql server and it has been working beatiful for me for that last couple of months. You set it up once and you can forget about it.|||

An advice though, if you'll use 3rd party backup software for SQL Server, better choose a tool that performs the backup via execution of T-SQL queries.

It is a more durable solution

Schedule backup SQL Server 2000

Hi all,

How can I schedule backup in SQL Server 2000 for ALL databases?
With SQL Server 2005 I can create maintenance plan to do this,
but in the 2000 version I don′t know.

thanks!!!!You can do the same thing in SQL Server 2000. Create a new maintenance plan, select All databases, specify backup options and a schedule, complete the wizard. It will create a job that will backup all of the databases using the options that you specified.|||

Have you tried one of the many different online backup solutions for sql server? there's one from

4backuponline.com that works with sql server and it has been working beatiful for me for that last couple of months. You set it up once and you can forget about it.|||

An advice though, if you'll use 3rd party backup software for SQL Server, better choose a tool that performs the backup via execution of T-SQL queries.

It is a more durable solution

Schedule backup SQL Server 2000

Hi all,

How can I schedule backup in SQL Server 2000 for ALL databases?
With SQL Server 2005 I can create maintenance plan to do this,
but in the 2000 version I don′t know.

thanks!!!!You can do the same thing in SQL Server 2000. Create a new maintenance plan, select All databases, specify backup options and a schedule, complete the wizard. It will create a job that will backup all of the databases using the options that you specified.|||

Have you tried one of the many different online backup solutions for sql server? there's one from

4backuponline.com that works with sql server and it has been working beatiful for me for that last couple of months. You set it up once and you can forget about it.|||

An advice though, if you'll use 3rd party backup software for SQL Server, better choose a tool that performs the backup via execution of T-SQL queries.

It is a more durable solution