Change Sql server of sharepoint 2013

I have instlled sharepoint 2013 with sql express edition. Now the issue is rising that my database grows up more than 10gb. Now i want to move it to sql express edition. Suggest me the best way to do?
I have database backup. Sharepoint site backup and stuff required to do.
Thanks in advance.

If you still have enough disk space, you can upgrade your Express Edition to Standard Edition on the same server and install the appropriate SQL Server updates. If you want to move the databases to a different server running SQL Server standard edition,
you can backup the databases from the Express Edition, restore it on the Standard Edition, copy the SQL Server logins between them and create a SQL Alias on the SharePoint servers to point to the new Standard Edition database server
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Similar Messages

Can service application be installed on sql server in sharepoint 2013

Hi ,
I want to install SharePoint server 2013. I have two machines
machine 1 : 4 Gb ram , 2.53 GHZ processor core i5 processor( I could upgrade ram to 8 GB)
Machine 2: 8 GB ram , 2.43 GHZ processor core i3 processor.
I want to install sql server 2008 R2 on one of the machine and SharePoint server 2013 on another.
I want to get best performance out of two systems.
I would do farm installation.
1.) Does sql server need to be more powerful or SharePoint server hardware wise.
2.) Can i install applications like , search server , access server etc on the server running sql server.
Basically I am looking for best performance.
Regards
Vinod
+91-9910988922

Hi vinod,
pls take machine 2 for sharepoint server installation. Justification below
http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx
Development or evaluation installation of SharePoint Server 2013 or SharePoint Foundation 2013 with the minimum recommended services for development environments. For information, see Minimum recommended services for development environments.
8 GB
64-bit, 4 cores
80 GB for system drive
Installation Scenario
Deployment type and scale
RAM
Processor
Hard disk space
Single server with a built-in database or single server that uses SQL Server
Development or evaluation installation of SharePoint Server 2013 or SharePoint Foundation 2013 with the minimum recommended services for development environments.
For information, see Minimum recommended services for development environments.
8 GB
64-bit, 4 cores
80 GB for system drive
Single server with a built-in database or single server that uses SQL Server
Development or evaluation installation of SharePoint Server 2013 or SharePoint Foundation 2013 running Visual Studio 2012 and the minimum recommended services
for development environments. For information, see Minimum recommended services for development environments.
10 GB
64-bit, 4 cores
80 GB for system drive
Single server with a built-in database or single server that uses SQL Server
Development or evaluation installation of SharePoint Server 2013 running all available services.
24 GB
64-bit, 4 cores
80 GB for system drive
Web server or application server in a three-tier farm
Pilot, user acceptance test, or production deployment of SharePoint Server 2013 or SharePoint Foundati
Please remember to click 'Mark as Answer' on the answer if it helps you

Use a seperate SQL server in Sharepoint 2013

We have SharePoint 2013 installed and running and its config, content, Search, etc. DBs on SQL 2008R2.
I want to create several NEW SharePoint DBs on a different SQL server that is running SQL 2012 SP1 (For BI mainly) but Im getting errors when attempting to do this. I do have rights on the server and in SQL to perform this action but what
im afraid is that SharePoint doesn't allow me connect to two different SQL servers in the same SP farm. I'm am wrong on this assumption?

You can have as many SQL Servers attached to a farm as you want. Make sure your Farm Admin has dbcreator and securityadmin rights. Then, of course validate that there are no network or host-based firewalls blocking access to SQL ports.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SharePoint - Changed SQL Server but DPM still References Old One

Hello
I have changed my SQL Server for SharePoint 2010 from Server1 to Server2. Everything is working OK. So I need to re-setup DPM as it is referencing the old instance.
I have uninstalled the protection agent for SharePoint on my Web Front End. I have re-installed it and when I go to set up the protection group it displays the SharePoint config as Server1 whereas it now sits on Server2.
Any ideas?!
I am using DPM 2012 SP1.
Thanks

run configuresharepoint.exe –enablesharepointprotection on the web front end and we are all set.
How to be sure that your SharePoint farm is fully protected
How to setup DPM 2012 to protect SharePoint 2010
Have a nice day !!!

How to Use Team Foundation Server With SharePoint 2013 For Development

Hi All,
As i am new to team foundation server and i want to use team foundation server for our development. Please give me good startup point.

Hi,
If you wanted to integrate Team Foundation Server with SharePoint 2013,
there are two articles for your reference:
http://dumians.wordpress.com/2013/04/01/integrate-team-foundation-server-with-sharepoint-2013/
http://nakedalm.com/integrate-sharepoint-2013-with-team-foundation-server-2013/
By the way, you can also post the question in in Visual Studio Team Foundation Server forums and more experts will assist you.
Team Foundation Server – General http://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=tfsgeneral
More information:
SharePoint Products requirements for Team Foundation Server:
http://msdn.microsoft.com/en-us/library/hh667648.aspx
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Is there a way in install a trial version of Project server on a Licensed edition server of sharepoint 2013?

Is there a way in install a trial version of Project server on a Licensed edition server of sharepoint 2013? Is there anyway around this or do I need to make a new box all trial versions to test this out?
Thanks
James T.F

James,
Yes, it is possible , however I wont recommend to do it. Since, once Project trial period expires you need to uninstall project server which can not be done without uninstalling SharePoint. Unless you are willing to rebuild the farm once your
testing is completed
Hrishi Deshpande
Senior Consultant

When I start SQL server agent (sharepoint) service it stops everytime.

hi,
I have a windows server 2012 and SQL server 2008 R2 and SQL server agent (sharepoint) service goes to stop status everytime i start it ,please help me?

There is no error log ,only 3 information log was there after starting the service that one of them is related to it after stopping (event ID=7036 all of them).but also there is a warning information that source of it is DNS client Events and it's event
ID= 1014 and in the general section of explanation i see the user of last event i mentioned is NETWORK SERVICE ,but the account that the service logs on with it,is administrator.
Without error log message or any kind of message its not possible to help you.Is your SQL Server up and running.Did you checked SQL server errorlog.Run this query after trying to start Agent and post the output.
sp_readerrorlog
Also can you locate SQLAGENT.OUT file and open it in notepad.Location can be at
"Drive :\Program
Files\Microsoft SQL Server\MSSQL\LOG--
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL Server for SharePoint farm

Hi All,
As per the best practice to setup the farm, SQL Server shouldn't be a physical machine instead of Virtual. I am wondering what is the reason behind it?
If we do setup the farm in Azure then will it be ok to use the VM for SQL Server since SharePoint doesn't support Azure SQL Server?
Regards Restless Spirit

Generally, for On-Premise, many organizations do not support or allow IT departments to virtualize database servers. This policy is typical in organizations that have dedicated database teams that tightly manage and maintain SQL Server. In these controlled
deployments, the database team has to create all databases. Virtualizing SQL Server is not an option
In Azure IASS, SQL VMs are supported
http://download.microsoft.com/download/8/7/6/876E7EBF-47ED-488D-A861-13A020EB40BD/SharePoint%202013%20on%20Windows%20Azure%20Infrastructure_v1.pdf
Please mark the replies as answers if they help or unmark if not.

Change sql server 2014 server name

Hi
This works on sql 2008 r2, but not on sql server 2014
sp_dropserver 'old_server'
Msg 15015, Level 16, State 1, Procedure sp_dropserver, Line 42
The server 'old_server' does not exist. Use sp_helpserver to show available servers.
sp_addserver 'new_server',local
Msg 15028, Level 16, State 1, Procedure sp_addserver, Line 74
The server 'new_server' already exists.

You mean you are changing server name(Host name) ? But this is only to change SQL instance name not server name.
Please paste output:
Select @@ServerName ServerName, Host_name() HostName
Follow steps from here:
http://mssqlfun.com/2014/06/30/rename-or-change-sql-server-standalone-default-instance/

Change SQL server instance collation after Sharepoint installation

Installed Sharepoint 2013 with the SQL Server 2012 db instance using the default collation Latin1_General_CI_AS. SQL is just used for Sharepoint 2013. the system is not released yet for production Run the installation and configurations and database
attach for all content databases. all content dbs were created by SP with proper collation Latin1_General_CI_AS_KS_WS, as well as search, UP and all service applications.
Would like to change the SQL collation for the instance to Latin1_General_CI_AS_KS_WS(as
https://support.microsoft.com/en-us/kb/2008668) . Steps that I see:
1. Stop IIS on SP
2. Script logins
3. recreate instance collation
setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=<Name> /SQLSYSADMINACCOUNTS=<Sysadmins> /SAPWD=PasswordSA /SQLCOLLATION=Latin1_General_CI_AS_KS_WS
4.recreate logins (including Sharepoint farm, portal and services service accounts) from previous scripts. Redeploy linked servers ,remote logins,endpoints, backup devices
4. attach all Sharepoint databases
5. since it is preproduction not need msdb also model can remain as recreated by setup
do you see any issue?

Hello,
Please take in consideration the steps suggested by Darren Madsen on the following resource.
http://darrenmarsden.com/post/sql-collation-settings-for-sharepoint
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server CLR SharePoint Interface for Sharepoint 2013

Hello everybody.
Is the project
http://archive.msdn.microsoft.com/SqlClrSharePoint
actual to use with Sharepoint 2013 + SQL Server 2012 SP1?
Sergey Vdovin

Have you read the readme that's included within the archive? I'll quote it below for ease of reference: -
Considering it's for SharePoint and SQL instances that are several versions below what's widely used or supported now, I'd be surprised if this worked. The db schema changes alone might make this tricky to get working.
sp_configure 'clr enabled',1
reconfigure
a) Create your target database if it doesn't exist.
b) Mark the database as TRUSTWORTHY, to allow you to run EXTERNAL_ACCESS CLR code.
alter database MyDB set trustworthy on
c) Make sure your database is owned by a sysadmin or the database owner has the EXTERNAL
ACCESS ASSEMBLY privilege.
2) Build the assembly SqlClrSharePointInterface.dll using VisualStudio (or MsBuild)
3) Pre-Generate the XML Serialization Assembly
XML Serializer Generator Tool (Sgen.exe)
http://msdn2.microsoft.com/en-us/library/bk3w6240(vs.80).aspx
eg:
sgen /a:c:\mycode\SqlClrSharePointInterface\bin\release\SqlClrSharePointInterface.dll /f
4) Install the Assemblies in SQL Server
a)Copy the XML Serialization assembly and SqlClrSharePointInterface.dll somewhere where your SQL Server
can read the files.
b) run CREATE ASSEMBLY on SqlClrSharePointInterface.dll, marking it as EXTERNAL_ACCESS
CREATE ASSEMBLY [SqlClrSharePointInterface]
FROM 'c:\deploy\SqlClrSharePointInterface.dll'
WITH PERMISSION_SET = EXTERNAL_ACCESS
c) run CREATE ASSEMBLY on the XML Serialization assembly
CREATE ASSEMBLY [SqlClrSharePointInterfaceXML]
FROM 'c:\deploy\SqlClrSharePointInterface.XmlSerializers.dll'
5) Register the functions by running CREATE FUNCTION on each UDF.
Something like:
CREATE FUNCTION [dbo].[GetListCollection](@siteUrl [nvarchar](4000))
RETURNS TABLE (
[Title] [nvarchar](max) NULL,
[Description] [nvarchar](max) NULL,
[Name] [uniqueidentifier] NULL,
[ItemCount] [int] NULL
) WITH EXECUTE AS CALLER
AS
EXTERNAL NAME [SqlClrSharePointInterface].[ListFunctions].[GetListCollection]
GO
CREATE FUNCTION [dbo].[GetListItemsTable](@siteUrl [nvarchar](4000), @listName [nvarchar](4000), @viewName [nvarchar](4000))
RETURNS TABLE (
[ID] [int] NULL,
[ModifiedBy] [nvarchar](200) NULL,
[Title] [nvarchar](200) NULL,
[ContentType] [nvarchar](100) NULL,
[Created] [datetime] NULL,
[Modified] [datetime] NULL,
[EncodedAbsUrl] [nvarchar](400) NULL
) WITH EXECUTE AS CALLER
AS
EXTERNAL NAME [SqlClrSharePointInterface].[ListFunctions].[GetListItemsTable]
GO
CREATE FUNCTION [dbo].[GetListItems](@siteUrl [nvarchar](4000), @listName [nvarchar](4000), @viewName [nvarchar](4000))
RETURNS [xml] WITH EXECUTE AS CALLER
AS
EXTERNAL NAME [SqlClrSharePointInterface].[ListFunctions].[GetListItems]
GO
Then query SharePoint. Something like
select * form dbo.GetListCollection('http://MySharePointSite');
To get the list of SharePoint Lists available. Then retrieve the items for one of the lists.
the GetListItems function returns a single XML document containing all of the items. So to
make use of the data, you would typically use an XML-shreading query like this:
with ListItems as
select dbo.GetListItems('http://MySharePointSite','Site Collection Documents',null) AllListItems
select
Item.value('@ows_Title', 'varchar(50)') Title,
Item.value('@ows_EncodedAbsUrl','varchar(max)') Url
,Item.query('.') Item
from ListItems cross apply ListItems.AllListItems.nodes('/*/*') Items(Item)
There is also an example of a higher-performance solution that shreads the XML in CLR code
and returns a relational result to SQL Server. But you will need to customize the coding
to return the fields that are relevent in your list.
Select * from dbo.GetListItemsTable('http://MySharePointSite','Site Collection Documents',null)
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

Changing sql server service and sql server agent service startup account in SQL Server hosting SharePoint DB

Hi
i have a sharepoint deployment with one SQL Server (running on VM) hosting the config DB and another SQL Server (Physical Host because VM was running out of space) to host the huge Content DBs. I need to schedule automatic backups of the Content DBs to a
network share. For that i need to run the SQL Server Service with an account having permissions to the share as suggested in https://support.microsoft.com/kb/207187?wa=wsignin1.0
I tried changing the logon as a service account to a domain
account which has permissions to the Network Share and is also in local Administrators group of SQL Server and has "public and sysadmin" roles in SQL Server but that caused an issue. the SharePoint Web Application started showing a White Screen so
I had to revert back to the default accounts i.e. NT Service\SQLSERVERAGENT and NT Service\MSSQLSERVER. I viewed the event logs . These are the types of error i got after changing the logon as a service account to a domain account
1) Information Rights Management (IRM): Retried too many times to initialize IRM client. Cannot retry more. Retried times is:0x5.
System
Provider
[ Name]
Microsoft-SharePoint Products-SharePoint Foundation
[ Guid]
{6FB7E0CD-52E7-47DD-997A-241563931FC2}
EventID
5148
Version
15
Level
2
Task
9
Opcode
0
Keywords
0x4000000000000000
TimeCreated
[ SystemTime]
2015-02-02T04:46:04.750899500Z
EventRecordID
176477
Correlation
[ ActivityID]
{8FACE59C-1E17-50D0-7135-25FDB824CDBE}
Execution
[ ProcessID]
6912
[ ThreadID]
8872
Channel
Application
Computer
Security
[ UserID]
S-1-5-21-876248814-3204482948-604612597-111753
EventData
hex0
0x5
2)
Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below.
The target principal name is incorrect. Cannot generate SSPI context.
System
Provider
[ Name]
Microsoft-SharePoint Products-SharePoint Foundation
[ Guid]
{6FB7E0CD-52E7-47DD-997A-241563931FC2}
EventID
5586
Version
15
Level
2
Task
3
Opcode
0
Keywords
0x4000000000000000
TimeCreated
[ SystemTime]
2015-02-02T07:01:35.843757700Z
EventRecordID
176490
Correlation
[ ActivityID]
{50B4E59C-5E3A-50D0-7135-22AD91909F02}
Execution
[ ProcessID]
6912
[ ThreadID]
5452
Channel
Application
Computer
Security
[ UserID]
S-1-5-17
EventData
int0
0
string1
The target principal name is incorrect. Cannot generate SSPI context.

Hi Aparna,
According to your description, you get the above two errors when scheduling backups of Content DB. Right?
Based on those two error messages, they are related to the service principal name(SPN) for SQL Server service. Please verify the if the SPN is registered successfully. You can view it in ADSI Edit or use command line. Please see:
http://blogs.msdn.com/b/psssql/archive/2010/03/09/what-spn-do-i-use-and-how-does-it-get-there.aspx
When installing SQL Server, those two services below should be registered:
MSSQLSvc/servername:1433
MSSQLSvc/servername
Please check if those SPNs or duplicated SPNs exist. You can use command to reset SPN or remove duplicated SPN and add new one. See:
Setspn.
We have also met this issue when this SPN is registered under Administrator. Please try to register it under Computer. You can add it in ADSI Edit.
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

SQL Alias for Analysis Server for SharePoint 2013

Hi
I created a SQL Alias for my Analysis Server but somehow, It is not working.
I am frequently using SQL Alias for my SQL database servers within the SharePoint 2013 and it is working correctly.
Could you please guide me for this.
Regards,
Yogendra
My name is yogendra

A Sql Aliase works only for relational database engines, but not for multidimensional engines / SSAS
Olaf Helper
[ Blog] [ Xing] [ MVP]

Report service Integration (sql 2012 and SharePoint 2013) error Report Server WMI Provider error: Invalid namespace

Report Server WMI Provider Error: Invalid namespace
Domain Server, Sql2012 server and SP2013 Server (3 vm servers)
the sql server reporting services service application and applications Proxy are installed and started (SP2013 Sever)
the sql server PowerPivot system Service and SQL server Reporting Services Service are Started (in Services on Server)
in sql server 2012 sp1 reporting service configured (web service URL and Report Manager URL are configured and tested, the database report server mode is native) (SQl 2012 Server)
under general Application Settings .. trying to setup the "Reporting Service Integration" give us the above error message (Report Server WMI Provider Error: Invalid namespace)
I was looking for all blogs and TechNet material but without success.

Follow these steps:
1) Uninstall SSRS from the Database Engine server (MSSQLSERVER instance).
2) Install SSRS on the SharePoint server using the "Reporting Services - SharePoint" install option during SQL Feature selection, no other services are required (e.g. you do not need to install Database Engine services).
3) You should then see SSRS as a Service Instance in Central Admin -> Manage Services on Server, at which point you can also create an SSRS Service Application.
While this guide (http://msdn.microsoft.com/en-us/library/jj219068.aspx#bkmk_install_SSRS) walks you through it, this is for a single server install where the Database Engine is also installed on SharePoint, not something you want to do.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Office web apps Server for Sharepoint 2013

Hello,
I used the following article to install office web apps server and hook it up to a test sharepoint server:
http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx. The OWAS service was verified as working by loading:
https://owas.companyname.com/hosting/discovery
For the sharepoint configuration phase, the following commands were run on the sharepoint machine:
1) New-SPWOPIBinding -ServerName "owas.companyname.com" -- (owas.companyname.com) is the host name of the owas server)
2) Get-SPWOPIZone
3) Set-SPWOPIZone -zone "external-https"
However, office documents are still launching in the desktop office applications, not in the browser. Any ideas of what else I may need to do?
thanks,
Sherazad

Hi ,
According to your description, my understanding is that you fail to configure Office Web Apps for your SharePoint 2013.
How about run Get-SPWOPIZone? If you can get a result, it says that your SharePoint have connected with Office Web Apps.
Then you can run below command to change the zone to internal-https.
Set-SPWOPIZone -zone "internal-https"
Reference:
http://technet.microsoft.com/en-us/library/ff431687(v=office.15).aspx
http://stevegoodyear.wordpress.com/sharepoint-2013-build-guide/office-web-apps-2013-server-install-and-configuration/
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
contact [email protected]
Eric Tao
TechNet Community Support

Change Sql server of sharepoint 2013

Similar Messages

Maybe you are looking for