Hi Ola,

Thanks for your support. If someone else find a solution, would you like to
know it ??

Bye.

André



"Ola Hallengren" wrote:

> I'm sorry, but I don't know how to solve this problem.
>
> Ola Hallengren
> http://ola.hallengren.com
>
>
>
> "inf0m286" wrote:
>
> > Hi Ola,
> >
> > I created two simple job (one on each instance) that executedd a DOS command
> > and on the default instance, noting was updated and in the new instance, all
> > is right.
> >
> > I also make a test on a virtual machine with 2 instances and i have the same
> > problem
> >
> > Thanks
> >
> > "Ola Hallengren" wrote:
> >
> > > Did you do this test on the instance where you have the problem?
> > >
> > > What if you just create a simple sql server agent tsql job and execute that?
> > >
> > > /Ola
> > >
> > >
> > >
> > >
> > > "inf0m286" wrote:
> > >
> > > > Hi Ola,
> > > >
> > > > I know that i can take a backup online of each database and take these
> > > > databases for the backup. But, some of the jobs that was not update are the
> > > > maintenance plan that was created by the Database Maintenance plan wizard.And
> > > > that these jobs was running well before 2008-03-13 and also some job that we
> > > > created. The data
> > > >
> > > > The only thing that was made on the server is the add of another instance of
> > > > SQL. That installation was made in mid-february and nothing was wrong with
> > > > that. The problem is coming up when i detached one database of the first
> > > > instance and move it on the second one. And i created a maintenance plan for
> > > > the new instance and the status is OK
> > > >
> > > > It's really a strange error.
> > > >
> > > > Thanks.
> > > >
> > > >
> > > > "Ola Hallengren" wrote:
> > > >
> > > > > I think that you should edit this batch file so that you don't stop and start
> > > > > the sql server and sql server agent services.
> > > > >
> > > > > Instead you should add some sqlcmd commands to the batch file that performs
> > > > > that sql backups.
> > > > >
> > > > > sqlcmd -E -S Server1\Instance1 -d master -Q "BACKUP DATABASE master TO DISK
> > > > > = 'C:\master.bak'" -b
> > > > >
> > > > > If you would like to have a more dynamic solution you could use a solution
> > > > > that I have made for this.
> > > > > http://blog.ola.hallengren.com/blog/...1/3440068.html
> > > > >
> > > > > Ola Hallengren
> > > > > http://ola.hallengren.com
> > > > >
> > > > >
> > > > >
> > > > > "inf0m286" wrote:
> > > > >
> > > > > > A job for the tivoli server is scheduled and a we can run a pre-backup and
> > > > > > post-backup set. In the pre-backup step, a batch file is running In that
> > > > > > batch file, some services (SQL Server and SQL Server agent) is stopped (by
> > > > > > the dos command net stop). After that, the backup was taken and the services
> > > > > > is restarted.
> > > > > >
> > > > > > I can take a backup while the database is online. i have make a tets with
> > > > > > SQL Query Analyzer.
> > > > > >
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > > André
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > "Ola Hallengren" wrote:
> > > > > >
> > > > > > > >At each night, an automated backup is schedule and i stop/start sql server
> > > > > > > during that task.
> > > > > > >
> > > > > > > Could you give me some more information about how this is working. Is this a
> > > > > > > sql server agent job?
> > > > > > >
> > > > > > > Could you also give me some background for this backup strategy. In sql
> > > > > > > server it is possible to backup a database with the BACKUP DATABASE command
> > > > > > > while it is online.
> > > > > > >
> > > > > > > >I have a lot of jobs that was schedule in SQL Server Agent and since 2008-03-13 the status won't be update
> > > > > > >
> > > > > > > What if you just create a simple sql server agent tsql job and execute that?
> > > > > > >
> > > > > > > /Ola
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > "inf0m286" wrote:
> > > > > > >
> > > > > > > > Hi Ola,
> > > > > > > >
> > > > > > > > I see no error in the server and agent log file. But, there is something
> > > > > > > > strange. At each night, an automated backup is schedule and i stop/start sql
> > > > > > > > server during that task. Normally, it create a new SQL log file and it's not
> > > > > > > > doing that since 03/17 .
> > > > > > > >
> > > > > > > > For the account that own SQL Server and Agent, it is the local system
> > > > > > > > account (in the definition on these services), so i think it has sysadmin
> > > > > > > > rights .
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > >
> > > > > > > > "Ola Hallengren" wrote:
> > > > > > > >
> > > > > > > > > You have no error messages in the sql server or sql server agent log file?
> > > > > > > > >
> > > > > > > > > Does the sql server agent service account have sysadmin rights?
> > > > > > > > >
> > > > > > > > > Ola Hallengren
> > > > > > > > > http://ola.hallengren.com
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > "inf0m286" wrote:
> > > > > > > > >
> > > > > > > > > > Hi,
> > > > > > > > > >
> > > > > > > > > > I have a lot of jobs that was schedule in SQL Server Agent and since
> > > > > > > > > > 2008-03-13, the status won't be update. But, i know that the job still
> > > > > > > > > > running well. But the status of the next run date was OK.
> > > > > > > > > >
> > > > > > > > > > I have search on the web and i don't see anything that can me.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > SQL2000 Standard Edition (two instance) (SP4)
> > > > > > > > > > Windows 2003 Server
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >