Change SharePoint_Config Database to simple recovery mode. Risk.

Hello,
we have SBS 2008 with Exchnage and OWA-Service.
The Logfile of SharePoint is very large (30 GB).
But we don't use SharePoint.
I want to change the recovery mode of SharePoint_Config Database to simple.
But i don't know, what of Application/Services/Programms use SharePoint Database.
What are the risks of changing SharePoint_Config Database to Simple Mode?
What of the Sevices/Programms use SharePoint Database ?
Thank You

Hi ,
As Dimitri pointed out, SharePoint DB is in SQL database, the change of it won't affect Exchange and Outlook Web Access.
If you use SharePoint in future, you may take a look at the following article about the effect to SharePoint database with simple recovery mode.
http://searchwinit.techtarget.com/tip/How-SQL-Server-recovery-models-impact-your-SharePoint-databases
Thanks
Daniel Yang
TechNet Community Support

Similar Messages

What is impact to MDF file size if change database to simple recovery mode

Hi,
Currently I have a Database with 27GB MDF and 80GB LDF.
If I change from Full recovery to Simple recovery mode, would LDF information be transfered to MDF file and make
MDF file size exceed 100GB?

Hi
May I know how to perform point in time recovery? Currently the only backup we perform every 4 hours is the server OS snapshot.
Example :
1. Now is 6pm and some error transaction occurred.
2. We can perform 3pm server OS snapshot recovery on the mdf file. ( We would lost 3 hours data in this case )
3. Could we apply the ldf transaction log after OS snapshot recovery and roll it forward till 5:50pm?
You would be able to perform point in time recovery if you have
1. Database configured in full recovery mode
2. You were taking transaction log backups.(of course with full backup or may be differential)
In your scenario applying snapshot wont help you.What you have to do it you should have full backup in place .If you had full backup ,like full backup at 3 PM then you would have restored it with no recovery.After that suppose you took tansaction log backups
every on hour then restore 1 PM ,2 PM and 3 PM log backup all in nore covery.
Now i should have mentioned first but before restoring full backup you can also take tail log backup read this article
http://technet.microsoft.com/en-us/library/ms179314.aspx
So now after full and all log backups are applied with no recobery apply tail log backup with recovery and its quite possible that you might not have a data loss or in some scenario very small data loss( not 3 hrs as you would have with snapshot)
hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Simple recovery mode

Hi,
I have a question..
My production database is in full recovery mode and we have daily full backups and t-log backups after every 10 minutes.
Suppose if I set the database in simple recovery mode for some reason, do the old full backups and t-log backups are of no use after setting the db in simple recovery mode. can I use these backups to go back in time.
Regards

Assume the following chain of events:
A: Full backup
B: Log backup
C: Switch to simple reocvery
D: Full backup
E: Log backup
F: Switch back to full recovery.
G: Log backup
H: Full backup
I: Log backup
You will be able to restore to any point in time up to C. You will also be able to restore to any point in time from H and on - but only if the full backup at H is good. The log backups at point E and G will fail, since you cannot take log backups in simple
recovery. And the database remains in simple recovery until you have taken a full backup.
Erland Sommarskog, SQL Server MVP, [email protected]
Erland,
After you switch to simple recovery how is log backup E possible. Again how is log backup G possible after you switch to full recovery and dont take full backup ?
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

If db is in simple recovery mode can we identify who deleted the login id?

if db is in simple recovery mode can we identify who deleted the login id?

You can take a look in the default trace to find who dropped it. If you are lucky enough.
The database being in simple recovery mode has nothing to do with it. Even in full recovery mode this is not going to be seperately logged.
SELECT TE.name AS [EventName] ,
v.subclass_name ,
T.DatabaseName ,
t.DatabaseID ,
t.NTDomainName ,
t.ApplicationName ,
t.LoginName ,
t.SPID ,
t.StartTime ,
t.RoleName ,
t.TargetUserName ,
t.TargetLoginName ,
t.SessionLoginName
FROM sys.fn_trace_gettable(CONVERT(VARCHAR(150), ( SELECT TOP 1
f.[value]
FROM sys.fn_trace_getinfo(NULL) f
WHERE f.property = 2
)), DEFAULT) T
JOIN sys.trace_events TE ON T.EventClass = TE.trace_event_id
JOIN sys.trace_subclass_values v ON v.trace_event_id = TE.trace_event_id
AND v.subclass_value = t.EventSubClass
WHERE te.name IN ( 'Audit Addlogin Event', 'Audit Add DB User Event',
'Audit Add Member to DB Role Event' )
AND v.subclass_name IN ( 'Drop', 'Revoke database access' )
https://www.simple-talk.com/sql/performance/the-default-trace-in-sql-server---the-power-of-performance-and-security-auditing/
This query is only going to check the last trace file and by default you have four others, putting path instead of the subquery to find the trace path will also work.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

If your database in Full Recovery mode, can you use Bulk Insert Task to load data

If your database in Full Recovery mode, can you use Bulk Insert Task to load data

If your database in Full Recovery mode, can you use Bulk Insert Task to load data
Yes you can ofourse but dont be in idea that logging will be mininal. Loggign will be as per recovery model full. Every thing will be logged. If you are going to use bulk insert task you can consider switching recovery model to Bulk logged but you will not
have option to do point in time recovery.
PS: please dont create duplicate threads
If you read first Note section in below link it clearly states that yes logging will be full and you can use
http://technet.microsoft.com/en-us/library/ms191244(v=sql.105).aspx
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Errors while Changing the Database to Mutli User Mode from Single user mode in SQL Server 2012

Hi,
Good Afternoon :). Need your help in resolving one of the issue with SQL Server 2012.
Today, we kept one of the database in the Single User mode and wanted to bring back to Multi User mode. But we are getting the below error. There are no user sessions connected to this database which are blocking each other. I see multiple
SYSTEM sessions are in blocked state.  The blocking is not cleared even affter restarting the SQL services.
Verified the SQL Server Errorlog and couldnt get much useful information to troubleshoot the issue.
pasted the information from the sys.sysprocesses as well for your kind reference.
Msg 1205, Level 13, State 68, Line 1
Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
spid
kpid
blocked
waittype
waittime
dbid
login_time
status
cmd
18
1004
36
0x0005
144
5
4/9/2014 13:13
background
TASK MANAGER
35
1796
36
0x0005
35
5
4/9/2014 13:34
background
TASK MANAGER
36
2464
37
0x0005
363
5
4/9/2014 13:34
background
TASK MANAGER
37
5100
36
0x0005
254
5
4/9/2014 13:04
background
TASK MANAGER

Clearly 36 and 37 are causing deadlock.
see
https://www.simple-talk.com/sql/database-administration/handling-deadlocks-in-sql-server/
http://www.mssqltips.com/sqlservertip/1036/finding-and-troubleshooting-sql-server-deadlocks/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SharePoint_Config database

We recently switched the SharePoint_Config database to Simple recovery model to control the transaction logs. However, the ldf file still gets larger than the actual database file(mdf).
I have researched some of the autogrowth/pre-sizing settings, and I just don't understand it for the log portion. Right now, they are just set to the default SQL Server settings.
Does anyone have any suggestions as to what I can do to keep the transaction log smaller than the database files or at least relatively small?
I have checked, and I do not have any active transactions at the moment.
Thanks!

It is still growing. Yesterday, it was at 51MB and now it is at 110MB(which I know is not much compared to others, but we really rely on the server that SharePoint is on), so I am guessing it grows after the database backup(@10:15pm), and then the growth
doesn't change much throughout the day since I am the only one using it for development.
Yes, it may be completely normal, but I just don't want it to continue to grow 50MB+ every night, if it is not normal.
I no longer truncate the logs every night since it is in Simple recovery. Should I still be doing that?
I tried to find out through internet research if I still needed to, but everyone was saying that Simple recovery takes care of the truncation when the file gets a certain size. Well is there a way to check the size that the auto truncation will take place?

Shrink Log file in log shipping and change the database state from Standby to No recovery mode

Hello all,
I have configured sql server 2008 R2 log shipping for some databases and I have two issues:
can I shrink the log file for these databases: If I change the primary database from full to simple and shrink the log file then change it back to full recovery mode the log shipping will fail, I've seen some answers talked about using "No
Truncate" option, but as I know this option will not affect the log file and it will shrink the data file only.
I also can't create maintenance to reconfigure the log shipping every time I want to shrink the log file because the database size is huge and it will take time to restore in the DR site, so the reconfiguration
is not an option :(
how can I change the secondary database state from Standby to No recovery mode? I tried to change it from the wizard and wait until the next restore for the transaction log backup, but the job failed and the error was: "the step failed". I need
to do this to change the mdf and ldf file location for the secondary databases.
can any one help?
Thanks in advance,
Faris ALMasri
Database Administrator

1. can I shrink the log file for these databases: If I change the primary database from full to simple and shrink the log file then change it back to full recovery mode the log shipping will fail, I've seen some answers talked about using "No Truncate"
option, but as I know this option will not affect the log file and it will shrink the data file only.
I also can't create maintenance to reconfigure the log shipping every time I want to shrink the log file because the database size is huge
and it will take time to restore in the DR site, so the reconfiguration is not an option :(
2. how can I change the secondary database state from Standby to No recovery mode? I tried to change it from the wizard and wait until the next restore for the transaction log backup, but the job failed and the error was: "the step failed". I need to do
this to change the mdf and ldf file location for the secondary databases.
can any one help?
Thanks in advance,
Faris ALMasri
Database Administrator
1. If you change recovery model of database in logshipping to simple and back to full Logshipping will break and logs wont be resored on Secondary server as log chain will be broken.You can shrink log file of primary database but why would you need that
what is schedule of log backup. Frequent log backup is already taking care of log files why to shrink it and create performance load on system when log file will ultimately grow and since because instant file initilaization is not for Log files it takes time
to grow and thus slows performace.
You said you want to shrink as Database size is huge is it huge or does it have lots of free space. dont worry about data file free space it will eventually be utilized by SQL server when more data comes
2. You are following wrong method changing state to no recovery would not even allow you to run select queries which you can run in Standby mode. Please refer below link to move Secondary data and log files
http://www.mssqltips.com/sqlservertip/2836/steps-to-move-sql-server-log-shipping-secondary-database-files/
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

SP 2013 - Database Recovery Mode When Using SQL Server Mirroring

Hello Community,
Our DBA is configuring a High Availability Architecture for our SharePoint 2013 Farm. Essentially he is using SQL Server Database mirroring with a clustered automatic failover using a witness server. He has informed me that mirroring requires
that the databases are set to Full Recovery Mode, but that several of the databases are set to Simple Recovery Mode, the databases are the following:
SearchService_DB
SearchService_DB_CrawlStore
SearchService_DB_AnalyticsReportingStore
SearchService_DB_LinksStore
WSS_UsageApplication
User_Profile_DB
User_Sync_DB
User_Social_DB
However, when I checked the following article -
http://technet.microsoft.com/en-us/library/cc678868.aspx - I see that Simple Recovery Mode is the default configuration for these databases. So, finally, here is my question - will it be detrimental to these databases to set them to the Full Recovery
Mode?
Thanks!
Tom
Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award -
Linked-In - SharePoint Gypsy

This really depends on your recovery objectives. The main reason for taking log backups, aside from truncating the log, is to be able to recover to a specific point-in-time. This is very helpful in mission-critical, highly transactional systems. I have not
seen a SharePoint environment require a point-in-time restore of the content or application service database. So for this case, you can overwrite the LDF bakups. Just make sure that you can recover your databases appropriately and meet your recovery objectives
on the farm level.
As far as the log file growth is concerned, you are correct. If you cap the size of your LDF file to let's say 10 GB, regular log backups will truncate the log, thereby, having space for additional transaction log records. The only risk here is when your
log backups are not frequent enough that the LDF file fills up before the next log backup runs to truncate the log. You run the risk of your database behaving as read-only and that will affect the site collections/applications using those databases
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Why is the transaction log file not truncated though its simple recovery model?

My database is simple recovery model and when I view the free space in log file it shows 99%. Why doesn't my log file truncate the committed
data automatically to free space in ldf file? When I shrink it does shrink. Please advice.
mayooran99

My database is simple recovery model and when I view the free space in log file it shows 99%. Why doesn't my log file truncate the committed
data automatically to free space in ldf file? When I shrink it does shrink. Please advice.
mayooran99
If log records were never deleted(truncated) from the transaction log it wont show as 99% free.Simple recoveyr model
Log truncation automatically frees space in the logical log for reuse by the transaction log and thats what you are seeing. Truncation wont change file size. It more like
log clearing, marking
parts of the log free for reuse.
As you said "When I shrink it does shrink" I dont see any issues here. Log truncation and shrink file is 2 different things.
Please read below link for understanding "Transaction log Truncate vs Shrink"
http://blog.sqlxdetails.com/transaction-log-truncate-why-it-didnt-shrink-my-log/

Simple recovery

Hi All,
Its very basic question for my understanding I have try to learn my self but need some important and Perfect information request to you every body please answer the below.
In Simple recovery why does not allow transaction log backups and why does not support point-in-time recovery.
Kindly provide valuable information
subu

To add a little more to the above point illustrated, a database in
Simple Recovery model is usually in Auto-Truncate mode which means log truncation can usually occur immediately after upon
checkpoint in performing in a making of space available for reuse.
read here more about checkpoint
http://msdn.microsoft.com/en-gb/library/ms189573.aspx
…to explain it in other word SQL Server usually flushes cached dirty pages to disk after first writing the transaction details and after this process what it does is immediately truncates
(remove the data from the log to make space without reducing the size) any
VLF that are no longer active (internally SQL Server breaks a transaction log file down into sub-files which is called Virtual Log Files (VLFs)) so in this truncation process the space that are freed can be used to store new log records.
Therefore simple recovery model keeps the transaction log records only till the next checkpoint process happens because of this reason SQL will not allow us to perform transaction
log backup in simple recovery model because the transaction log is not retained in simple recovery and the main reason taking transaction log is for DR reason.
So that’s the reason why log backups are simply meaningless for simple recovery model databases since it’s on auto-truncate and we are not able to use the contents of the log to restore the
database to a state of failure or point in time.
So to sum up Transactional replication, log shipping, or data mirroring is not allowed in the simple recovery model since their life basically relay on transaction log and simple recovery
is their enemy in truncating their log every checkpoint.
I hope this helps
Please remember to click “Mark as Answer” on the post that has answered your question as it is very relevant to other community members dealing with same problem in seeking the right answer.

Standby recovery mode

hi all,
how we can find that standby database is in recovery mode using a query.
when i checked status it is shown mount. but not sure it is in recovery mode or not.
please let me know.
thanks

Hi.
More info...
The physical standby database uses several processes to achieve the automation necessary for disaster recovery and high availability. On the standby database, log apply services use the following processes:
Remote file server (RFS)
The remote file server (RFS) process receives redo logs from the primary database either in the form of archived redo logs or standby redo logs.
Archiver (ARCn)
If standby redo logs are being used, the ARCn process archives the standby redo logs that are to be applied by the managed recovery process (MRP).
Managed recovery process (MRP)
The managed recovery process (MRP) applies information from the archived redo logs or standby redo logs to the standby database.
Log apply services, in coordination with log transport services, manage the standby database by automatically applying archived redo logs to maintain transactional synchronization with the primary database.
Log apply services can apply logs to a physical standby database when the database is performing recovery (for example, in managed recovery mode), but not when it is open for reporting access (for example, in read-only mode).
For physical standby databases, you can easily change between managed recovery mode and read-only mode. In most implementations of a Data Guard environment, you may want to make this change at various times to either:

Restart on primary database restarts the recovery process on standby

We have a dataguar broker configuration running in maximum perfromance mode.
Every time we start the primary database, the recovery process on standby gets restarted.
I can consistently reproduce teh problem. Looks like expected behaviour.
Even if standby is in read only mode and restart the primary database it bring the database back in recovery mode.
Any explanation why oracle needs to do it?

Neil_Arul wrote:
We have a dataguar broker configuration running in maximum perfromance mode.
Every time we start the primary database, the recovery process on standby gets restarted.
I can consistently reproduce teh problem. Looks like expected behaviour.
Even if standby is in read only mode and restart the primary database it bring the database back in recovery mode.
Any explanation why oracle needs to do it?Yes, When you enable broker it very common behaviour.
When ever you bounce the database also MRP process will be started automatically.
By disabling broker you can avoid automatic startup, BTW Standby should be in recovery mode, i think no need to worry on this.
If you want to disable as per time, you can disable it as below
ALTER SYSTEM SET DG_BROKER_START=FALSE ;
Total Questions: 3 (3 unresolved)
Close the threads when you feel its answered, Keep the forum clean.
Edited by: CKPT on Feb 15, 2012 12:57 PM

DB2 change the database recovery mode

Hi Friends,
We are doing an upgrade, in the process will be necessary to change the DB recovery mode.
Database is DB2 9.5 and the platform is Unix (AIX). I wold like to clarify the process of change the recovery mode, I underestand that it is to switch off the logg retain, but I have found in some forums that in order to switch on the logg retain, when the upgrade finished, I have to have an full backup of this database.
I need to plan this activity and its effects.
Please do you know something about it, can you clarify me the process?
Thanks a lot.
Regards
Enrique Sánchez

The process is pretty straightforward:
1. Shutdown SAP and deactivate the database.
2. Enable recovery mode by setting logarchmeth1 (as user db2<sid>)
db2 update db cfg for <SID> using logarchmeth1 disk:<archivepath> immediate
3. Perform an offline backup of the database (as user db2<sid>)
db2 backup database <sid> to <backuplocation> compress without prompting
The backup time depends on the size of your system. Once the backup is complete, you can activate the database and bring up SAP.
- Sameer

SQL Server Database - Transaction logs growing largely with Simple Recovery model

Hello,
There is SQL server database on client side in production environment with huge transaction logs.
Requirement :
1. Take database backup
2. Transaction log backup is not required. - so it is set to Simple recovery model.
I am aware that, Simple Recovery model also increases the transaction logs same as in Full Recovery model as given on below link.
http://realsqlguy.com/origins-no-simple-mode-doesnt-disable-the-transaction-log/
Last week, this transaction log became of 1TB size and blocked everything on the database server.
How to over come with this situation?
PS : There are huge bulk uploads to the database tables.
Current Configuration :
1. Simple Recovery model
2. Target Recovery time : 3 Sec
3. Recovery interval : 0
4. No SQL Agent job schedule to shrink database.
5. No other checkpoints created except automatic ones.
Can anyone please guide me to have correct configuration on SQL server for client's production environment?
Please let me know if any other details required from server.
Thank you,
Mittal.

@dave_gona,
Thank you for your response.
Can you please explain me this in more details --
What do you mean by one batch ?
1. Number of rows to be inserted at a time ?
2. or Size of data in one cell does matter here.
As in my case, I am clubbing together all the data in one xml (on c# side) and inserting it as one record. Data is large in size, but only 1 record is inserted.
Is it a good idea to shrink transaction log periodically, as it is not happening itself in simple recovery model.
HI Mittal,
Shrinking is bad activity yu should not shrink log files regularly, in rare case if you want to recovery space you may do it.
Have manual chekpoints in Bulk insert operation.
I cannot tell upfront what should be batch size but you can start with 1/4 th of what you are currently inserting.
Most important what does below query return for database
select log_reuse_wait_desc from sys.databases where name='db_name'
The value it returns is what stopping the log from getting cleared and reused.
What is version and editon of SQl server we are talking about. What is output of
select @@version
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Change SharePoint_Config Database to simple recovery mode. Risk.

Similar Messages

Maybe you are looking for