MS Excel has import functionality.
You can also use SQL Server 2008 R2's (even earlier versions can be used) Import and Export Wizard.
A more generic tool and that is especially meant or Import/Export of even more complicated situations is MS SQL Server Integration Services.
The following design diagram shows roughly what you should be considering. If you use left two items you will be exporting from Excel to SQL Server and if you use the right two items you will be importing from SQL Server to Excel.
This is all very simply explained in my book which I do recommend.
The readers of my articles on several forums asks questions regarding something or the other and I do answer them promptly. However I feel the answers should be shared among a larger group of people. I think this blog will make this possible.
Showing posts with label Report Processing in SQL server 2008. Show all posts
Showing posts with label Report Processing in SQL server 2008. Show all posts
Monday, June 21, 2010
Thursday, June 18, 2009
How do I create a simple table in a database on SQL Server 2008 and populate it?
Let us say you want to create a table such as the one shown in this example (PrincetonTemp2) and populate it with some values. There is more than one way to create a table in SQL Server 2008.This one uses Create Table query to create a table. You then edit the table to insert the values. Values can also be inserted using code. In here, the query creates the table and you then manually insert the data.
Step 1: Create table using the query
In SQL Server 2008 right click the database in which you want to create a table and choose New Query
Type in the Query window as shown in the next figure. Check the syntax of the query by clicking the icon at the far right of the figure. Execute the query by clicking the (!)Execute.
You will have created a table called PrincetonTemp2. You can see it in the Tables node after you refresh the database by right clicking the database node and choosing Refresh from the list.
Step 2: Populate the table by editing the table :
Right click the table in the Management Studio after expanding the database node.

From the drop-down click on Edit Top 200 Rows.
In the table that shows up fill in the data you want to insert. The data has to match the query you used to create the table. One line inserted is shown in the next figure.
Step 1: Create table using the query
In SQL Server 2008 right click the database in which you want to create a table and choose New Query
Type in the Query window as shown in the next figure. Check the syntax of the query by clicking the icon at the far right of the figure. Execute the query by clicking the (!)Execute.
You will have created a table called PrincetonTemp2. You can see it in the Tables node after you refresh the database by right clicking the database node and choosing Refresh from the list.
Step 2: Populate the table by editing the table :
Right click the table in the Management Studio after expanding the database node.

From the drop-down click on Edit Top 200 Rows.
In the table that shows up fill in the data you want to insert. The data has to match the query you used to create the table. One line inserted is shown in the next figure.
Wednesday, July 9, 2008
How are reports processed on a Report Server in SSRS 2008?
In SSRS 2008 reports are processed on the Report Server instance (not IIS) configured during installation and uses the two special relational databases as the backend, ReportServer and ReportServerTempdb.
Reports are procesed when they are requested by the user. These requests can take the following forms:
On-demand ->
User accessing report triggers report processor on the report server or, user working on a model-based report triggers report processor.
Demand for a cached report->
User accessing a cached copy triggers this type of processing if cached copy has expired.
From schedulig and delivery processor->
Schedules and delivery events trigger this type of processing.
In all these cases the published report definition file is retrieved. This file defines both data and formatiing information. The data from the data processing extension is merged with the formatting information to produce the report in an intermediate format. The rendering extension takes this report in the intermediate format, processes it and produces the report rendered in a device specific format. During this process it may also process information that were not processed earlier like expressions in the report.
In the case of report being requested due to user working with a model, the steps are similar except that the model is interrogated to provide report and model data.
In essence core processors, the several specialized extensions, and the backend work together to produce a finished report.
Reports are procesed when they are requested by the user. These requests can take the following forms:
On-demand ->
User accessing report triggers report processor on the report server or, user working on a model-based report triggers report processor.
Demand for a cached report->
User accessing a cached copy triggers this type of processing if cached copy has expired.
From schedulig and delivery processor->
Schedules and delivery events trigger this type of processing.
In all these cases the published report definition file is retrieved. This file defines both data and formatiing information. The data from the data processing extension is merged with the formatting information to produce the report in an intermediate format. The rendering extension takes this report in the intermediate format, processes it and produces the report rendered in a device specific format. During this process it may also process information that were not processed earlier like expressions in the report.
In the case of report being requested due to user working with a model, the steps are similar except that the model is interrogated to provide report and model data.
In essence core processors, the several specialized extensions, and the backend work together to produce a finished report.
Subscribe to:
Posts (Atom)




