So, till now, we have done a lot of labs on SSIS and SSIS. And also we have gone in depth into SSIS and SSIS and even on the SSRS part we have done some labs, but we have not got into in details of SSRS. So, in this video we will try to understand understand internals of SSRS. So, we will try to understand the architecture of SSRS we will try to understand something called as report server we will try to understand what exactly are reports we will try to understand the configuration tool. So, in this video we will be going in depth into SSRS and understand the architecture and tools of SSRS. Now, till now, we have been running the SSRS reports inside the Visual Studio.

Now this Visual Studio tool over here is only meant for development purpose. This will not be available on production. This is only for programmers for msba programmers. So what if the end user wants to go And see this report you know, how will you actually go and see the report right that is the first thing. So, the first point I want to put forward here is that if you see at this moment, you know, all these reports are stored into this dot RDL file, you can see over here, this dot RDL file. And if you remember, in one of the previous videos, I said that this RDL file is nothing but it is actually an XML file.

So, if you go and see the code internally it is a it is a XML file. Now, this is a development environment. If you want to go and put these reports on a production environment, you need two things. You definitely need SQL Server. And second is you need Internet Information Server that is I is now in order to configure IIS and SQL Server for SSRS. SSRS has given us something called as The SQL Server Reporting Services configuration tool.

So if you go here to the configuration tool, you can find this reporting services Configuration Manager. So this tool actually helps you to configure IIS and SQL Server for your SSRS. Software or for your SSRS deployment. So you can see first thing when I actually say Connect, it actually tells me that Okay, tell me, you know, which instance of reporting services you want to connect, right? So I will say, Actually, I'm going to go and connect to this server name. Now, one of the things which can come to your mind is that why is he asking for a SQL Server thing?

What does SSRS have connection with SQL Server? So let me just flip to SQL Server here. Now what happens is that when you go and deploy your reports to your server to your production server, it gets deployed into these two databases. You can see here there is some called us a report server database. And there is something called as a report server and DB database. Now this report server is a database in which your reports will get stored, okay.

And this report server temp DB is for caching purpose. So for example, if you have a report which you are pulling again and again, and the report data is not changing, then it will actually go and store those ready made reports into report server temp dB. So reports our temp DB is for caching purpose. And the report server database is where your reports actually get stored. Right. So at the end of the day, your SSRS stores your reports into these two databases.

What it also means is that tomorrow if you want to go and migrate your server from if you want to migrate your reporting services server, then you need to migrate both of these databases as well. And also a word of caution. If for some reason both of these databases go off Then your reports have a big problem. So you need to backup these two databases time again and again, to ensure that you do not have problems, right? So first thing, when you actually go and deploy your reports, your RDL files onto your production, it actually gets stored into SQL Server. And to configure your report server database, right, you need to go to the reporting services Configuration Manager, and you need to click on this database tab here.

And over here, you can see that you can you need to give two things. One is, you know, where your databases and another one is the credential for the database. So in case tomorrow, if your database is changing, right, you need to actually go and give the provide the appropriate things over here. So one thing is that the reports get saved into the reporting services database. That means it gets saved into report server or report server temp dB. The other thing is that, you know, we need a way by which you know, these reports can be rendered.

Remember that at this moment you are rendering using the Visual Studio ID. So when you render using the Visual Studio ID it is all inside the development environment, we are talking about now the production environment. So in production environment, also, we need a facility by which we can go and render these reports which are saved into report server and report server temp dB. For that, you know, the SSRS team has created a website. So they have created a website inside is is stands for Internet Information Server, which is a web server. So in that web server, you know, they have created a small functionality by which, you know, you can go and render these reports which are saved into the report server database.

So if you go to the reporting services Configuration Manager, you can see that there is something called as the web service URL. So if you click on this web service URL over here, you can see that he has given here something called as something like HTTP, the server name at Port and report server. So let's go and click on this. After that it asks for the credential. Now, these credentials are the same credentials, you know, which you had provided when you were installing SSRS. So when you were installing SQL Server, so at that time, it was saying that you know, what should be the credential.

So this is the same credential. So at this moment, I'm going to give my administrator account of my computer so I will see administrator and the password. And you can see that it is actually trying to open something inside the browser. So you can see that he's actually running it on you can see that there is actually a URL saying HTTP, my PC name, my server name slash report server. So let us wait for some time until displays something. Now, when the site is displayed over here you can see that there are lots of links which are displayed here, okay.

So, let me explain you what these links are you can see that okay, let us let us open our reporting services report. So, if you see our reporting services report you can see that and the left hand side put the solution explorer right and at the right hand side are those links right. So, if you see your SSRS It comprises of three sections, one is there is something called as a data source. The other one is something called as a data set, and then your reports, right, so, this data source and data set is saved into these two links. So, when you click on these two links, it actually takes you to the data source and data sets section. And the other all links are actually the reports, okay?

These are the report projects. So in other words, for example, if I go and deployed this SSIS customer on this report server, I will actually find one more link here saying customer SSRS. And when I click on the customer SSRS, I would see all these reports. Okay, so at this moment, I have not deployed it, so I don't see anything. Okay? Now remember that at the, at the end of the day, this URL will be accessed by the end user.

So end user, you know, will not be clicking on data source and data sets, you know, they will actually be going to the reports, right. So the first two links are really for our it is for the developers and the other links is what you will give it to the end user. Okay, so let us do one thing, let us go and deploy our report into the report server. And let us see that if we can see over here, customer SSRS SSRS or not. So let us go and copy this URL. So I'm going to go and copy the report server URL.

Let us go to Visual Studio. So let me go to Visual Studio over here. It is not maximized. Yeah, there it is. And right click on the project of the report server and go to the properties. When you go to the properties, you know, there is one link over here called as a target server URL.

So I'm going to go and paste this target server URL over here. And I will say, Okay, and now I will right click and deploy it. So, I'm going to go and right click and deploy this report. So, as you do that, you know, you would see in case everything is successful, you should see some successful messages down. So, you can see that everything has succeeded and nothing has failed. So, now, let us go to our report server and let us do a refresh.

So once I do a refresh, you can see that there is a customer SSRS displayed here. So let us click on this customer SSRS and let us see one of the reports. Let us see this manual is concerned Report. So if you remember, you know, these were the reports we were creating with the project. So remember the top hierarchy, what you see in the report server is actually the project. Okay, so there you can see our report getting displayed inside the browser.

So the end user would be interacting, you know, with this UI to see the reports, right. So end user would be interacting via the browser, and you can see the same kind of look and feel what you see in your Visual Studio is now displayed on the browser itself. Right? So there you can see my report is loading. And you can see that he's displaying me the reports, right. So at the end of the day, you're going to go and give this link this URL link to the customer to see the reports and not your Visual Studio.

Your Visual Studio is meant for development purpose, and also very quickly, you can see that all those facility of exporting this report doing a search Know what we had? All these facilities are available in this online report viewer as well. Right. Now, internally, there are two websites. One is the HTTP, your PC name slash report server. So one is this one, which we just saw.

And the other one is reports, just HTTP server name and reports. So you can see that again, when I go to http server name slash reports, I see certain kind of a UI here. And for HTTP report server, I see some different kind of a UI right. Now, the HTTP slash reports is for administration purpose, while the HTTP slash report server is for end users. So for end users, if you want to give reports, you will use the HTTP report server URL. And if you want to do administration, then you will say HTTP reports.

How again, I would like to iterate over here. Both of these websites that is HTTP slash reports and HTTP slash report server, they read the data from your report server and report server temp dB. So remember that when you say deploy, your reports physically get stored into these databases, and HTTP reports and HTTP report server are nothing but they are websites which internally go and use that database. So the HTTP reports is used to do management. And the HTTP report server is used to display reports for the end user. So you know, over here you see these folder icons, but that does not mean that your reports are stored into some kind of a physical hard disk.

So now you can see in this Reporting Services Administration website, you can configure things at the top level. That means at your project level, you can see there is something called as folder setting or if you go inside You can go to every report inside and do configuration for that report. So you can click on every reports manage, you can see that there is a managed menu here. For example, if you remember we had all these reports in our project. So let us say I go and click on this manage of this child report. So on this, you know, you can go and change, you can go and apply a new kind of security, you can go and see your data sources.

You can go and you can go and see your parameters. Right. So, basically, this administration tool, what do you see of SSRS help you to helps you to configure things regarding your reports, right. We will go into the administration part of SSRS in detail in one of the videos. At this moment. I'm just trying to make sure that you understand what every section contains.

So remember, whenever you say HTTP reports website, it is for administration purpose. If you see HTTP report server it is meant for and users to see the report. So from here, you will actually give this URL to the end user. So for example, let us say that you want to go and see the graphical report. Remember, we had some graphical reports which we are created. So what you should do is you should click on this and take this URL what you see at the top and apply it inside your website as a hyperlink or give it to the end user on an email or whatever it is.

Great. So report server for the end user and reports is nothing but your manager which helps you to manage your reports for administration purpose, right so you can see even the graphical reports are seen in the same way as they were seen inside the Visual Studio. Now due to resolution, you can see that this thing is seen down so very quickly because of resolution issues. You can see that this man who is coming down, but I'm sure that if you are in a proper resolution, they should come properly. Right. Let us go ahead and run through the SSRS Configuration Manager.

We will have a separate session on how to do administration of reports later on. So don't worry what is that in the reports Don't worry what is that in the report server? First let us try to understand the architecture. So in this video, my concentration is to understand the various components of SSRS and then we will have a in depth session later on. So in reporting services Configuration Manager, we had all these menus over here. So let us go through go through them one by one.

I have gone through some menus but let me just go through them once properly. So the first menu here says that what is the status of your SSRS services? Remember SSRS at the end of the day is a service so over here, if you go to your services dot MSC, you will see that SSRS is a separate service. Right? So yes, one is that you can go here and you can start and stop from here. But otherwise, you can do it from here as well.

The second one is a service account. Now, this SSRS service has to run inside some kind of credential, right? So this is the built in service account under which the SSRS runs. So if you go here very quickly, just to cross check. So if I go to properties, you can see that here also, he's running on inside the report server account. So that's the same thing.

The next thing is the web service URL. Okay. So this web service URL, what you see over here, you know, helps you to give the end user reports, right. So if you wish, you can go and change this URL as well. Right. So This section is meant to configure the report.

So have is okay. The next thing after this is database. So this database is the you know the the RDB, Ms two tables, two databases what we have that is report server and report server temp dB. So that is this is where you will go and configure the SSRS database. The next thing is the report manager. Remember I said one is we have the web service URL which is for the which is actually for the end users to supply reports and this one is the web service manager.

Okay. Then we have email settings. We will discuss about this email setting what it does later on. But now what happens is a lot of times you want to you know, deliver reports Okay, so or you want to actually send some kind of error. So this is where you know you'd like to give that email setting execution account, execution account and scale out deployment. Both of these menus we will talk separately later.

So don't worry on that. But let us talk about this menu here called as encryption keys. Now, if you remember I said that at the end of the day SSRS stores its reports in the, in the RDBMS database that is report server and report server temp dB. Now when you go and backup these database or when you go and maybe want to restore this database to some other server at that time, you need to have this key, okay? This key is nothing but your key which is used for encrypting those reports. Because remember that a lot of times, you know, these reports are, you know, very, very sensitive or it can have sensitive information.

So what Microsoft has done, they have created a key and anybody who wants to actually backup or restore these database anywhere else, right, he needs to have this key. So ensure that you have this key backed up. If you don't have this key, then it is very difficult to restore your report server and report server temp dB, I again repeat the statement. Without this key, you only be able to restore your report server and report server temp dB. So, because once you start checking in and tomorrow for some reason this key is not backed up, then you will have a lot of problems. So ensure to backup this key and put it into a you know into proper storage.

And then later on, you know, when you see that you want to move this report server from one server to another server, you need to give that key over here. So if you for example, if I backup now, it actually goes and gives me a file location, right and afterwards, you know, wherever I want to restore, I can say restore. So let us do a quick revision on the article. feature of SSRS you know, whatever we have learnt till now. So first thing is from Visual Studio, you need to go and provide the report server URL, right. So you need to go here to the, to the properties of SSRS.

And over here in the properties, you see this target server URL. So from here, you will actually you will actually go and provide this report server URL which you will get from this reporting services Configuration Manager, right. So, you will go and you will provide this URL and then you will check in right or you will actually deploy, so you will right click and he will say deploy. So, right click and it will say deploy, deploy. Once you say deploy, all your reports actually get stored into report server and report server temp dB. So both of these databases is where your report will get stolen.

Now, from these database there are two websites sites created in is in the web server. One is a report server. Right? So whatever is your computer name slash report server. The other one is reports or reports. Right?

So this reports website actually helps you to do management of SSRS reports, it helps you to do the administration part, while the report server is for the end user to see the reports. So that is the overall architecture of SSRS. We will go into the in depth section and we will go later on in depth into the report manager configuration. Don't worry on that, but for now, my goal is to go through the architecture. So I hope that you enjoyed this video. In this video, we were trying to understand what are the different components in SSRS?

What is the architecture of SSRS and how to do deployment in SSRS. Thank you so much.