Proposals for splitting a database server from a SharePoint Farm

By -
SharePoint 2013 Farm Architecture

Proposal No 1

Architecture Changes:
·         Adding a new server as Web Front End.
·         Redirect all clients (users) requests to new WFE.
Advantages:
·         Only SharePoint services along with SQL services will be running on the existing server.
Disadvantages:
·         Installation and configuration of SharePoint server on new WFE.
·         Installation and configuration of all third party/custom solutions packages.
·         The existing server will still have SharePoint server instance running along with SQL server, in a result more resource consumption.
·         A license would be required for a new WFE in case we currently have license per server.
Procedure:
·         Install SharePoint server on new WFE.
·         Connect the server to existing SharePoint farm after installation.
·         Install/configure third party or custom solutions on new server.
·        NLB changes to redirect users to new server.




Proposal No 2
(Recommended on the basis of less workaround and advantages)
Architecture Changes:
·         Adding a new server as dedicated DB server.
Advantages:
·         DB server will be separated from SharePoint instance.
·         No installation of SharePoint or any third party/custom solution will be required.
·         No changes required in NLB and user’s requests will be served same as currently.
·         Independently change resources of DB server.
·         No license required for new DB server as it will not run the SharePoint instance.
Disadvantages:
·         Installation of SQL server and SSRS on new server.
Procedure:
·         Separating Content DB’s:
o   Install SQL server on new server.
o   Backup and restore existing content databases and from old server to new one.
o   Set new DB server for content databases in CA.
·         Separating SSRS:
o   Install SSRS on new server.
o   Change connection strings to point new DB server.

Note: You must check my other notes on Moving All SharePoint Databases to new DB Server for best way to move your all SharePoint content and config DB's to new server.


Comments

Post a Comment

Popular Posts

GREYCstoration Oil Paint plugin for Photoshop

By -
Image
Oil Paint Filter is missing in Photoshop? Try GREYCstoration plugin. An alternate for Oil Paint filter. I found my Adobe Photoshop CS5 is missing Oil Paint filter plugin due to GPU unavailable on my machine. I found an alternate tool to get oil painting effect on photos. Below are the steps to use this tool. 1.  Download  tool and extract http://www.mediafire.com/download/3j15dj3opmip4ez/GreycShop.zip 2. Copy the extracted files on below path(s)     For 64Bit: C:\Program Files\Adobe\Adobe Photoshop CS5 (64 Bit)\Plug-ins     For 32Bit: C:\Program Files (x86)\Adobe\Adobe Photoshop CS5\Plug-ins 3. Run Adobe Photoshop 4. Select Noise >> GREYCstoration  For example: Enjoy :)
Read more

Apple iPhone sending SMS automatically 00447786205094

By -
Image
Hi There, I have just noticed that my credit is being deducted from my mobile account. I am in Pakistan and using Warid Tel network. I see my mobile credit details after few hours on my screen. This facility is provided only by Warid Telecom that they provide your credit details each time you make a call or send SMS. I checked my Message,Calls logs emails logs etc but no point where i can check that why me credit is being deducted. Absolutely nothing found. :-/  I called Warid Tel support center and the guy told me that there are 4 SMS that have been sent internationally from my iPhone 5. Whattt???? :O I have't sent even a single one. He was bound not to tell me the number however i found that number from Warid Tel online customer portal. That magical number was  00447786205094. Warid Web Self Service Portal I googled and found that its UK number and an iPhone application Facetime/iMessage used to send text to this number for their activation wi...
Read more

SharePoint online hub navigation not updating for other users

By -
Its been quite a time that I am working with SharePoint Online and meeting new challenges every day. Its feels great when you find a solution for something which Google do not tell you. I am just writing this post because there might be someone out there facing the same issue and this post might help him. BTW, before you check the actual post of how to fix the navigation check below, this might also help to change the user language. Problem Description: When an Admin of SharePoint Online site, updates the hub navigation (or may be site navigation), it do not get updated for all the users instantly. User has to clear browser cache to get the updated navigation. As per discussion with Microsoft, SharePoint saves a copy of the navigation in browser cache which automatically refreshes after a certain period of time. By default, you cannot clear browser cache using React or JS code. Browsers do not allow you to do so. So, the user should wait till that time? ABSOLUTELY NOT! (Imran Khan 😋 )...
Read more

Service Bus Gateway service stuck at Starting

By -
Image
Lesson Learned: Never leave your servers to automatically download and install the updates. We had a SharePoint farm where Workflow manager is configured on one of its server and rest of them are just using WFM client to connect with the server. Everything was running smooth until some updates got installed on the servers over night and the next morning Workflows stuck and start giving errors. As initial check, I verified SharePoint services and WFM services, noticed that the Service Bus Gateway service is struck at Starting state. This was very generic thing but at least a point to start thinking... Troubleshooting: 1. Tried manual restart, but no luck. 2. Tried Leaving and Joining the WFM Farm again. But the timeout error. Error message received during rejoining:  “Starting Service bus gateway on machine <servername> failed: timeout has expired and the operation has not been completed” 3. Tried ULS check and noticed below error. "  Service cannot be started. Micr...
Read more

RangeError: Maximum call stack size exceeded | Node JS | SPFX React

By -
Image
I literally had no idea that my minor experiment can ruin my 10 hours in troubleshooting. However, at the end, you learn something new. I am currently developing a project in SPFX - React to build a customized portal for a client. Later today i modified a config file in the SPFX project called "config.json" to include a new script file. Everything worked perfect until I stopped the debugging and start it again after some time. When I ran Gulp Serve I start seeing below error when Node tried to start "webpack" await Promise.all(externalModule.globalDependencies.map(async (dependencyName) => { RangeError: Maximum call stack size exceeded and some other errors like below. This is probably not a problem with npm. There is likely additional logging output above. npm ERR ! A complete log of this run can be found in : Googled around and found few solutions like clearing NPM cache with  npm cache clean --force and deleting package-lock.json,  then ran npm install ag...
Read more