16

There are lots of point to discuss before coming to a conclusion here. But I will just explain the different possible ways you could do backup in SharePoint in an order of good to best. Central Admin Backup - This is a default UI option that comes within Central Administration. It allows to take full and differential backups. You have the additional ...


14

Given the amount of bloat and the fact there's not much in the 2nd stage recycle bin, it's more than likely Auditing has been turned on for the site collection. I believe trimming of the audit log is not enabled by default either, which could cause your content db to grow out of hand pretty quickly depending on level of activity within the site collection. ...


11

I discovered that the problem comes from the program Microsoft Visual Studio 2010 Shell (Isolated) - ENU that gets installed with SQL Server 2012. After uninstalling that program and then running the SharePoint 2013 installer I am able to see the splash screen. Warning - This will prevent Sql Server Management Studio 2012 from working on that machine.


11

If you use the commandlet Get-SPDatabase there are several properties of the returned object that can give you the information you need. $db = (Get-SPDatabase)[0] $db.Server Will print out the full server name, and I would assume instance, for that database. Another interesting property would be $db.DatabaseConnectionString That will print out something ...


9

It is not supported, sharepoint 2010 is not supported on even Microsoft SQL Server 2014. If you read the software requirement MSFT give the equation which help to determine awl version support. In order to maintain SharePoint and SQL Server compatibility we use the “SharePoint N-1 on SQL Server N+1” equation to determine version support. Using ...


8

Definitely don't want to go the SQL query route because you can easily create an ineffecient query if you don't understand the underlying data model...also possible that you'll develop a query that breaks or becomes inefficient after a CU or SP is applied. CAML queries are very efficient and depending on the scope of your query you have a lot of options. ...


8

To find the table(s) which are taking up the most space run this query in SQL Server Management Studio (with your content database selected to query against). That should help you narrow it down to a particular table or tables and then from there you can determine what can be done to reduce the size. You might want to throw some "with nolock"s in there to ...


7

If you want to split your site collection into multiple Content DB and then spread those DB across both SQL server. then it is Big NO You can not have a site collection in to Multiple database, it is not supported. If you want multiple SQL server attached to a farm, then you can do it. It is supported. we have 4 SQL server attach to one farm due to ...


6

The biggest determining factor here between SharePoint Backups and SQL Server backups is going to be how much content you have in your farm. Based on what I could find on TechNet, SharePoint backups are not supported for content databases over 200 GB in size (http://technet.microsoft.com/en-us/library/cc262787.aspx) and site collections over 100 GB in size (...


6

I have never done it personally but Microsoft has a document that lays out the steps pretty clearly. As always, be sure to take a good backup before attempting this. Shrinking a database by using SQL Server 2008 Management Studio On the taskbar, click Start, point to All Programs, point to Microsoft SQL Server 2008, and then click SQL Server Management ...


6

Yes, You can. One Sql Server with two Different SharePoint Farm. Currently i have two Dev farm(2013) which are sharing the Same Database server. As long as you have unique Names for your Config & content DBs. Having Enough hardware to support both farm I am positive you will not do this in production, big risk. If DB server goes down...both farm will go ...


6

The service which makes a SharePoint server web front end is Microsoft SharePoint Foundation Web Application service. If it is started in a server, it becomes web front end. The services will be available in all servers. However, it is the status (started/stopped) which determines the role. That can be checked by going into CA->Application Management -> ...


6

Yes, It's compatible. Just make sure you use MOSS SharePoint Service Pack 3, and you should be just fine. Also there's no difference to SharePoint concern whether you use SP2 or SP3 on the SQL Server. In general SHarePoint installations work with one version up and down of the current minimum requirements. As SharePoint 2007 minimum requirements are SQL ...


5

Here are some details about support for large databases with SP1. http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=988 Officially there is support up to 4TBs with optimization, but realistically that is difficult to support and should only be used in extreme exceptions. Technically there were no real changes made to support the additional ...


5

Microsoft licensing can seem complicated if you are doing that for the first time and I would advise you to contact a licensing specialist in your country/region that can help you optimize for best price and licensing deals. For a company of 10000 people you should not be checking these prices online, you need to talk to licensing specialist! Chances are you ...


5

SSRS, to be used in SharePoint Integrated Mode, must be installed on a server that has SharePoint installed and joined to the farm. Obviously this would not be a good idea to install SharePoint on a Database Engine server if you can avoid it. Install SSRS on your SharePoint server in Integrated mode. Yes, you must license SQL Server (SSRS) on your ...


5

First thing you should do is choose the appropriate recovery model for your databases. If you need point in time restore, go for the FULL recovery model. The price you have to pay is to make regular log backups or your logfile will grow indefinitely. Taking a full backup does not stop them from growing. If you use mirroring or log shipping, you also need to ...


5

This can mean any of the two things. A previously deleted site collection is still residing in the content database if your farm is a SP2010 SP1 and above. This can account to different size of the site collection that shows up in the central admin and a different size for content database keeping all deleted site collections. Your Content Database contains ...


5

When a site collection's size is calculated, the size of the second stage recycle bin is not included. However, the size of 2nd stage recycle bin will contribute to the size of your content database. Perhaps your 2nd stage recycle bin is large? Consider emptying the recycle bin and/or adjusting its quota settings in Central Admin (web application settings > ...


5

You can use Caching a DataTable Object The code in these examples suspends all other threads in a critical section running in IIS, and prevents other threads from accessing the cached object until it is completely built. This addresses the thread synchronization issue; however, the code is still not correct because it is caching an object that is not ...


5

1. A calendar that, when a user logs in, is filled with courses that the user is currently signed up for. The information is contained within a SQL database we keep on-prem (The server itself is hosted by Microsoft). You can create a job that will be pushing items from your SQL to SharePoint (you can use Client Object Model or rest object model https://msdn....


5

I agree with Trevor that you don't have to do anything however, generally if the SQL servers are going to be offline, it's a good idea to shut the SharePoint servers down before SQL goes offline and start them back up after SQL is back online again. This provides a good opportunity to clear any cobwebs from memory while shutting all of SharePoint down ...


5

They carry the same requirement as MAXDOP = 1, especially now that in 2016 the Project schema resides within the content databases.


4

Simplest answer is: No. Similar issue (follow first link provided in answer): SharePoint License for Database Server Look also at comment by Jesus Shelby The only exception would be if you are running Reporting Service in integration mode, then you would have SharePoint installed alongside the SQL instance hosting the report server.


4

This was nice quest for me. I will not ask why do you need this and I hope that you don't need warning like: Never mess with SharePoint databases directly! I didn't found many articles on net covering this specific issue (no wonder when it is bad practice). The only one was 2007 related: Determining the Configuration Database in a SharePoint 2007 Farm. ...


4

As long as you name your 2010 configuration database differently than your 2007 config db, you should be fine. In general, I'd recommend making an effort to name all the databases for your 2010 farm in a way that you can easily distinguish the databases for each farm. Or, you could create a separate database instance on your SQL Server host and point your ...


4

Doing the SQL Server backup of the content databases is almost identical to what you are doing with the PowerShell script: protecting your content. This is of course the most important thing that you will want to protect. The advantage that doing these backups through a maintenance plan on SQL gives you is that you can perform both full and differential ...


4

It's not the prerequisites installation which selects sql, but the SharePoint installation. To run on a real Sql Server select Server Farm and then Complete, NOT Standalone or Stand-alone: When you then run the Configuration Wizard you are prompted to select the SQL server: Images taken from How to Install SharePoint 2010 on Small Farm – Part 1: Full ...


4

You should be backing up and truncating your TLOGS. If you have not been doing that, than yes, do a backup, truncate, and shrink will restore space. To keep that space however, you will need to set growth limits on your database and log files. Microsoft has a paper on "best practices" with SQL maintenance: http://technet.microsoft.com/en-us/library/...


4

Minimal is SQL Server 2008 Express with SP1. The main difference with Standard is you can have a larger than 4gb database. So the answer is yes. Comparisons here


Only top voted, non community-wiki answers of a minimum length are eligible