i have tried to script the user rights the login has and couldnt find anything with DENY ...so I am pretty sure that there are no Deny access for the...

The user is already a member of the listed roles.

I tried that ...the user is using windows authetiaction and tried giving the user all the SQL operator roles....doesnt seem to work....

In the link for schedules it say...

I did....but it doesnt seeem to work....

I beleive the roles are the 'Jobs owned by the user only'. I need the user to be able to change the schedule for...

Not exactly. I want to know how the database was used in the recent time , the kind of updates that were done on various tables ......so I was...

There are few clustered indexes and heap present on the db....

I have also tried the follwing code to rebuild all the indexes in the db ...

DECLARE @TableName varchar(255)

DECLARE @cmd NVARCHAR(500)

DECLARE @fillfactor INT

SET @fillfactor = 90

DECLARE TableCursor CURSOR...

Thanks for your suggestion , I will try that out.

Earlier we had a maintennace plan that we had some issues with ...so I created this new maintenance plan with a step to execute a SQL serer job and...

Ther are many index present in the db....

here is a fraction of result :

538968053601HEAPIN_ROW_DATA1095.88235294117651684.39880952380952739NULLNULLNULLNULLNULLNULLNULLNULL

542720062201HEAPIN_ROW_DATA1092.5925925925926275.85185185185185158NULLNULLNULLNULLNULLNULLNULLNULL

Thanks for the reply......

I might try taking the db to Bul logged and perform th erebuild of the indexes and then get it back to Full recovery model.

Hope everything goes...

thank for the link......

I am not sure if I understand this correctly...

I have a fulll backup taken before rebuilding of the indexes.

Index rebuild job runs.

A full backup scheduled to run...

In my case the full backup failed yesterdy night and I had the full backup taken this morning.....

So will I not be able to restored the transactional log backups along...

I have a job that takes transactional log backup every 15 mins....for example the last step when the db had to be taken to full recovery model ran 7:02 PM...

No more information was present in the log apart from the failure of the Jobs. Anything else that needs to be looked into?