Recent content by olahallengren

It's not so complicated. Please contact me if you need any help. http://blog.ola.hallengren.com/About.html Ola Hallengren http://ola.hallengren.com

I know that Service Pack 2 fixes a number of bugs related to the Maintenance Plans, but I don't know about this one specifically. If you're interested I have a stored procedure based maintenance solution that you're welcome to use...

Unfortunately SQL Server Express doesn't have the Maintenance Plans. I have a set of maintenance stored procedures that you're welcome to use. http://blog.ola.hallengren.com/blog/_archives/2008/1/1/3440068.html Ola Hallengren http://ola.hallengren.com

What you could do is to perform your local backups with the option COPY_ONLY. This way you're not affecting the managed backup solution. http://msdn.microsoft.com/en-us/library/ms186865.aspx I do not believe that the Maintenance Plans have support for the COPY_ONLY option, so you need to use a...

I have a stored procedure based maintenance solution that you are welcome to use. http://blog.ola.hallengren.com/blog/_archives/2008/1/1/3440068.html Ola Hallengren http://ola.hallengren.com

I'm not sure what setting it is that you've changed. I do not know of any setting to control how long the SQL Server Agent Jobs are allowed to run. One approach that some people are using is to create a special monitor job that keeps track of the other jobs. Another approach that could be...

Another backup strategy could be to create unique file names (with date and time) for each backup. This could be done with the Maintenance Plans or with T-SQL scripts. I have a stored procedure that you could use that supports this backup strategy...

I agree that creating multiple tempdb data files is a best practise. Another thing that you should consider is Instant File Initialization. http://msdn.microsoft.com/en-us/library/ms175935.aspx Kimberly Trip has a blog post about this...

I think that your plan looks about right. Just a few things. The database should have the same name on the two servers, when you establish database mirroring. I think that log backups normally have the .trn file extension. Ola Hallengren http://ola.hallengren.com

>So I'm thinking of trying to create a stored procedure to perform the maintenance tasks and schedule a job to run on a weekly basis. I have made a stored procedure based maintenance solution that does backup, integrity check and index optimization...

You can establish database mirroring with the database online and with updating users all the time. The transactions since the last log backup are transferred to the mirror server after you issue the SET PARTNER command (the status changes from Synchronizing to Synchronized). Ola Hallengren...

Thanks, ESquared. Please feel free to contact me directly if you have any questions about my solution. http://blog.ola.hallengren.com/About.html Ola Hallengren http://ola.hallengren.com

>Thanks a bunch for your help. Things are looking a lot better now. (And I'm going to fix the reindex job I had going.) With a database of this size you could save a lot of resources, if you only do something about the indexes with fragmentation. You could also do a reorganize instead of a...

If you're on SQL Server 2005 you could check the index fragmentation levels with sys.dm_db_index_physical_stats. This way you only have to do something about the indexes with a high fragmentation level. You could also dynamically do a rebuild or a reorganize based on the fragmentation level. I...

I think that you should contact MS Support. You should not need a trace flag to run database mirroring with SP2. Ola Hallengren http://ola.hallengren.com