Showing posts with label sp2. Show all posts
Showing posts with label sp2. Show all posts

Friday, February 24, 2012

Column Layout

I am just getting started with reportingservices and have it installed (SP2)
on my development machine (Win XP Pro SP2).
I created a simple report and set the layout to be 2 columns across.
It print previews as two columns in VS designer, but when viewing through
the report web interface, it only displays as a single column.
However, if I export it to PDF, it then renders the 2 columns correctly.
Is there a way to fix this?
Also, does anyone know of a news server that has this group on it, so it can
be accessed via Outlook Express?
It is not available on news.microsoft.com
TIAThe new group is located at msnews.microsoft.com .
Have you tried the sample reports to see if they work correctly?
"AVG" <AVG@.discussions.microsoft.com> wrote in message
news:72ED551C-4D61-4A5D-88F0-3402BFFA969E@.microsoft.com...
>I am just getting started with reportingservices and have it installed
>(SP2)
> on my development machine (Win XP Pro SP2).
> I created a simple report and set the layout to be 2 columns across.
> It print previews as two columns in VS designer, but when viewing through
> the report web interface, it only displays as a single column.
> However, if I export it to PDF, it then renders the 2 columns correctly.
> Is there a way to fix this?
> Also, does anyone know of a news server that has this group on it, so it
> can
> be accessed via Outlook Express?
> It is not available on news.microsoft.com
> TIA
>|||Thanks for the quick reply Mark. Outlook Express is much quicker than the
web interface.
The only sample report that does not work is the Foodmart. Apparently MS
forgot to include the datasource for it.
Anyway, none of the samples use the multiple column layout. They are all
single column.
I am not referring to simply two columns of data like productid and name. I
am referring to the columns property of the layout tab of the report
properties.
--
Alphonse Giambrone
Email: a-giam at customdatasolutions dot us
"Mark" <mis@.ifcfabricsnospam.com> wrote in message
news:ONsEgGNTFHA.2828@.TK2MSFTNGP10.phx.gbl...
> The new group is located at msnews.microsoft.com .
> Have you tried the sample reports to see if they work correctly?
> "AVG" <AVG@.discussions.microsoft.com> wrote in message
> news:72ED551C-4D61-4A5D-88F0-3402BFFA969E@.microsoft.com...
>>I am just getting started with reportingservices and have it installed
>>(SP2)
>> on my development machine (Win XP Pro SP2).
>> I created a simple report and set the layout to be 2 columns across.
>> It print previews as two columns in VS designer, but when viewing through
>> the report web interface, it only displays as a single column.
>> However, if I export it to PDF, it then renders the 2 columns correctly.
>> Is there a way to fix this?
>> Also, does anyone know of a news server that has this group on it, so it
>> can
>> be accessed via Outlook Express?
>> It is not available on news.microsoft.com
>> TIA
>|||I think this must be by design. Mine does the same, previews in 1 column but
exports & prints in multiple columns.
Maybe MSFT can comment.
"AVG" <NOSPAMa-giam@.example.invalid> wrote in message
news:emfUAQNTFHA.3696@.TK2MSFTNGP15.phx.gbl...
> Thanks for the quick reply Mark. Outlook Express is much quicker than the
> web interface.
> The only sample report that does not work is the Foodmart. Apparently MS
> forgot to include the datasource for it.
> Anyway, none of the samples use the multiple column layout. They are all
> single column.
> I am not referring to simply two columns of data like productid and name.
> I am referring to the columns property of the layout tab of the report
> properties.
> --
> Alphonse Giambrone
> Email: a-giam at customdatasolutions dot us
>
> "Mark" <mis@.ifcfabricsnospam.com> wrote in message
> news:ONsEgGNTFHA.2828@.TK2MSFTNGP10.phx.gbl...
>> The new group is located at msnews.microsoft.com .
>> Have you tried the sample reports to see if they work correctly?
>> "AVG" <AVG@.discussions.microsoft.com> wrote in message
>> news:72ED551C-4D61-4A5D-88F0-3402BFFA969E@.microsoft.com...
>>I am just getting started with reportingservices and have it installed
>>(SP2)
>> on my development machine (Win XP Pro SP2).
>> I created a simple report and set the layout to be 2 columns across.
>> It print previews as two columns in VS designer, but when viewing
>> through
>> the report web interface, it only displays as a single column.
>> However, if I export it to PDF, it then renders the 2 columns correctly.
>> Is there a way to fix this?
>> Also, does anyone know of a news server that has this group on it, so it
>> can
>> be accessed via Outlook Express?
>> It is not available on news.microsoft.com
>> TIA
>>
>|||I wouldn't mind so much if it did print correctly, but for me it does not
(except through the VS designer).
The only way I get the two columns (via reportserver) is to export to pdf.
Ok, Microsoft, any answers?
--
Alphonse Giambrone
Email: a-giam at customdatasolutions dot us
"Mark" <mis@.ifcfabricsnospam.com> wrote in message
news:%23hLRKkNTFHA.3308@.TK2MSFTNGP14.phx.gbl...
>I think this must be by design. Mine does the same, previews in 1 column
>but exports & prints in multiple columns.
> Maybe MSFT can comment.
> "AVG" <NOSPAMa-giam@.example.invalid> wrote in message
> news:emfUAQNTFHA.3696@.TK2MSFTNGP15.phx.gbl...
>> Thanks for the quick reply Mark. Outlook Express is much quicker than the
>> web interface.
>> The only sample report that does not work is the Foodmart. Apparently MS
>> forgot to include the datasource for it.
>> Anyway, none of the samples use the multiple column layout. They are all
>> single column.
>> I am not referring to simply two columns of data like productid and name.
>> I am referring to the columns property of the layout tab of the report
>> properties.
>> --
>> Alphonse Giambrone
>> Email: a-giam at customdatasolutions dot us
>>
>> "Mark" <mis@.ifcfabricsnospam.com> wrote in message
>> news:ONsEgGNTFHA.2828@.TK2MSFTNGP10.phx.gbl...
>> The new group is located at msnews.microsoft.com .
>> Have you tried the sample reports to see if they work correctly?
>> "AVG" <AVG@.discussions.microsoft.com> wrote in message
>> news:72ED551C-4D61-4A5D-88F0-3402BFFA969E@.microsoft.com...
>>I am just getting started with reportingservices and have it installed
>>(SP2)
>> on my development machine (Win XP Pro SP2).
>> I created a simple report and set the layout to be 2 columns across.
>> It print previews as two columns in VS designer, but when viewing
>> through
>> the report web interface, it only displays as a single column.
>> However, if I export it to PDF, it then renders the 2 columns
>> correctly.
>> Is there a way to fix this?
>> Also, does anyone know of a news server that has this group on it, so
>> it can
>> be accessed via Outlook Express?
>> It is not available on news.microsoft.com
>> TIA
>>
>>
>|||Multi-column layout is not supported in the HTML rendering extension.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"AVG" <AVG@.discussions.microsoft.com> wrote in message
news:72ED551C-4D61-4A5D-88F0-3402BFFA969E@.microsoft.com...
>I am just getting started with reportingservices and have it installed
>(SP2)
> on my development machine (Win XP Pro SP2).
> I created a simple report and set the layout to be 2 columns across.
> It print previews as two columns in VS designer, but when viewing through
> the report web interface, it only displays as a single column.
> However, if I export it to PDF, it then renders the 2 columns correctly.
> Is there a way to fix this?
> Also, does anyone know of a news server that has this group on it, so it
> can
> be accessed via Outlook Express?
> It is not available on news.microsoft.com
> TIA
>|||Thanks Brian,
I am sure MS has a reason for it.
Is there any documentation available on features that are not supported in
the various rendering extensions?
One could waste a lot of time trying to figure things like this out.
--
Alphonse Giambrone
Email: a-giam at customdatasolutions dot us
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
news:%23c4zeEUTFHA.1040@.TK2MSFTNGP10.phx.gbl...
> Multi-column layout is not supported in the HTML rendering extension.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "AVG" <AVG@.discussions.microsoft.com> wrote in message
> news:72ED551C-4D61-4A5D-88F0-3402BFFA969E@.microsoft.com...
>>I am just getting started with reportingservices and have it installed
>>(SP2)
>> on my development machine (Win XP Pro SP2).
>> I created a simple report and set the layout to be 2 columns across.
>> It print previews as two columns in VS designer, but when viewing through
>> the report web interface, it only displays as a single column.
>> However, if I export it to PDF, it then renders the 2 columns correctly.
>> Is there a way to fix this?
>> Also, does anyone know of a news server that has this group on it, so it
>> can
>> be accessed via Outlook Express?
>> It is not available on news.microsoft.com
>> TIA
>|||There is a section in the docs but it is unfortunately not very complete.
I'll pass this suggestion to our doc team.
The reason it is not supported is that there is no easy way to calculate the
page size like there is on physical pages. I suppose we could take the
definition page breaks and cut it in half but this would result in different
sizes for each page.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"AVG" <NOSPAMa-giam@.example.invalid> wrote in message
news:%23OYpquXTFHA.3840@.tk2msftngp13.phx.gbl...
> Thanks Brian,
> I am sure MS has a reason for it.
> Is there any documentation available on features that are not supported in
> the various rendering extensions?
> One could waste a lot of time trying to figure things like this out.
> --
> Alphonse Giambrone
> Email: a-giam at customdatasolutions dot us
>
> "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
> news:%23c4zeEUTFHA.1040@.TK2MSFTNGP10.phx.gbl...
>> Multi-column layout is not supported in the HTML rendering extension.
>> --
>> Brian Welcker
>> Group Program Manager
>> Microsoft SQL Server Reporting Services
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "AVG" <AVG@.discussions.microsoft.com> wrote in message
>> news:72ED551C-4D61-4A5D-88F0-3402BFFA969E@.microsoft.com...
>>I am just getting started with reportingservices and have it installed
>>(SP2)
>> on my development machine (Win XP Pro SP2).
>> I created a simple report and set the layout to be 2 columns across.
>> It print previews as two columns in VS designer, but when viewing
>> through
>> the report web interface, it only displays as a single column.
>> However, if I export it to PDF, it then renders the 2 columns correctly.
>> Is there a way to fix this?
>> Also, does anyone know of a news server that has this group on it, so it
>> can
>> be accessed via Outlook Express?
>> It is not available on news.microsoft.com
>> TIA
>>
>

Thursday, February 16, 2012

Column Chart Issue in MSRS 2005

Hi,
I have report created with Reporting Service 2000 SP2 designer. This
contains a Column Chart with Simple Column type. I had selected
GraySacle Pallete for my report. I have max 4 columns in my report.
When I deployed the report on MSRS 2000 SP2 Report Server it is showing
correctly. The style of the columns in legend and that appearing in
chart are correct.
When I deploy the same report on MSRS 2005 SP1 Report Server its
showing in-correct. The style of the columns in legend and that
appearing in chart are not matching. For e.g I have a column
representing "Data Unavailable" in legend it shows as "Front
Slash" on reports in the chart this DataUnavailable appears 7 times
(representing week) first time it appears as "Front Slash" 2nd time
"Back Slash" 3rd time "Straight horizontal line", 4th
"Vertical lines" ...and so on all 7 times it appears different.
Is this a bug in 2005. Its working fine in MSRS 2000 SP2
What is a solution for making it consistent on MSRS 2005?
Thanks in advance for any kind of help.
Regards,
ManojHi
Do anyone know the reason for this behaviour?
I tried creating the same report in Reporting Service 2005 SP1
designer. Still same result. GrayScale Pallete shows wrong column graph
other than those shown in legends
Any kind of help in this regards will be very usefull.
Regards,
Manoj
Manoj wrote:
> Hi,
> I have report created with Reporting Service 2000 SP2 designer. This
> contains a Column Chart with Simple Column type. I had selected
> GraySacle Pallete for my report. I have max 4 columns in my report.
> When I deployed the report on MSRS 2000 SP2 Report Server it is showing
> correctly. The style of the columns in legend and that appearing in
> chart are correct.
> When I deploy the same report on MSRS 2005 SP1 Report Server its
> showing in-correct. The style of the columns in legend and that
> appearing in chart are not matching. For e.g I have a column
> representing "Data Unavailable" in legend it shows as "Front
> Slash" on reports in the chart this DataUnavailable appears 7 times
> (representing week) first time it appears as "Front Slash" 2nd time
> "Back Slash" 3rd time "Straight horizontal line", 4th
> "Vertical lines" ...and so on all 7 times it appears different.
> Is this a bug in 2005. Its working fine in MSRS 2000 SP2
> What is a solution for making it consistent on MSRS 2005?
> Thanks in advance for any kind of help.
> Regards,
> Manoj

Friday, February 10, 2012

Collation Questions SQL Server 2005 SP2

A few collation questions on SQL Server 2005 SP2, which I'll call SQLS.

The default collation for SQLS is apparently SQL_Latin1_General_CP1_CI_AS.

I wish to use a variation of this, SQL_Latin1_General_CP1_CS_AI
collation, but there is no such collation returned from
fn_helpcollations(). Also, if I try to use this collation in
a CREATE DATABASE stmt, SQLS yells about it.

I see that there is a Latin1_General_CS_AI. What effects are there
in using this collation? The SQL_* collations are SQL collations,
while non-SQL_* collations are Windows collations, yes? SQLS runs
only on Windows, so am I safe in using Latin1_General_CS_AI? What
does the CP1 in the SQL collation signify? Am I asking for trouble?
-----------
Assuming that I set Latin1_General_CS_AI (or any other case-sensitive
collation) at the database level, I believe my DDL/DML for that database
also becomes case-sensitive. How can I specify that I want ONLY my data
access to be case-sensitive, and not my DDL/DML? I don't want to have
to remember to type "select * from MyCamelCase" when "mycamelcase"
should work.

Any help appreciated.

A new SQLS DBA..

ajaj (ronald@.mcdonalds.com) writes:

Quote:

Originally Posted by

A few collation questions on SQL Server 2005 SP2, which I'll call SQLS.
>
The default collation for SQLS is apparently SQL_Latin1_General_CP1_CI_AS.


The default collation when you install SQL Server depends on your regional
settings. SQL_Latin1_General_CP1_CI_AS is what you get when your regional
settings is English (US).

Quote:

Originally Posted by

I see that there is a Latin1_General_CS_AI. What effects are there
in using this collation? The SQL_* collations are SQL collations,
while non-SQL_* collations are Windows collations, yes? SQLS runs
only on Windows, so am I safe in using Latin1_General_CS_AI? What
does the CP1 in the SQL collation signify? Am I asking for trouble?


You should be fine. About everywhere else in the world when you install SQL
Server, the default collation is a Windows collation. For instance, in my
case it's Finnish_Swedish_CI_AS (but I always change it to
Finnish_Swedish_CS_AS.)

Windows collations are drawn from Windows and Unicode, and the sorting for
varchar and nvarchar data is the same (save that nvarchar includes far more
characters). SQL collations on the other hand are completely different
for varchar and nvarchar. For varchar they are just an 8-bit character
set, while for nvarchar they are Unicode. The flip side of this is since
they for varchar only have 255 charcters, operations with varchar are
quite a bit faster with SQL collations than with Windows collations (save
binary collations). However, there are also potential for performance
disasters with SQL collations if you join varchar and nvarchar that
are less likly to occur with Windows collations.

Quote:

Originally Posted by

Assuming that I set Latin1_General_CS_AI (or any other case-sensitive
collation) at the database level, I believe my DDL/DML for that database
also becomes case-sensitive. How can I specify that I want ONLY my data
access to be case-sensitive, and not my DDL/DML? I don't want to have
to remember to type "select * from MyCamelCase" when "mycamelcase"
should work.


You would have to set the database collation to be one that fits your
preference for identifiers and then explcitly set the collation for each
column to be case-sensitive.

My strong recommendation is that you should always develop on a
case-sensitive collation. If you develop on a case-insensitive collation,
and the customer then insists on case-sensitive, you may have a complete
mess to sort out.

Personally, I don't see the point of using MyCamelCase, if you don't
care to remember how you originally defined it.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Thanks for your response. This confirms what we suspected.

Do you have any idea why there is no SQL_Latin1_General_CP1_CS_AI
collation? Can I get it somewhere?

Erland Sommarskog wrote:

Quote:

Originally Posted by

aj (ronald@.mcdonalds.com) writes:

Quote:

Originally Posted by

>A few collation questions on SQL Server 2005 SP2, which I'll call SQLS.
>>
>The default collation for SQLS is apparently SQL_Latin1_General_CP1_CI_AS.


>
The default collation when you install SQL Server depends on your regional
settings. SQL_Latin1_General_CP1_CI_AS is what you get when your regional
settings is English (US).
>

Quote:

Originally Posted by

>I see that there is a Latin1_General_CS_AI. What effects are there
>in using this collation? The SQL_* collations are SQL collations,
>while non-SQL_* collations are Windows collations, yes? SQLS runs
>only on Windows, so am I safe in using Latin1_General_CS_AI? What
>does the CP1 in the SQL collation signify? Am I asking for trouble?


>
You should be fine. About everywhere else in the world when you install SQL
Server, the default collation is a Windows collation. For instance, in my
case it's Finnish_Swedish_CI_AS (but I always change it to
Finnish_Swedish_CS_AS.)
>
Windows collations are drawn from Windows and Unicode, and the sorting for
varchar and nvarchar data is the same (save that nvarchar includes far more
characters). SQL collations on the other hand are completely different
for varchar and nvarchar. For varchar they are just an 8-bit character
set, while for nvarchar they are Unicode. The flip side of this is since
they for varchar only have 255 charcters, operations with varchar are
quite a bit faster with SQL collations than with Windows collations (save
binary collations). However, there are also potential for performance
disasters with SQL collations if you join varchar and nvarchar that
are less likly to occur with Windows collations.
>

Quote:

Originally Posted by

>Assuming that I set Latin1_General_CS_AI (or any other case-sensitive
>collation) at the database level, I believe my DDL/DML for that database
>also becomes case-sensitive. How can I specify that I want ONLY my data
>access to be case-sensitive, and not my DDL/DML? I don't want to have
>to remember to type "select * from MyCamelCase" when "mycamelcase"
>should work.


>
You would have to set the database collation to be one that fits your
preference for identifiers and then explcitly set the collation for each
column to be case-sensitive.
>
My strong recommendation is that you should always develop on a
case-sensitive collation. If you develop on a case-insensitive collation,
and the customer then insists on case-sensitive, you may have a complete
mess to sort out.
>
Personally, I don't see the point of using MyCamelCase, if you don't
care to remember how you originally defined it.
>
>

|||aj (ronald@.mcdonalds.com) writes:

Quote:

Originally Posted by

Do you have any idea why there is no SQL_Latin1_General_CP1_CS_AI
collation?


No. Maybe they never developed this combiniation for SQL collations, but got
it for free with Windows collation. fn_helpcollations tells me that there
are no CS_AI SQL collation at all.

Quote:

Originally Posted by

Can I get it somewhere?


No. There is support for adding collations.

If you feel strongly about it, you can submit a suggestion on
http://connect.microsoft.com/SqlServer/Feedback.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx