14

This is a known issue[citation needed] and unfortunately restoring to a new content database is the only workaround (I refuse to call it a solution since you now have a new problem). Once restored, you can't move the site back either; the error it returns is about how the site used to exist in the content database. If you can, avoid deleting site ...


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. ...


10

The only reason is that your contents are still residing in SP Content database. Just verify following URL once and check whether you skipped deleting items from this locations. SiteUrl/_layouts/15/AdminRecycleBin.aspx SiteUrl/_layouts/15/AdminRecycleBin.aspx?view=2 SiteUrl/_layouts/15/RecycleBin.aspx SiteUrl/_layouts/15/AdminRecycleBin.aspx?view=2 is the ...


9

To do this we exported each site to the local file system, created a new site collection with the new content DB and them imported the site into the site collection. You can export a site using PowerShell and Export-SPWeb. I recommend testing this process too before you execute it in production, we had lots of tidying up to do with customisations etc. ...


9

You probably need to update the site map in the config db: $db = get-spcontentdatabase -Identity [insert guid of cdb here] $db.RefreshSitesInConfigurationDatabase()


9

This might certainly be it. It might also be trying to create one on the default SQL server and not the one you want. We have 3 sql servers in our farm and it was going to the 1 instead of 2. This is an old point but I did want to point out something. When you run the command: Mount-spcontentdatabase -name (name of your db) -webapplication (name of ...


9

Follow these steps: Open Central Administration. Application Management. View all site collections. Select the site collection you need to get the database name. In the panel on the right you should see "Database Name", that's the name of the content database. -Hope it helps-


9

Felt my way around this, I found that context.Load(file) , context.ExecuteQuery(), was needed to actually load the file, and then I need to proceed into putting it in a stream which I later turned into a byte array which I was able to convert into base 64. public static void GetImage(ClientContext context, string uri) { try { var files = context.Web....


9

Make sure that you have deleted the items in Site Collection Recycle Bin Note: Once the document is deleted it moved to 1st stage recycle bin. It stays there based on the web application recycle bin setting that (default is 30 days). after this period finished (30 days) it moved to 2nd stage recycle bin it also called Site Collection Recycle Bin. In 2nd ...


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 ...


8

Just look at the code snippet below and try to imagine the scenario of what will happen: using(SPSite site = new SPSite("http://somesite")) { using (SPWeb web = site.OpenWeb(SameGuid)) { return web.Url; } } The above code can raise an exception because two web objects would be returned, there are infinite scenarios where GUID is used to ...


8

No that is not possible. That layer of the infrastructure is blocked from Global Administrators. Best you can do is something like: $sites = Get-SPOSite -Limit all foreach($site in $sites){ $site.StorageUsageCurrent }


7

Why not simply using Central Admin... :-) (works even if you do NOT have access to either the physical server (console) or databases server. Central Admin -> Upgrade and Migration -> Review Database Status. By pasting /_admin/DatabaseStatus.aspx at your CA url. Rgds, Arjan Vos


7

When I need to move content from one environment to another I use backup/restore. I see no reason in copying the files, it's far easier to use the backup/restore routines - also there are often the case that you use other tools than SQL backup to do the actual backup. Copying the files is also a dangerous option due to file locks etc, and you don't want to ...


7

There is an information worker download of a complete environment from Microsoft. This includes a pre-populated sample AD, documents, lists, libraries, profiles, etc. http://blogs.msdn.com/b/cjohnson/archive/2011/09/15/2010-information-worker-demonstration-and-evaluation-virtual-machine-sp1.aspx


7

Short answer, the quote above does say RBS and the content database must not exceed the limit. Not just the content DB when RBS is used. Database size is such a gray area with SharePoint. MS's recommendation of 200GB is to ease the maintenance of the database. "Content databases exceeding 200 GB and up to 4 TB support much of the same flexibility as ...


7

because when I was installing second server in farm it said that servers must share config database. Way before starting installation or implementation of SharePoint one needs to decide the topology they will follow as advised by Microsoft as best practices. I am actually very surprised by your questions specially when you are installing second server. ...


7

Directly querying or modifying the database can place extra load on a server, or can expose information to users in a way that violates security policies or personal information management policies. If server-side code must query data, then the process for acquiring that data should be through the built-in SharePoint object model, and not by using ...


6

I know this question is nearly a year old, but we recently had a similar problem and I thought I'd post here in case it helps anyone else. We had the same issue, a web application that, according to central admin, had a single content database with 0 site collections in it. I ran the following commands: $app = get-spwebapplication –identity “url of the ...


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

use below PowerShell code: $url="http://sharepoint.contoso.com/site/subsite/" (Get-SPSite $url).ContentDatabase.name Result should appear as: WSS_Content_2


6

There is a couple of reasons for this: SharePoint is from companies point of view a Microsoft product, so if there is a security risk then it's seen as Microsofts fault. This is the reason for Microsoft to putting in a lot of security into SharePoint which by default isn't in ASP.Net like: not running full trust not allowing updates on GETs and unverified ...


6

In SharePoint 2016 > Create A new web application. Then Create a new site collection. Go back to Application Management > Manage Content database. Click on Content Database name > Check Remove Content Database > OK. Or use Dismount-SPContentDatabase "<ContentdBName>" Open SQL Management Studio. Restore your database. then run the following Mount-...


6

Yes it's correct, you can't restore a content database to another web application on the same farm because the Content Database GUID is already existing. So to overcome this issue, you have to do the following: Create your new web application Create the root site collection. Backup and restore the site collections from source content database to new one ...


5

When you delete a Site Collection, it will still remain in the Content database until the "Gradual Site Delete" Timer job is run (by default, it runs once daily). So, once you delete the site collection and run the timer job, then you can again restore the same site collection in the same content database.


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

Whatever ID the application pool is running as needs 1) proper permissions to the config database (see this info from Microsoft) 2) inclusion in the proper security groups on the local machine (these usually start with WSS_) and 3) permission to go through the proxy using a windows credential rather than a forms-style login. If you are in a large corporate ...


5

Did you check to make sure that you mounted the right db. If you type the database name wrong it will create a new database and it will show 0 current site count. I know - I've done this and because I didn't refresh the sql node I didn't see the new content_database listed. For example: Your content database is named: wss_content_help0101 You meant ...


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

Generally you only have one instance of SQL server per farm. Unless you cluster or mirror you instance. A SharePoint farm can only have one central administration database although you can host the central administration website on more than one server in your farm The SharePoint config database is used by central administration to help manage all of your ...


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