In this article, I will elaborate How to Scale Out SQL Reporting Service (SSRS) to work with two Database Server (Always-on)?
I have a 2-Tire SharePoint 2013 Farm
- 2 WFE+ APP Servers.
- 2 Database Servers (Always-on).
If you need to use Reporting Services with SharePoint. it’s recommanded to configure SSRS SharePoint integrated mode with Reporting service application service on an indpenedent reporting server to ensure the Performance, Manageability and Security.
But in my case, the customer budget is not enough to apply the best practice, Meanwhile configuring SSRS SharePoint integrated mode with Reporting service application service on the same WFE + APP server lead to low performance.
So I have decided to work with SSRS Native mode to ensure at least the performance and show reports inside SharePoint via:
And in this case, I should configure SSRS Native mode on both SharePoint WFE Servers because as we know the Database Servers are not accessible over the internet,
Note: If you configured SSRS native mode on only one WFE server. you will get it worked properly. but sometimes when browsing the Report Manager URL you will get 404 error!
Continue reading “Scale-Out Deployment for SQL Reporting Service (SSRS)”
After installing and configuring SQL Server Reporting Service.I tried to open Report Manager URL but unfortunately, I got the following error:
User does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed.
The current user doesn’t have a sufficient permission to access Report Manager URL.
Solution: Continue reading “SSRS Permission Issue: User does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed.”
SQL Server Reporting Services (SSRS) is a server-based report generating software system from Microsoft. It is part of suite of Microsoft SQL Server services, including SSAS (SQL Server Analysis Services) and SSIS (SQL Server Integration Services).
In this article, I will elaborate How to install and configure SQL Server Reporting Service (SSRS) native mode.
Note: The mentioned steps is valid for SSRS 2008 / 2012 / 2014.
Steps: Continue reading “Install and Configure SQL Server Reporting Service (SSRS)”
In some situation, you may need to check the SQL Server Instance connectivity from the application server to database server for a specific user especially when you don’t have access to SQL Servers on your farm based on your company policy.
You may try to perform Ping cmdlet for the SQL Server IP and Telnet to SQL TCP port.but that means There’s a network connectivity between two servers and you can reach the database server from the application server.
But what about if you need to test connectivity to SQL Server Instance for a specific user without using SQL Server Management Studio?
In this case, you can test connectivity to SQL Server Instance by creating a data link UDL file as I have mentioned below:
Steps: Continue reading “How to Check SQL Server Instance Connectivity from the application server to database server for a specific user without using SQL Server Management Studio”
In this hint, I’ll show How to get the build number of the latest Cumulative Update / Service Pack that has been installed in SQL Server.
I decided to configure PowerPivot for SharePoint 2013 Enterprise Edition with Service Pack 1 that requires installing SQL Server 2012 Service Pack 1 as a prerequisite.
So that I need to check if the SQL Server Service Pack 1 has been installed on my DB Server or not by getting the build number of the latest Cumulative Update / Service Pack that has been installed in SQL Server by following the mentioned steps below:
Steps: Continue reading “Get the build number of the latest Cumulative Update / Service Pack that has been installed in SQL Server”
The Major factor that faces me when I was trying to create a Shrink a transaction log file Maintenance Plan is the shrink option in Maintenance Tasks that include shrink operation for both data file and transaction log file, and there is not an option for only log file!
In this article, I am trying to perform a shrink operation for only the transaction log file via Maintenance Plan to run on a regular basis or on demand based on your requirement.
Before you start, you should be aware of the following
- To create or manage maintenance plans, you must be a member
of the sysadmin fixed server role.
- The SQL Server performance will be affected during executing The Shrink operation. Thence, I advise performing the shrink operation out working hours.
- The Shrink operation causes index fragmentation and can slow the performance of queries that search a range of the index. So you should consider rebuilding the indexes to eliminate the fragmentation before the shrink operation has been completed .
Therefore, It’s not recommended to perform the shrink operation periodically! Only in some circumstances that you need to reduce the physical size. (Check the possible responses to a full transaction log and suggested how to avoid it in the future).
Steps: Continue reading “Shrink a transaction log file Maintenance Plan in SQL Server”
In the previous article, I discussed the possible responses to a full transaction log and suggested How to avoid it in the future.
In this article, I will explain
- How to create a LOG_BACKUP Maintenance Plan in SQL Server that should be run on a regular basis or on demand via Microsoft SQL Server Agent.
- How to restore a LOG_BACKUP that have already taken via Maintenance Plan.
Continue reading “Create a LOG_BACKUP Maintenance Plan in SQL Server”