Sql Server 2005

Tuesday, July 27, 2004

SQL Server Express and MSDE - Differences


SQL Server Express and MSDE - Differences










This URL explains the major differences between SQL Server Express and MSDE
(Microsoft Desktop Engine)

















































SQL Server Express
2005
MSDE
2000
Application XCopy support Feature not present
No DTS DTS runtime present
Easy deployment because of no MDAC MDAC is part of install
MSI only, good servicing story MSI and MSM, servicing of MSM hard
Client Replication for Transactional, Merge, and snapshot Merge/snapshot publication supported in addition to replication
subscription
Robust Setup UI Basic setup UI
No agent Agent present
Supports Windows 2000 SP4, Windows XP SP1, and Windows
2003
Supports Windows 98, Windows Me, Windows 2000, Windows XP, Windows
NT4, and Windows 2003
CLR support No CLR support
GUI tools provided No GUI tools
Database size limit: 4G Database size limit: 2G
1 CPU, 1GB RAM 2 CPU, 2GB RAM
No throttle Workload throttle enforced
Deep integration with Visual Studio Basic integration with Visual
Studio


Read more ..



Regards,
Mitesh Mehta
Microsoft Certified Professional
miteshvmehta@gmail.com

Saturday, July 17, 2004

Learn: What's New in FOR XML in Microsoft SQL Server 2005

Learn: What's New in FOR XML in Microsoft SQL Server 2005









This article details the major new capabilities of the server-side FOR XML
clause in the next version of SQL Server. These enable to further enhance the
XML support in applications and to write easy-to-maintain relational data-to-XML
aggregations.


the URL is http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/forxml2k5.asp msdn.microsoft.com/library/default.asp? url=/library/en-us/dnsql90/html/forxml2k5.asp



Regards,
Mitesh Mehta
Microsoft Certified Professional



Monday, July 12, 2004

Article: Integrating Analysis Services with Reporting Services

Article: Integrating Analysis Services with Reporting Services










This article explains How
to create a compelling solutions using Analysis Services reports and answers
analytical questions to improve traditional reporting scenarios.

The ability to define
reports, manage reports, and convert them to various formats can enhance many
Analysis Services implementations.


http://msdn.microsoft.com/sql/default.aspx?pull=/library/en-us/dnsql2k/html/olapasandrs.asp



Regards,
Mitesh Mehta


Thursday, July 08, 2004

SQL Server Reporting => Understanding Report Layout and Rendering

SQL Server Reporting => Understanding Report Layout and Rendering









A report consists of three main areas: a page header, a page footer,
and the body. The page header and footer repeat the same content at the
top and bottom of each page of the report. You can place report items
such as images, text boxes, and lines in headers and footers. The body
of the report contains the report data. In addition to the report items
that you can place in a header or footer, you can place data regions,
which display the data from a dataset, anywhere in the report body.


The placement of report items in a report is completely freeform.
With Reporting Services, you are not limited to "bands" of data in a
report. You can place data regions with different sets of data
side-by-side. Certain report items can also contain other report items.
For data regions, this means that you can nest groups of data within
other groups.


Rendering


When you run a report, the report server combines the layout from
the report definition with the data from the data source, and renders
the report in a specified format. The report server uses extensions to
perform much of this work: a data processing extension is used to
retrieve the data based on the type of data source, and a rendering
extension is used to provide report output based on the selected
format. Different extensions can change the way data is processed and
the report is rendered.


Pagination


Pagination in a report is determined by the page size of the report
and any page breaks placed on report items. Rendering extensions that
support page size, such as image and PDF, format the data in the report
to fit within each page. Rendering extensions that do not support page
size, such as HTML, render all data between page breaks on a single
page. All rendering extensions that support page breaks on items will
start a new page after each page break in the report.



Regards


Mitesh Mehta


miteshvmehta@gmail.com



Wednesday, July 07, 2004

A List Of Date Formatting String in Reporting Services Design Reports








A List Of Date Formatting String in Reporting Services Design Reports


Formatting Dates


The following table describes common .NET date formatting strings.








































Format string


Name


d


Short date


D


Long date


t


Short time


T


Long time


f


Full date/time (short time)


F


Full date/time (long time)


g


General date/time (short time)


G


General date/time (long time)


M or m


Month day


R or r


RFC1123 pattern


Y or y


Year month


You can also a use custom formatting strings, for example, dd/MM/yy.


SQL Server Rep Services => Working with Items in a Report








Working with Items in a Report


A report in Reporting Services uses report items to display data and
graphical elements. In addition to the data regions table, matrix,
list, and chart, report items also include text box, image, line,
rectangle, and subreport.


Text Box


Text boxes display all text data in a report. A table or matrix cell
include a text boxes by default to display data. Text boxes can be
placed anywhere on a report and can contain labels, fields, or
calculated data. You use expressions to define data in text boxes.


Image


Images display binary image data in a report. An image report item
can use a URL to display an image stored on a Web server, display
embedded image data, or display an image from binary data in a
database. Reporting Services supports .bmp, .jpeg, .gif, and .png
files.


Line


Lines are graphical elements that you can place anywhere on a page.
A line is defined with a start and end point and can have a number of
styles (for example, weight and color) assigned to it. A line has no
data associated with it.


Rectangle


Rectangles can be used in two ways: as a graphical element and as a
container for other report items. When you place report items within a
rectangle, you can move them with the rectangle. This is useful for
keeping numerous text boxes and other items together in a report.


Subreport


A subreport is an item in a report that points to another report on
the report server. The report that the subreport refers to can be a
full report that can also run on its own, or it can be a report that
looks best when embedded within the main report. When you define a
subreport, you can also define parameters to filter data in the
subreport.


When deciding whether to use a subreport, you may want to consider
using a data region instead. Because the report server processes each
instance of a subreport as a separate report, performance can be an
issue. Data regions provide much of the same functionality and
flexibility as subreports, but with better performance.


Item Properties


All items in a report, including groups, table and matrix columns
and rows, the above items, and the report itself, have properties
associated with it. These properties govern the appearance and behavior
of the item. For information about the properties associated with an
item, see the documentation for that item.


Regards
Mitesh Mehta