Reporting Services (SSRS)

External Article

SQL Server RDL Specification

  • Article

In today's database reporting market, most vendor applications use a proprietary format for representing the definition of a report. In addition, vendors that provide a report execution environment usually only support their own design tools. For customers, this means that reports cannot be easily moved between different reporting implementations and that there are few options for choosing new tools that work with their existing execution environments.

2009-10-08

440 reads

External Article

Securing Reporting Services

  • Article

Marcin Policht continues his discussion of implementing Reporting Services on SQL Server 2005 Express Edition, focusing in particular on security-related topics. This article continues this subject by describing other technologies that assist with data protection, their corresponding configuration settings, and a few authentication and authorization caveat

2009-10-07

2,632 reads

External Article

Reporting Services System and Item Security

  • Article

Recent installments of our series have focused on SQL Server 2005 Express Edition's implementation of the Reporting Services component. This article addresses our temporary disregard of security restrictions by describing authentication and authorization functionality that can be leveraged to control access to published content and management characteristics.

2009-08-24

2,699 reads

External Article

Taking Advantage of Sample Reporting Services Reports

  • Article

Recent installments of our series dedicated to SQL Server 2005 Express Edition have discussed the Reporting Services component. This article provides an overview of sample reports that you can take advantage of in order to familiarize yourself with the more advanced graphical designer features present in SQL Server 2005 Express Edition-based Reporting Services.

2009-07-03

2,764 reads

Technical Article

The Basic Functionality of Report Designer

  • Article

Recent installments of our series dedicated to the most prominent features of SQL Server 2005 Express Edition have discussed its reporting capabilities. This article illustrates another approach to generating reports, relying on the Report Server Project template, which offers a considerably wider range of flexibility than its wizard-driven counterpart does.

(1)

You rated this post out of 5. Change rating

2009-06-18

2,151 reads

Technical Article

Report Design Tips and Tricks

  • Article

This white paper covers best practices on report design and helps you avoid common mistakes when choosing a report layout and output format. Take advantage of existing product features to achieve the results you want. The paper includes report and code examples that implement functionality that is frequently requested.

2009-05-13

4,606 reads

Blogs

Crawl, Walk, Run with Agentic Development of Power BI Assets

By

If you’ve been watching AI roll through the data community and thinking, “this seems...

How AgentDBA Diagnoses SQL Server Issues Fast

By

Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...

Five Ways Redshift Serverless Quietly Eats Your Budget

By

It is Friday, the queries are running, and nobody is watching the bill. That...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

Finding 'bad' characters

By Barcelona10

Hi All I am trying to find 'bad' characters that users might type in....

BCA KCP Pulogadung Trade Centre Tlp:0817839777

By R4nt4u

WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...

Visit the forum

Question of the Day

Changing the Schema

I set up a few users on my SQL Server 2022 instance.

CREATE LOGIN User1 WITH PASSWORD = 'Demo12#1'
CREATE USER User1 FOR LOGIN User1
GO
CREATE LOGIN User2 WITH PASSWORD = 'Demo12#2'
CREATE USER User2 FOR LOGIN User2
GO
CREATE LOGIN User3 WITH PASSWORD = 'Demo12#3'
CREATE USER User3 FOR LOGIN User3
GO
I then created a schema that one of them owned. Under this schema, I added a table with some data.
CREATE SCHEMA MySchema AUTHORIZATION User1
GO
CREATE TABLE Myschema.MyTable(myid INT)
GO
INSERT MySchema.MyTable
(
    myid
)
VALUES
(1), (2), (3)
GO
SELECT * FROM MySchema.MyTable
GO
I granted rights and verified that User2 could access this table.
GRANT SELECT ON Myschema.MyTable TO User2
GO
SETUSER 'USER2'
GO
SELECT * FROM MySchema.MyTable
GO
This worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3;
GO
What happens with this code?
SETUSER 'USER2'
GO
SELECT * FROM MySchema.MyTable
GO

See possible answers