Thursday, May 21, 2009

Navigations in Reporting Services


We can make three types navigations in SQL Server Reporting Services



  1. Navigating in same report(Book Marking)

  2. Navigating to another Report(Jump to Report)

  3. Navigation Website(Jum to URL)


Any text box or image item can be used for intrareport or interreport navigation,
for navigation to external resources like web pages and documents, and also to send
e-mail. All of these features are enabled by using navigation properties that can
be specified in the Textbox Properties or Image Properties dialog.



1.Navigating in same report(Book Marking)


This can be achieve with Book Marking in Reports.




Abookmark is a text box or image in a report that can be used as a navigational
link. If you want to allow the user to click an item and navigate to another item,
assign a bookmark value to each of the target items.




First, open the Textbox Properties dialog by right-clicking the text box and selecting
Properties from the pop-out menu. In the Textbox Properties dialog, then switch
to the Navigation tab.

To enable navigation to a bookmark, set the Jump to bookmark property to the target
bookmark.


Using bookmarks to navigate within a report is very easy to do. Each report item
has a BookMark property that may be assigned a unique value.

After adding bookmarks to any target items, use the Jump to Bookmark Selection list
to select the target bookmark in the Properties for the Source item. This allows
the user to navigate to items within the same report.







2.Navigating to another Report(Jump to Report)


This powerful feature enables a text box or image to be used as a link
to another report by passing parameter values to the target report. The target report
can consist of a specific record or multiple records, depending on the parameters
passed to the target report.




The following example uses a Products by Category report.That means the Products
report shows the list of all Products and the Category Report shows the information
about perticular Product. Name text box is used to link to a report that will display
the details of a single product record. The Product Details report is very simple.
This report accepts a ProductID parameter to filter the records and narrow down
to the record requested.


First, open the Textbox Properties dialog by right-clicking the text box and selecting
Properties from the pop-out menu. In the Textbox Properties dialog, then switch
to the Navigation tab.

Then select the Jump to report radio button, and select the target report from the
drop-down list.



Any parameters you need to pass to the target report can be configured using the
Parameters button. In the Parameters dialog, parameters for the target report are
selected in the Parameter Name column. Values supplied from the current report are
provided in the Parameter Value column, If you need to give a cue to the user that
the item is a link, you may want to display text with an underline.





When a product name is clicked on the main report, the viewer redirects to the detailed
report for the specific product by passing the ProductID parameter value.




3.Navigation Website(Jum to URL)


The Jump to URL option can be used to navigate to practically any report
or document content on your report server, and files, folders, and applications
in your intranet environment or on the World Wide Web. It can also be set to an
expression that uses links stored in a database, custom code, or any other values.
It’s more accurate to say that any URI (Uniform Resource Identifier) can be used
since a web request is not limited
only to a web page or document. With some creative programming, queries, and expressions,
your reports could be designed to navigate to a web page, document, e-mail address,
Web service request, or a custom web application, directed by data or custom expressions.



Wednesday, May 20, 2009

SQL Server Editions

Understanding SQL Server 2005 Editions







A major part of the installation planning process is determining the SQL Server 2005 edition you need to use. SQL Server 2005 offers five editions—two of which come in either 32-bit or 64-bit versions—each designed for a specific environment. Determining the proper edition to install is critical for meeting the functionality needs of your current environment as well as any future needs you might expect. Here is a description of each edition:






SQL Server 2005 Enterprise Edition (32-bit and 64-bit)




Enterprise Edition is designed to support the largest enterprise online transaction processing (OLTP) environments, highly complex data-analysis requirements, data-warehousing systems, and active Web sites. DBAs designing large database installations should consider only Enterprise Edition.






SQL Server 2005 Standard Edition (32-bit and 64-bit)




Standard Edition includes the essential functionality needed for e-commerce, data warehousing, and lineof- business solutions that most small- and medium-sized organizations  use. Organizations with databases that will contain large amounts of data but do not need installations with all the features of Enterprise Edition might want to consider Standard Edition.







SQL Server 2005 Workgroup Edition (32-bit only)




Workgroup Edition is the datamanagement solution for small organizations that need a database that has no limits on size or number of users and has the capability to serve as a back end to small Web servers and departmental or branch-office operations. DBAs working with small amounts of data on smaller servers might want to consider using Workgroup Edition.






SQL Server 2005 Developer Edition (32-bit and 64-bit)




Developer Edition includes all the functionality of SQL Server 2005 Enterprise Edition, but it is licensed for use as a development and test system, not as a production server. Developer Edition is suited for developers in larger companies who need to develop applications that will use Enterprise Edition but who do not want to install Enterprise Edition on development or test servers.






SQL Server 2005 Express Edition (32-bit only)




SQL Server Express is a free, easyto-use, and simple-to-manage database that can be redistributed to function as the client database as well as a basic server database. Express Edition is usually suited only for very small data sets. Developers who are developing applications that require a small data store should consider using Express Edition. Express Edition also makes a suitable replacement for Microsoft Access databases.

Majic Tables in SQL Server

What are Majic Tables in SQL Server?





Whenever a trigger fires in response to the INSERT,DELETE,or UPDATE statement,two special tables are created.These are the inserted and the deleted tables.They are also referred to as the magic tables.These are the conceptual tables and are similar in structure to the table on which trigger is defined(the trigger table).


While using triggers these Inserted & Deleted tables (called as magic tables) will be created automatically.

The inserted table contains a copy of all records that are inserted in the trigger table.

The deleted table contains all records that have been deleted from deleted from the trigger table.

Whenever any updation takes place,the trigger uses both the inserted and deleted tables.



When we insert any record then that record will be added into this Inserted table initially, similarly while updating a record a new entry will be inserted into Inserted table & old value will be inserted into Deleted table. In the case of deletion of a record then it will insert that record into the Deleted table.



Note that the Magic Table does not contain the information about the columns of the data-type text, ntext, or image. Attempting to access these columns will cause an error.


There was an error in this gadget

About Me

My photo
I am a Postgraduate in Mathematics from Sri Venkateswara University. I made this blog to share and gain knowledge and basically to express myself. The purpose of making this site was also to make my work available at a single point on Internet. I started programming with dBase and FoxPro, then C and C++. I am a developer working with Software Company.

This Day in History