Database Maintenance Plan

I used the Database Maintenance Plan Wizard,
I have scheduled it once a day at a certain time.
And nothing happen. No program run at that time.
Is there something else to do to run the plan ?
And is it possible to run it immediatly ?
Thanks for help.
Pierre.The problem comes from a Loggin failure.

I am very confused with all these loggin !

My SQLdatabase have SQL login (not window).

When I run the SQL job, it takes my window login.

What should I do to be coherent.
(SQLserver 2000, and Windows 2000)

Thanks, Pierre.|||First of all check from EM --> Management --> JObs and specified job is enabled or not.

And use Local or domain account with admin privileges for SQL services account.

Try to execute the job manually and see the results.|||Ok, my problem is that I do not understand well Windows2000.

I understand that a User belong to a group.
And this group have priviledges.

But I do not see where to modify the group properties for assigning rights (priviledges).

Thanks for any help, if possible.|||On Win2K from Administrative tools --> Services and select MSSQLSErver & MSSqlAgent to add this user from that group/domain.

Restart the service to take the effect.|||I add the user I use to loggin Windows2000.
(MSSQLSERVER Service properties : Log On)

I restart the Server and run the job.
But the SQL job did fail again.

database log file size

I want to ask what are the impacts if I limit the file size to certain MBs and will it report (File is full) or overwrite old data when the file reachs the assigned size?

you have to configure an alert (several MB) before log gets full.

when the log gets full no change in the database shall be committed.

|||

but is it true that SQL Server will be faster if the allocated size for the log file was larger?

|||

Jassim,

Perhaps you are referring to an auto grow capability of data and log files. By default database files are created with auto grow option. Each time a file reaches it's full capacity it gets resized, by the specified amount (either fixed size or percentage). This operation has some negative impact on the database performance, so in general it should be avoided. The autogrow functionality is primarly useful in systems that are not closely monitored by an adminstrator, for example embedded applications.

So if you set the initial log size to be bigger, you avoid growing the log file on demand. You can monitor for the auto grow of log and data files using SQL Profiler by selecting Log File Auto Grow and Data File Auto Grow events.

Hope that helps.

Regards,

database log file size

I want to ask what are the impacts if I limit the file size to certain MBs and will it report (File is full) or overwrite old data when the file reachs the assigned size?

you have to configure an alert (several MB) before log gets full.

when the log gets full no change in the database shall be committed.

|||

but is it true that SQL Server will be faster if the allocated size for the log file was larger?

|||

Jassim,

Perhaps you are referring to an auto grow capability of data and log files. By default database files are created with auto grow option. Each time a file reaches it's full capacity it gets resized, by the specified amount (either fixed size or percentage). This operation has some negative impact on the database performance, so in general it should be avoided. The autogrow functionality is primarly useful in systems that are not closely monitored by an adminstrator, for example embedded applications.

So if you set the initial log size to be bigger, you avoid growing the log file on demand. You can monitor for the auto grow of log and data files using SQL Profiler by selecting Log File Auto Grow and Data File Auto Grow events.

Hope that helps.

Regards,