Downloading Crystal Reports missing Components for SSRS 2008

Recently i have assigned a task to add crystal reports in SSRS 2008 and open their design in it. I have tried one of my colleague's system and i will see report design successfully opened in it. But when i have tried to open it in my system it returns binary format of file. I have uninstall SSRS 2008 and install it again but fails. Even i have tried to use SSRS 2008 R2 and i did not find my required result.

Then during search i found missing components needs to install in SSRS 2008. I have used following link to download CR package for SSRS.

http://resources.businessobjects.com/support/additional_downloads/runtime.asp#09

List of components requried to install with sSRS 2008 can be
- Runtime Pre-requisites
- Microsoft .NET Framework v3.5 (x64)
- Microsoft Visual Studio 2008 64bit Prerequisites (x64)
- Microsoft Document Explorer 2008
- Microsoft Visual Studio Web Authoring Component
- Microsoft Visual Studio 2008
- Microsoft .NET Compact Framework 2.0 SP2
- Microsoft .NET Compact Framework 3.5
- Microsoft Visual Studio Tools for the Microsoft Office system (version 3.0 Runtime)
- Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System Runtime
- Microsoft SQL Server Compact 3.5
- Microsoft SQL Server Compact 3.5 Design Tools
- Microsoft SQL Server Compact 3.5 For Devices
- Windows Mobile 5.0 SDK R2 for Pocket PC
- Windows Mobile 5.0 SDK R2 for Smartphone
- Microsoft Device Emulator version 3.0 (x64)
- Microsoft SQL Server 2005 Express Edition
- Microsoft Visual Studio 2008 Remote Debugger (x64)
- Crystal Reports Basic for Visual Studio 2008
- Crystal Reports Basic 64-Bit Runtime for Visual Studio 2008
- Microsoft Windows SDK for Visual Studio 2008 Tools (x64)
- Microsoft Windows SDK for Visual Studio 2008 Headers and Libraries (x64)
- Microsoft Windows SDK for Visual Studio 2008 Win32 Tools (x64)
- Microsoft Windows SDK for Visual Studio 2008 .NET Framework Tools (x64)
- Microsoft Windows SDK for Visual Studio 2008 SDK Reference Assemblies and IntelliSense (x64)
- Microsoft SQL Publishing Wizard

More blogs are
http://msmvps.com/blogs/martinpoon/archive/2008/03/09/installing-components-full-installation-of-visual-studio-2008-professional-edition.aspx

Izdenda reporting Tool: An easy way to generate a report.

Build a sample report.
http://www.youtube.com/watch?v=N3uY9hi2UNQ

Handling report from sample dashboard
http://www.youtube.com/watch?v=5UT6pwMT3lM

SSRS is also a powerfull tool but Izenda have much more options.

Searching Multi key word in SQL Server 2005

There are many types of searches operators applies in SQL Server SQL to find related data. One of the most famous opeator is Like operator. When we need to search any character from a string we use like opeator and append %% with parameter like

Select * from tbl where columnname like '%xyz%';

Now if user wants to enable google type search and ask for searching Multicharacters at a time. Then we have another solution for that type of search example as follows

Now we can see we have I and a in parameter string and using cross apply query can easly search both values.

How it works
1. fn_Split is a self made function that return a table with one column and it has all values seperated by comma. In above example we have 2 rows with "I" and "a" values respectivly. 
2. Cross apply duplicates all data against each value of fn_split. In this example 10 rows generated five with joins for "I" and five with "a" .
3. Using "item" column in where clause instead of parameter name search for both characters from 10 rows.
4. Distinct clause removes duplicate records from result set.

Now if we need to impliment this in muliple tables and columns as mostly required we can easily get our required result. as shown in example

NOTE: Remember this is a space hungry query as much values you have in your parameter, data will be duplicated but this will help you to enable google like search in your application.

Preventing table changes from SSMS 2008

I got a lot of questions from developers about SSMS 2008 error. Error message generates while saving any changes from designer studio from SSMS table designer.

Here is the solution for that.

We need to setup properties for Management Studio and then we can make changes to our table through designer.
Go to Tools -- > options.

 
click designer tab and check "table and designers tab" on left side we have following options.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
un-check prevent saving changes that require table re-creation and click Ok.
 
you can also use other powerfull features like create change script is one.
 
cheers:)

Using wildcard characters in Search feature for SQL Server

Like operator is one the built in function use for search function for different requirements. For example user wants to search all data from a table where name contains “q” in its string. User use like operator with ‘%q%’ but if anyone wants to search all data that lies between ”m” and “q” then we need to do some difference technique to get required result. SQL server uses few wildcard characters for this kind of situations.

We have following wildcard characters available

·         Percent (%)

Find any length that contain mentioned characters in the string. Like %s search sha,shamas,whats etc.

·         Underscore (_)

Find exactly one character in mentioned string. Like _ha would found sha but could not find shamas etc.

·         Square Brackets ([])

Find any range of characters mentioned between brackets like [m-q] return all data between m to q. we can also use [m,n,o,p,q]

·         Caret (^)

Any character not in mentioned range like [^m-q].

For performance issue try to avoid not in clause and like clause because it did not include indexes in search.

To understand we have following table structure and data for our example.

/****** Object:  Table [dbo].[code]    Script Date: 07/22/2010 16:34:43 ******/

IF  EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[code]') AND type in (N'U'))

DROP TABLE [dbo].[code]

GO

CREATE TABLE [dbo].[code](

      [id] [int] IDENTITY(1,1) NOT NULL,

      [name] [varchar](50) NULL

) ON [PRIMARY]

GO

INSERT INTO [code] ([id],[name])VALUES(1,'this')

INSERT INTO [code] ([id],[name])VALUES(2,'that')

INSERT INTO [code] ([id],[name])VALUES(3,'Which')

INSERT INTO [code] ([id],[name])VALUES(4,'What')

INSERT INTO [code] ([id],[name])VALUES(5,'shamas')

INSERT INTO [code] ([id],[name])VALUES(6,'qamar')

INSERT INTO [code] ([id],[name])VALUES(7,'atif')

INSERT INTO [code] ([id],[name])VALUES(8,'kashif')

INSERT INTO [code] ([id],[name])VALUES(9,'this')

INSERT INTO [code] ([id],[name])VALUES(10,'that')

INSERT INTO [code] ([id],[name])VALUES(11,'Which')

INSERT INTO [code] ([id],[name])VALUES(12,'What')

INSERT INTO [code] ([id],[name])VALUES(13,'shamas')

INSERT INTO [code] ([id],[name])VALUES(14,'qamar')

INSERT INTO [code] ([id],[name])VALUES(15,'atif')

INSERT INTO [code] ([id],[name])VALUES(16,'kashif')

GO

Now try this query

select * from code where name like '%m%'

select * from code where name like '%q%'

You can get required result for data containing “m” to “q”.

Results are:

 

By combining different search operator we can get required query as follows

select * from code where name like '[k-t]%'

and results are

You can view all data between k,l,m,n,o,p,q,r,s,t characters.

You can also use caret character as

select * from code where name  like '[^k-t]%'

and got this result

  
Summary: wildcard characters can be very use full feature in SQL server search operator.

Finding dependency using SQL Server 2005

I got a requirement today that a developer needs to return all dependent procedures on a table "ABC" because he has changed a column name and need to change it on all its dependent objects.

I gave him first solution. He can use SSMS feature to find dependent objects.
Step1: to get this you can go to required table --> right click -- > click view dependcy

Step2: On clicking view dependency you can see dependent procedures and tables of mentioned table or procedure.

After some time developer came to me and thanks for this help but he wants to know some SQL for this work.

I have given him following query that retun all dependent procedures that contains its required table name or column name. This query also return those procedures which use required table in a dynamic statement.

Using first query he can get all procedures. While 2nd and 3rd query return required table or column name from mentioned database.

HOPE! THIS BLOG HELPS

Reducing SQL Server Locks from SQL Server Performance

1. Use appropriate locking level

you can override how SQL Server performs locking on a table by using the SP_INDEXOPTION command. Below is an example of code you can run to tell SQL Server to use page locking, not row locks, for a specific table:

SP_INDEXOPTION 'table_name', 'AllowRowLocks', FALSE
GO
SP_INDEXOPTION 'table_name', 'AllowPageLocks', FALSE
GO
This code turns off both row and page locking for the table, thus only table locking is available.

2. Keep all Transact-SQL transactions as short as possible.
3. An often overlooked cause of locking is an I/O bottleneck.
4. To help reduce the amount of time tables are locked, which hurts concurrency and performance, avoid interleaving reads and database changes within the same transaction.
5. Any conditional logic, variable assignment, and other related preliminary setup should be done outside of transactions
6. Encapsulate all transactions within stored procedures
7. If you have a client application that needs to "check-out" data


for more information in detail please review:

SET DEADLOCK_PRIORITY (Transact-SQL)

SET DEADLOCK_PRIORITY { LOW | NORMAL | HIGH | | @deadlock_var | @deadlock_intvar }

::= { -10 | -9 | -8 | … | 0 | … | 8 | 9 | 10 }


LOW

Specifies that the current session will be the deadlock victim if it is involved in a deadlock and other sessions involved in the deadlock chain have deadlock priority set to either NORMAL or HIGH or to an integer value greater than -5. The current session will not be the deadlock victim if the other sessions have deadlock priority set to an integer value less than -5. It also specifies that the current session is eligible to be the deadlock victim if another session has set deadlock priority set to LOW or to an integer value equal to -5.

NORMAL

Specifies that the current session will be the deadlock victim if other sessions involved in the deadlock chain have deadlock priority set to HIGH or to an integer value greater than 0, but will not be the deadlock victim if the other sessions have deadlock priority set to LOW or to an integer value less than 0. It also specifies that the current session is eligible to be the deadlock victim if another other session has set deadlock priority to NORMAL or to an integer value equal to 0. NORMAL is the default priority.

HIGH

Specifies that the current session will be the deadlock victim if other sessions involved in the deadlock chain have deadlock priority set to an integer value greater than 5, or is eligible to be the deadlock victim if another session has also set deadlock priority to HIGH or to an integer value equal to 5.



Is an integer value range (-10 to 10) to provide 21 levels of deadlock priority. It specifies that the current session will be the deadlock victim if other sessions in the deadlock chain are running at a higher deadlock priority value, but will not be the deadlock victim if the other sessions are running at a deadlock priority value lower than the value of the current session. It also specifies that the current session is eligible to be the deadlock victim if another session is running with a deadlock priority value that is the same as the current session. LOW maps to -5, NORMAL to 0, and HIGH to 5.

@deadlock_var

Is a character variable specifying the deadlock priority. The variable must be set to a value of 'LOW', 'NORMAL' or 'HIGH'. The variable must be large enough to hold the entire string.

@deadlock_intvar

Is an integer variable specifying the deadlock priority. The variable must be set to an integer value in the range (-10 to 10).


Remarks

Deadlocks arise when two sessions are both waiting for access to resources locked by the other. When an instance of SQL Server detects that two sessions are deadlocked, it resolves the deadlock by choosing one of the sessions as a deadlock victim. The current transaction of the victim is rolled back and deadlock error message 1205 is returned to the client. This releases all of the locks held by that session, allowing the other session to proceed.

Which session is chosen as the deadlock victim depends on each session's deadlock priority:

* If both sessions have the same deadlock priority, the instance of SQL Server chooses the session that is less expensive to roll back as the deadlock victim. For example, if both sessions have set their deadlock priority to HIGH, the instance will choose as a victim the session it estimates is less costly to roll back.
* If the sessions have different deadlock priorities, the session with the lowest deadlock priority is chosen as the deadlock victim.

SET DEADLOCK_PRIORITY is set at execute or run time and not at parse time.

DECLARE @deadlock_var NCHAR(3);
SET @deadlock_var = N'LOW';

SET DEADLOCK_PRIORITY @deadlock_var;
GO


for more detail :

Understanding sp_who SQL Server procedure status

sp_who Provides information about current users, sessions, and processes in an instance of the Microsoft SQL Server Database Engine.


1. dormant. SQL Server is resetting the session.
2. running. The session is running one or more batches. When Multiple Active Result Sets (MARS) is enabled, a session can run multiple batches.
3. background. The session is running a background task, such as deadlock detection.
4. rollback. The session has a transaction rollback in process.
5. pending. The session is waiting for a worker thread to become available.
6. runnable. The session's task is in the runnable queue of a scheduler while waiting to get a time quantum.
7. spinloop. The session's task is waiting for a spinlock to become free.
8. suspended. The session is waiting for an event, such as I/O, to complete.

Understanding sp_who SQL Server procedure

sp_who provides information about current users, sessions, and processes in an instance of the Microsoft SQL Server Database Engine.

exec sp_who

A blocking process, which may have an exclusive lock, is one that is holding resources that another process needs.

In case of parallel processing, subthreads are created for the specific session ID. The main thread is indicated as spid = and ecid =0. The other subthreads have the same spid = , but with ecid > 0.

In SQL Server 2000 and later, all orphaned distributed transactions are assigned the session ID value of '-2'. Orphaned distributed transactions are distributed transactions that are not associated with any session ID.

SQL Server 2000 and later reserves session ID values from 1 through 50 for internal use, and session ID values 51 or higher represent user sessions.
By default user sees only the current session processes or you need VIEW SERVER STATE permission on the server to see all executing sessions on the instance of SQL Server.

Following are sp_who columns information

1. spid (smallint) Session ID
2. ecid (smallint) Execution context ID of a given thread associated with a specific session ID. i.e. 0,1,2,3,…n. values >0 represents sub-thread.
3. Status(nchar(30)) Process status.
4. Loginame(nchar(128)) Login name associated with the particular process.
5. Hostname(nchar(128)) Host or computer name for each process.
6. Blk(char(5)) Session ID for the blocking process only, if one exists. Otherwise, this column is zero. This column will return a '-2' for the blocking orphaned transaction.
7. Dbname(nchar(128)) Database used by the process.
8. Cmd(nchar(16)) Database Engine command (Transact-SQL statement, internal Database Engine process, and so on) executing for the process.
9. request_id(int) ID for requests running in a specific session.

Examples

Listing all current processes
USE master;
GO
EXEC sp_who;
GO

Listing a specific user's process
USE master;
GO
EXEC sp_who 'janetl';
GO

Displaying all active processes
USE master;
GO
EXEC sp_who 'active';
GO

Displaying a specific process identified by a session ID
USE master;
GO
EXEC sp_who '10' --specifies the process_id;
GO

you can get more information from http://msdn.microsoft.com/en-us/library/ms174313.aspx

Features Supported by the Editions of SQL Server 2008

I got this information from MSDN.

Features Supported by the Editions of SQL Server 2008

 Scalability

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
Partitioning	Yes
Data compression	Yes
Resource governor	Yes
Partition table parallelism	Yes

 High Availability

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
Multi-instance support	50	16	16	16	16	16	16
Online system changes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Log shipping	Yes	Yes	Yes	Yes
Database mirroring2	Yes (full)	Yes (safety full only)	Witness only	Witness only	Witness only	Witness only	Witness only
Failover clustering	Operating system maximum1	2 nodes
Dynamic AWE	Yes	Yes
Failover without client configuration	Yes	Yes
Automatic corruption recovery from mirror	Yes	Yes
Database snapshots	Yes
Fast recovery	Yes
Online indexing	Yes
Online restore	Yes
Mirrored backups	Yes
Hot add memory	Yes
Online configuration of P2P nodes	Yes
Hot add CPU	Yes
Backup compression	Yes

1 Windows Server 2003 supports a maximum of 8 failover cluster nodes. Windows Server 2008 supports a maximum of 16 failover cluster nodes.

 Security

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
C2 audit mode	Yes	Yes	Yes	Yes	Yes	Yes	Yes
SQL Server auditing	Yes
Transparent database encryption	Yes
ISV encryption (off-box key management)	Yes

 Replication

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
Merge replication	Yes	Yes	Subscriber only¹	Subscriber only	Subscriber only	Subscriber only	Subscriber only
Transactional replication	Yes	Yes	Subscriber only¹	Subscriber only	Subscriber only	Subscriber only	Subscriber only
Snapshot replication	Yes	Yes	Subscriber only	Subscriber only	Subscriber only	Subscriber only	Subscriber only
SQL Server change tracking	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Heterogeneous subscribers	Yes	Yes
Oracle publishing	Yes
P2P transactional replication	Yes

¹If an instance of WorkGroup is used as a Publisher, it supports a maximum of 25 subscriptions to all merge publications, and five subscriptions to all transactional publications. It supports an unlimited number of subscriptions to snapshot publications.

 Manageability

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
User instances					Yes	Yes	Yes
Dedicated admin connection	Yes	Yes	Yes	Yes	Yes (Under trace flag)	Yes (Under trace flag)	Yes (Under trace flag)
Policy-Based Management	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Policy-Based Management automation	Yes	Yes	Yes	Yes
Policy-Based Management best practices policies	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Performance data collection and warehouse	Yes	Yes	Yes	Yes
Standard performance reports	Yes	Yes
Plan guides	Yes	Yes
Plan freezing for plan guides	Yes	Yes
Distributed partition views	Yes
Parallel index operations	Yes
Automatic query-to-indexed-view matching	Yes
Parallel database backup checksum check	Yes
Database mail	Yes	Yes	Yes	Yes
SQL Server Migration Assistant1	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Maintenance plans	Yes	Yes	Yes	Yes

 Management Tools

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
SQL Server management objects (SMO)	Yes	Yes	Yes	Yes	Yes	Yes	Yes
SQL Server Configuration Manager	Yes	Yes	Yes	Yes	Yes	Yes	Yes
SQL CMD (command prompt tool)	Yes	Yes	Yes	Yes	Yes	Yes	Yes
SQL Server Management Studio	Yes	Yes	Yes	Yes (Basic version)		Yes (Basic Version)	Yes (Basic version)
SQL Server Profiler	Yes	Yes	Yes	Yes
SQL Server Agent	Yes	Yes	Yes	Yes
Database Engine Tuning Advisor	Yes	Yes	Yes	Yes
Microsoft Operations Manager Pack	Yes	Yes	Yes	Yes

 Development Tools

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
Microsoft Visual Studio Integration	Yes	Yes	Yes	Yes	Yes	Yes	Yes
SQL query and edit and design tools	Yes	Yes	Yes
IntelliSense (Transact-SQL and MDX)	Yes	Yes	Yes		No (SSMS is not installed with this edition)	Yes	Yes
Version control support	Yes	Yes	Yes
Business Intelligence Development Studio	Yes	Yes
MDX edit, debug, and design tools	Yes	Yes

 Programmability

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
Common language runtime (CLR) integration	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Native XML support	Yes	Yes	Yes	Yes	Yes	Yes	Yes
XML indexing	Yes	Yes	Yes	Yes	Yes	Yes	Yes
MERGE capabilities	Yes	Yes	Yes	Yes	Yes	Yes	Yes
FILESTREAM support	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Date and Time data types	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Internationalization support	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Full-text search	Yes	Yes	Yes	Yes			Yes
Specification of language in query	Yes	Yes	Yes	Yes			Yes
Service Broker (messaging)	Yes	Yes	Yes	Client only	Client only	Client only	Client only
XML/A support	Yes	Yes
Web services (HTTP/SOAP endpoints)	Yes	Yes

 Spatial and Location Services

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
Spatial indexes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Geodetic data type	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Advanced spatial libraries	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Standards-based spatial support	Yes	Yes	Yes	Yes	Yes	Yes	Yes

 Integration Services

SQL Server Standard or Enterprise is required to design and run Integration Services packages. The Integration Services features that are installed by Workgroup, Web, and Express are only for use by the SQL Server Import and Export Wizard.

Feature	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
SQL Server Import and Export Wizard, and the basic Integration Services features required by the wizard	Yes	Yes	Yes	Yes	Yes	Yes	Yes
SSIS Designer including VSTA scripting	Yes	Yes
Integration Services service, wizards, and command prompt utilities	Yes	Yes
Basic tasks and transformations in addition to those used by the Import and Export Wizard	Yes	Yes
Log providers and logging	Yes	Yes
Data profiling tools	Yes	Yes
Additional sources and destinations: Raw File source XML source DataReader destination Raw File destination Recordset destination SQL Server Compact destination SQL Server destination	Yes	Yes
Advanced sources, transformations, and destinations: Data Mining Query transformation Fuzzy Lookup and Fuzzy Grouping transformations Term Extraction and Term Lookup transformations Data Mining Model Training destination Dimension Processing destination Partition Processing destination	Yes

 Data Warehouse Creation

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
Create cubes without a database	Yes	Yes
Auto-generate staging and data warehouse schema	Yes	Yes
Attribute relationship designer	Yes	Yes
Efficient aggregation designers	Yes	Yes

 Data Warehouse Scale and Performance

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
Change data capture	Yes
Star join query optimization	Yes
Scalable read-only AS configuration	Yes
Proactive caching	Yes
Auto parallel partition processing	Yes
Partitioned cubes	Yes
Distributed partitioned cubes	Yes

 Multi-Dimensional Analytics

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
SQL Server Analysis Services service	Yes	Yes
SQL Server Analysis Services backup	Yes	Yes
General performance/scale improvements	Yes	Yes
Dimension, attribute relationship, aggregate, and cube design improvements	Yes	Yes
Personalization extensions	Yes	Yes
Financial aggregations	Yes
Custom rollups	Yes
Semi-additive measures	Yes
Writeback dimensions	Yes
Linked measures and dimensions	Yes
Binary and compressed XML transport	Yes
Account intelligence	Yes
Perspectives	Yes
Analysis Services shared, scalable databases	Yes

 Data Mining

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
Standard algorithms	Yes	Yes
Data mining tools: wizards, editors, query builders	Yes	Yes
Cross validation	Yes
Models on filtered subsets of mining structure data	Yes
Time series: custom blending between ARTXP and ARIMA models	Yes
Time series: prediction with new data	Yes
Unlimited concurrent data mining queries	Yes
Advanced configuration and tuning for algorithms	Yes
Algorithm plug-in API	Yes
Parallel model processing	Yes
Time series: cross-series prediction	Yes
Unlimited attributes for association rules	Yes
Sequence prediction	Yes
Multiple prediction targets for naïve Bayes, neural network, and logistic regression	Yes

 Reporting

Feature Name	Enterprise	Standard	Workgroup	Web	Express	Express Tools	Express Advanced
Report server	Yes	Yes	Yes	Yes			Yes
Report Designer	Yes	Yes	Yes	Yes			Yes
Report Manager	Yes	Yes	Yes	Yes (Report Manager)			Yes (Report Manager)
Role-based security	Yes	Yes	Yes (Fixed roles)	Yes (Fixed roles)			Yes (Fixed roles)
Ad-hoc reporting (Report builder)	Yes	Yes	Yes
Word export and enhanced text formatting	Yes	Yes	Yes	Yes			Yes
Enterprise-scale reporting engine	Yes	Yes	Yes	Yes			Yes
IIS-agnostic report deployment	Yes	Yes	Yes	Yes			Yes
Updated management tools	Yes	Yes	Yes	Yes			Yes
Report definition customization extension (RDCE)	Yes	Yes	Yes	Yes			Yes
SharePoint integration	Yes	Yes
Enhanced SSRS gauges and charting	Yes	Yes	Yes	Yes			Yes
Custom authentication	Yes	Yes	Yes	Yes
Export to Excel, PDF, and images	Yes	Yes	Yes	Yes			Yes
Remote and non-relational data source support	Yes	Yes
E-mail and file share delivery	Yes	Yes
Report history, scheduling, subscriptions, and caching	Yes	Yes
Data source, delivery, and rendering extensibility	Yes	Yes
Scale out (Web farms)	Yes
Infinite click through	Yes
Data-driven subscriptions	Yes
Reporting Services memory limits	OS Maximum	OS Maximum	4 GB	4 GB			4 GB