Thursday, 18 October 2018

Managed Metadata terms changes display name is reflecting . Taxonomy Update Scheduler is not working

I am using Terms in list publish using Managed metadata services. I required to do Change certain terms . its Changed successfully.

I open the list where i am using it , its update as display only, when i use custom code to fetch the term its still showing the previous name. 

i verify the Taxonomy Update Scheduler from timer services , its running without any error, but somehow its not updating the values.

There is hidden list for taxonomy  that is need being update automatically, 

Need to update the Hidden list using powershell with below script.

$siteUrl = "http://devvmspap01:15734/"
$site = Get-SPSite $siteUrl
[Microsoft.SharePoint.Taxonomy.TaxonomySession]::SyncHiddenList($site)
$site.dispose()


Wednesday, 17 October 2018

Migrate SharePoint SiteCollections from one farm to another farm using Content Database

SharePoint Site collection can be moved to another farm or location using site collection backups or Content database back up.

If you required only one sitecollection then we can backup site collection using powershell or SharePoint central admin.

in my cases i have 2 site collection in one web application and both are using same content database.

I use Content database method.

Step 1 : backup Content Database from SQL Server.


Step 2: Restore Content database to new SQL Server (new Loction)
 








Step 3: Mount-SPContentDataBase
           
if you don't have existing web application please create new web application  and mount your database to web application, it will use the same managed path as you have in original location.

Mount-SPContentDatabase "WSS_Content_MyDB" -DatabaseServer "DEVVMSPDB01\SP2013DB" -WebApplication http://devvmspap01:15734/

SharePoint Database Log file is increase. (Shrink the SharePoint database Log file)


SharePoint Log files are Increase more then database file or some time increased more then it, 
Easy way is to reduce the log size using  Shrink the Log file.


-- Set database to simple
ALTER DATABASE WSS_Conten_MyDB
SET RECOVERY SIMPLE; 
GO 


-- 1st parameter is Database Log File name , 2nd parameter is new log Size in MB (100 MB)
DBCC SHRINKFILE (WSS_Conten_MyDB_Log, 100); 
GO 


-- Reset the database recovery model to full
ALTER DATABASE WSS_Conten_MyDB
SET RECOVERY FULL; 
GO