August 19, 2008 at 8:13 am
Backup can not be performed on this database. This sub task is ignored. I get this error message when my Transaction log is running for master DB. Master is set up to Full recovery.Can anyone help me
August 19, 2008 at 9:21 am
Master uses the simple recovery model by default and, even if you change the recovery model, you can't take or restore log backkups. See this in KB:
http://support.microsoft.com/kb/285288/en-us?FR=1
Greg
August 19, 2008 at 9:37 am
Thank you
September 17, 2008 at 10:28 am
I am new with DBA work, I was giving a server which contains no optimization,transaction logs, no integrity, no full back to be set up on schedule jobs. I was told that full backup is done thought NT exec command. I don't know what I need to start a maintance.What do I need to do, please help.Thank you
September 17, 2008 at 12:50 pm
I use the maintenance plan wizard (I know some people don't like MP). Obviously, the first thing to do is schedule full backups. Once you have that going, determine which are in "Full" recovery mode and schedule log backups at appropriate intervals to keep log growth to a minimum. Next, I'd determine where I have a maintenance window (are you 24 X 7 or can you schedule time on the weekend?) and run DBCC CheckDb on all production databases, at a minimum. Be sure you have good data so that backups actually have value in the event of failure. Then look at another window to rebuild your indexes on each of your production databases. There are scripts available EVERYWHERE on the web if you want to simply rebuild the ones that have reached a certain level of fragmentation (this'll potenetially shorten the maintenance window for this task). Maintenance jobs should be done maybe once a week. Backups, obviously, as often as necessary to cover business requirements. Check out the link below, it's kind of a "getting started" list.
http://blogs.mssqltips.com/forums/p/443/610.aspx#610
-- You can't be late until you show up.
September 19, 2008 at 8:00 am
Thank you, I will try to that. Also in the servers that my company have in the sql server agent have no maintentace, I found out that NT administrator does through Backup Exec. What is better to do like this and not to bother setting up jobs in SQL server? Please advise.
September 19, 2008 at 8:16 am
My company uses Backup Exec and I dislike it. It was in place when I started and they will not change it. It works fine but for restore purposes, it takes way too long for me. If it's on disk, you can restore much quicker that trying to catalog a tape or recalling it from offsite storage and then restoring. I have created a couple of jobs to backup business-critical databases to disk on a nightly basis. It gives me added peace of mind knowing I can respond quickly in the event of failure.
-- You can't be late until you show up.
September 19, 2008 at 10:11 am
Terry, I get Demo: Full msdb log and temp log alerts. do you know how I can fix it?
September 19, 2008 at 11:32 am
Thos are demo alerts that come with the insatll of SQL. Did you actually get an alert? msdb, by default, is set to simple recovery mode. Tempdb is you workhorse. That would be the one that I'd be concerned with. Do you have any maintenance jobs running? How big is your tempdb to begin with? To disable the alerts (personally I wouldn't) go into Enterprise Manager, select you server then go to Management->Sql Server Agent->Alerts. Double-click on the alerts and disable them. Again, let's take a look at tempdb first and go from there.
-- You can't be late until you show up.
September 19, 2008 at 12:00 pm
There is one server contains maintance job and temp is 9MB and 7MB is available. There is another server that contains no maintnance job and temp is 213.13MB and 209 is available. Thank you
September 19, 2008 at 12:10 pm
When the maintenance job runs it'll use tempdb. 9 Mb (and even 213 Mb) seems awful small for a tempdb. Mine average 5Gb. I guess it depends on your server and data load though. If you can increase the size, I would. Start with maybe 500Mb if free disk space is available.
-- You can't be late until you show up.
September 19, 2008 at 12:38 pm
There is one server contains no maintance job and temp is 9MB and server has 3583 memory , change temp to 500MB? and there is another server that contains maintnance job and temp is 213.13MB and server 255MB , do I change to 500MB too? Thank you
September 19, 2008 at 12:39 pm
Can I change memory to temp db anytime?
September 19, 2008 at 12:49 pm
yulichka (9/19/2008)
There is one server contains no maintance job and temp is 9MB and server has 3583 memory , change temp to 500MB? and there is another server that contains maintnance job and temp is 213.13MB and server 255MB , do I change to 500MB too? Thank you
Not sure what your trying to explain. What do you mean by "3583 memory"? Is that free disk space? That's what you need to quiet the alert you were receiving, not memory. As for the other server, if you only have 255MB of free disk space, you can't increase it to 500Mb. Again, my reply was a suggestion. If disk space is available AND if your load is high, I would increase tempdb - again, IMO 9Mb is way too small. It's really based on your company needs.
Edit - I just saw your other reply. Yes, you can change memory at anytime but it's allocated to SQL server, not to a database.
-- You can't be late until you show up.
September 19, 2008 at 1:12 pm
3583MB it is a memory to the system.Thank you for your help, I will increse from 9mb temp to 500mb. My question is can I change a temp that is contains 213.13MB and memory to operation server 255MB , do I change to 500MB too? Thank you
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply