Best practises for SSRS

-


Ø  Optimize the query to avoid unnecessary burden on the database. Avoid the use of "SELECT *" statement and specify only the columns that are required in report.

Ø  Do not use Report Parameters to filter the report data unless you are using Snapshot reports. Use Query parameters instead of Report parameters as Query parameters filters data while extracting it from database server to Report Server. On the other hand, when Report parameters are implemented, report is re-executed again based on report parameters/filters and the report server filters data again based on Report parameters.

Ø  Prefer to use Custom Assemblies rather than Embedded Code in case the same Custom Function (Embedded Code) needs to be referenced in multiple reports.

 

Comments

Post a Comment

Hi User,
Thanks for visiting My Blog and please provide your valuable feedback and subscribe for more updates. Please don't post any spam content or comments.
Thank You

Popular Posts

Failed to execute the package or element. Build errors were encountered

-
Error: TITLE: Microsoft Visual Studio ------------------------------ Failed to execute the package or element.   Build errors were encountered. For more information, see the Output window. ------------------------------ BUTTONS: OK ------------------------------   Solution: We tried to close SSDT and run it again but, we still got the same error while running SSIS package. Then, we need to follow bellow solution: Step 1: Go to Task Manager–> Details Tab. Step 2: Locate the process “ DtsDebugHost.exe “. Kill this process. There might be multiple instances of this process. Kill all of them. Step 3: Rerun SSIS package
Read more

Restore of database 'DataBase_Name' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)

-
TITLE: Microsoft SQL Server Management Studio ------------------------------ Restore of database 'DataBase_Name' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks) ------------------------------ ADDITIONAL INFORMATION: System.Data.SqlClient.SqlError: Exclusive access could not be obtained because the database is in use. (Microsoft.SqlServer.SmoExtended) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=12.0.2000.8+((SQL14_RTM).140220-1752)&LinkId=20476 ------------------------------ BUTTONS: OK ------------------------------ Procedure 1: 1. Right click Databases 2. Restore Database... 3. [General] Source from Device, select the bak file 4. [General] Change the Destination database name to a new name 5. [Files] Change mdf and ldf Restore As paths to a different, new path 6. [Options] (unnecessary on the other computer) Check Overwrite the existing database (WITH_REPLACE) 7. [Options] (unnecessary on the other computer)
Read more

Get List of logins on SQL Server instance

-
-- List of logins select sp . name as login ,        sp . type_desc as login_type ,        sp . type ,        sp . create_date ,        sp . modify_date ,        case                when sp . is_disabled = 1 then 'Disabled'             else 'Enabled'           end as status from sys . server_principals sp left join sys . sql_logins sl on sp . principal_id = sl . principal_id order by sp . name ;   --Get the list of all Login Accounts in a SQL Server SELECT name AS Login_Name , type_desc AS Account_Type FROM sys . server_principals WHERE TYPE IN ( 'U' , 'S' , 'G' ) and name not like '%##%' ORDER BY name , type_desc   --Get the list of all SQL Login Accounts only SELECT name , type_desc AS Account_Type FROM sys . server_principals WHERE TYPE = 'S' and name not like '%##%'   --Get the list of all Windows Login Accounts only
Read more