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

Friday, March 30, 2012

KPI List Web Part in MOSS 2007 - How Do I Display an 'As of Date' For Indicators?

I have created an SQL 2005 SSAS cube with many different KPIs defined. In MOSS 2007 (SP2) I have created a site to display these various KPIs in several KPI Lists. Some of the indicators in the underlying cube are updated daily, others weekly, others quarterly, etc.

What are some ways to display to the user what date or time slice each specific indicator is "as of"?

Thanks in advance for any help you can provide.

-Steve

Hello. I do not think that there is a property in SSAS2005 that you can use for this.

The easy way is to create separate KPI:s depending on the time slice /or update window and simply name the KPI:s in SSAS2005 in this way.

I can think of ActSalesBudSalesMonth and ActSalesBudSalesYearToDate. I usually use shorter names.

Else I recommend you to find a property/information field in MOSS 2007

HTH

Thomas Ivarsson

KPI List Web Part in MOSS 2007 - How Do I Display an 'As of Date' For Indicators?

I have created an SQL 2005 SSAS cube with many different KPIs defined. In MOSS 2007 (SP2) I have created a site to display these various KPIs in several KPI Lists. Some of the indicators in the underlying cube are updated daily, others weekly, others quarterly, etc.

What are some ways to display to the user what date or time slice each specific indicator is "as of"?

Thanks in advance for any help you can provide.

-Steve

Hello. I do not think that there is a property in SSAS2005 that you can use for this.

The easy way is to create separate KPI:s depending on the time slice /or update window and simply name the KPI:s in SSAS2005 in this way.

I can think of ActSalesBudSalesMonth and ActSalesBudSalesYearToDate. I usually use shorter names.

Else I recommend you to find a property/information field in MOSS 2007

HTH

Thomas Ivarsson

Known sp3a bugs.

Hello everyone,
We have upgraded to SQL Server 2000/sp2. When a service
pack comes, generally companies wait for sometime before
they apply. This is just to avoid potential new bugs and
find out some information.
My question is: Are there any known issues with SP3a? If
yes, what they are and whether its safe to apply the
patch.
Thanks in advance,
mzeeshanWe've had it installed on a dozen servers for awhile now with no problems. I
really think the practice of releasing patches has changed in that now they
are pretty thoroughly tested prior to public release. The problem with
waiting to install it is MS releases the bug fixes in the service pack once
they release the service pack and virus writers quickly write programs to
attach the patched holes knowing that admins are reluctant to patch the
systems right away. Not sure how to combat that but it is a problem
HTH.
--
Ray Higdon MCSE, MCDBA, CCNA
--
"mzeeshan" <mzeeshan@.yahoo.com> wrote in message
news:0fbe01c38a88$c3912300$a401280a@.phx.gbl...
> Hello everyone,
> We have upgraded to SQL Server 2000/sp2. When a service
> pack comes, generally companies wait for sometime before
> they apply. This is just to avoid potential new bugs and
> find out some information.
> My question is: Are there any known issues with SP3a? If
> yes, what they are and whether its safe to apply the
> patch.
> Thanks in advance,
> mzeeshan|||Thanks for your reply. I know the problems, the SQL
slammer worm was created by someone based on a CERT
advisory. And, if I am not wrong, the patch was already
there but not installed by users till it became the
problem. Fortunately, we were spared as all our boxes
were inaccessible from outside.
The flip side is the creation of new problems generated
by service packs themselves. If I can recall, there was a
service pack (may be 4 or 5) with WindowsNT that created
so many problems that a new one (sp6) was quickly
released.
Its good to hear that MS is more careful now.
Thanks anyway,
mzeeshan
>--Original Message--
>We've had it installed on a dozen servers for awhile now
with no problems. I
>really think the practice of releasing patches has
changed in that now they
>are pretty thoroughly tested prior to public release.
The problem with
>waiting to install it is MS releases the bug fixes in
the service pack once
>they release the service pack and virus writers quickly
write programs to
>attach the patched holes knowing that admins are
reluctant to patch the
>systems right away. Not sure how to combat that but it
is a problem
>HTH.
>--
>Ray Higdon MCSE, MCDBA, CCNA
>--
>"mzeeshan" <mzeeshan@.yahoo.com> wrote in message
>news:0fbe01c38a88$c3912300$a401280a@.phx.gbl...
>> Hello everyone,
>> We have upgraded to SQL Server 2000/sp2. When a service
>> pack comes, generally companies wait for sometime
before
>> they apply. This is just to avoid potential new bugs
and
>> find out some information.
>> My question is: Are there any known issues with SP3a?
If
>> yes, what they are and whether its safe to apply the
>> patch.
>> Thanks in advance,
>> mzeeshan
>
>.
>|||Didn't mean to sound insensitive to the concerns of reluctant admins, just
pointing it out, there's wisdom in waiting if you can afford to..everything
in one way or another is a cost-benefit analysis :)
GL
--
Ray Higdon MCSE, MCDBA, CCNA
--
"mzeeshan" <mzeeshan@.yahoo.com> wrote in message
news:2052f01c38a9e$01b99030$a601280a@.phx.gbl...
> Thanks for your reply. I know the problems, the SQL
> slammer worm was created by someone based on a CERT
> advisory. And, if I am not wrong, the patch was already
> there but not installed by users till it became the
> problem. Fortunately, we were spared as all our boxes
> were inaccessible from outside.
> The flip side is the creation of new problems generated
> by service packs themselves. If I can recall, there was a
> service pack (may be 4 or 5) with WindowsNT that created
> so many problems that a new one (sp6) was quickly
> released.
> Its good to hear that MS is more careful now.
> Thanks anyway,
> mzeeshan
> >--Original Message--
> >We've had it installed on a dozen servers for awhile now
> with no problems. I
> >really think the practice of releasing patches has
> changed in that now they
> >are pretty thoroughly tested prior to public release.
> The problem with
> >waiting to install it is MS releases the bug fixes in
> the service pack once
> >they release the service pack and virus writers quickly
> write programs to
> >attach the patched holes knowing that admins are
> reluctant to patch the
> >systems right away. Not sure how to combat that but it
> is a problem
> >
> >HTH.
> >
> >--
> >Ray Higdon MCSE, MCDBA, CCNA
> >--
> >"mzeeshan" <mzeeshan@.yahoo.com> wrote in message
> >news:0fbe01c38a88$c3912300$a401280a@.phx.gbl...
> >> Hello everyone,
> >>
> >> We have upgraded to SQL Server 2000/sp2. When a service
> >> pack comes, generally companies wait for sometime
> before
> >> they apply. This is just to avoid potential new bugs
> and
> >> find out some information.
> >>
> >> My question is: Are there any known issues with SP3a?
> If
> >> yes, what they are and whether its safe to apply the
> >> patch.
> >>
> >> Thanks in advance,
> >> mzeeshan
> >
> >
> >.
> >|||SP3 has all of MS's security fixes for SQL Server as well... I'd advise
going to it as quickly as you feel comfortable.
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"mzeeshan" <mzeeshan@.yahoo.com> wrote in message
news:0fbe01c38a88$c3912300$a401280a@.phx.gbl...
> Hello everyone,
> We have upgraded to SQL Server 2000/sp2. When a service
> pack comes, generally companies wait for sometime before
> they apply. This is just to avoid potential new bugs and
> find out some information.
> My question is: Are there any known issues with SP3a? If
> yes, what they are and whether its safe to apply the
> patch.
> Thanks in advance,
> mzeeshan

Monday, March 12, 2012

Key export: exception

Recently as part of the process of upgrading to RS SP2 I followed the
normal procedure to export my crypto keys. Unfortunately instead of
providing me with the key file, it gave me an "External component has
thrown an exception" message on the console. At the same time the RS
service shut itself down.
As it turns out, I already have the crypto key tucked away on a CD. I
went ahead and updated to RS SP2 successfully, but the key export is
still giving me trouble.
The trace log isn't doesn't appear to contain any error information.
Has anyone run into this before? How did you resolve it?I've googled and looked through the knowledgebase, but still haven't
found a solution to this.|||We also had this problem. The solution for us was to amend the
web.config file to <customErrors mode="Off"> (we were using a custom
error handler). If you have custom errors "On" then turn them off and
seeing what happens. It didn't fix the problem but it did give a
proper error page showing what the actual problem was and on what line
of code, etc. Good luck.

key attribute translation

Hello!

I've migrated a AS2000 database with "translations" (using the naughty trick with MEMBER_CAPTION) to a 2005 SP2 database, so far, everything is working fine, translations are displayed.
But now I need to create new dimensions with translations on the key attribute of each dim and I don't see where to do this in BIDS. You can define translations for other 'regular' attributes but not on a key attribute... I've generated a XMLA script from my converted from 2K dims and I can see the translation definitions on the key attributes so I know it's possible. Question is now: how to do this in BIDS ? Any idea ?
no idea ? Sad

Friday, March 9, 2012

Kerberos authentication doesn't work properly

Hi,
We have a SQL 2005 with SP2 configured with Kerberos authentication. We've
created a SOAP end-point and have set-up SPNs for the domain account that's
running the SQL service.
When browsing to this end-point via http://server.domain.com/name?WSDL -
browser just shows blank page. No errors being logged anywhere on the SQL
server. By looking at the requests and responses from client to the server,
IE makes only one Anonymous request to the server and then stops. Both the
client machine and the SQL server are in the same domain and the TCP port is
enabled on the SQL server and can be pinged from the client machine. The SPN
is set-up with the correct server name.
We downloaded a test application from the net and this app can get to this
same URL by Kerberos. The reson we know that Kerberos worked is because we
saw the ticket generated on the server. This client app is running on the
same client machine where we tried the IE. Version of IE is 7 and its a XP
machine.
When we turned the authentication to Integrated on SQL server, IE works in
Kerberos mode. Again, we saw the ticket generated but when we set
authentication to Kerberos only, IE is failing to pass Kereberos ticket and
render the WSDL.
Any idea about what could be going on ? How do we turn on some logging for
this SQL end-point ?
Thanks
-JigneshThis presentation might help:
http://support.microsoft.com/default.aspx?kbid=887682
Todd C
"Jignesh Shah" wrote:

> Hi,
> We have a SQL 2005 with SP2 configured with Kerberos authentication. We've
> created a SOAP end-point and have set-up SPNs for the domain account that'
s
> running the SQL service.
> When browsing to this end-point via http://server.domain.com/name?WSDL -
> browser just shows blank page. No errors being logged anywhere on the SQL
> server. By looking at the requests and responses from client to the server
,
> IE makes only one Anonymous request to the server and then stops. Both the
> client machine and the SQL server are in the same domain and the TCP port
is
> enabled on the SQL server and can be pinged from the client machine. The S
PN
> is set-up with the correct server name.
> We downloaded a test application from the net and this app can get to this
> same URL by Kerberos. The reson we know that Kerberos worked is because we
> saw the ticket generated on the server. This client app is running on the
> same client machine where we tried the IE. Version of IE is 7 and its a XP
> machine.
> When we turned the authentication to Integrated on SQL server, IE works in
> Kerberos mode. Again, we saw the ticket generated but when we set
> authentication to Kerberos only, IE is failing to pass Kereberos ticket an
d
> render the WSDL.
> Any idea about what could be going on ? How do we turn on some logging for
> this SQL end-point ?
> Thanks
> -Jignesh

Wednesday, March 7, 2012

Keep Together property not working on table

I'm using SSRS sp2 and have a report which has a table which spans the width
of the report. I set the 'KeepTogether' property on this table to True, but
I have detail rows from this table spanning 2 pages. I thought this prop
would keep them together and force a pagebreak before. There's only about
10 rows total and a height of 0.3 for each row.
Also, I assume this property (when it works) will only effect the detail
rows. what I really want to keep the entire table together including
header, detail and footer rows. is there a way to not-allow a pagebreak
anywhere in the table?
Thanks
--
moondaddy@.nospam.nospamHi moondaddy,
Would you please send me a sample page with datasource? I understand the
information may be sensitive to you, my direct email address is
v-mingqc@.online.microsoft.com, you may send the file to me directly and I
will keep secure.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi. I found a workaround to this problem which may help you. As far as I can
tell, the table "keep together" property only applies to individual detail
rows i.e. if you have multiple detail lines, they can still span pages.
If you can use a single detail row with multiple lines, the keep together
will work on those lines.
To create a detail row with multile lines, you can use the
"environment.newline()" function in expressions within the detail row. (This
function does not appear to be documented in an obvious location).
e.g. an expression like . . .
=Fields!line_1.value & environment.newline() & Fields!line_2.value
will result in two lines, but using a single detail row.
Hope this helps. It won't help with keeping your whole table on one page.
Reporting Services seems to be deficient in this area.
"moondaddy" wrote:
> I'm using SSRS sp2 and have a report which has a table which spans the width
> of the report. I set the 'KeepTogether' property on this table to True, but
> I have detail rows from this table spanning 2 pages. I thought this prop
> would keep them together and force a pagebreak before. There's only about
> 10 rows total and a height of 0.3 for each row.
> Also, I assume this property (when it works) will only effect the detail
> rows. what I really want to keep the entire table together including
> header, detail and footer rows. is there a way to not-allow a pagebreak
> anywhere in the table?
> Thanks
> --
> moondaddy@.nospam.nospam
>
>|||Thanks. These sound like good tips. I wish they were better documented.
(sorry for the late reply. just got back from a long leave of absence)
--
moondaddy@.nospam.nospam
"Glen" <Glen@.discussions.microsoft.com> wrote in message
news:BBCEBF2B-9146-410B-AB6D-2039A103C275@.microsoft.com...
> Hi. I found a workaround to this problem which may help you. As far as I
> can
> tell, the table "keep together" property only applies to individual detail
> rows i.e. if you have multiple detail lines, they can still span pages.
> If you can use a single detail row with multiple lines, the keep together
> will work on those lines.
> To create a detail row with multile lines, you can use the
> "environment.newline()" function in expressions within the detail row.
> (This
> function does not appear to be documented in an obvious location).
> e.g. an expression like . . .
> =Fields!line_1.value & environment.newline() & Fields!line_2.value
> will result in two lines, but using a single detail row.
> Hope this helps. It won't help with keeping your whole table on one page.
> Reporting Services seems to be deficient in this area.
> "moondaddy" wrote:
>> I'm using SSRS sp2 and have a report which has a table which spans the
>> width
>> of the report. I set the 'KeepTogether' property on this table to True,
>> but
>> I have detail rows from this table spanning 2 pages. I thought this prop
>> would keep them together and force a pagebreak before. There's only
>> about
>> 10 rows total and a height of 0.3 for each row.
>> Also, I assume this property (when it works) will only effect the detail
>> rows. what I really want to keep the entire table together including
>> header, detail and footer rows. is there a way to not-allow a pagebreak
>> anywhere in the table?
>> Thanks
>> --
>> moondaddy@.nospam.nospam
>>|||I'm having a similar problem with the KeepTogether option on a table. I have
a report with a simple 4 row table. The pages break fine in the HTML
rendering but when I export to PDF, the pages will break in between detail
rows of a single table at times.
Has anyone come up with a viable solution to this problem? I'm running
Reporting Services for SQL Server 2000 SP1.
Thanks.
PhilK
"moondaddy" wrote:
> Thanks. These sound like good tips. I wish they were better documented.
> (sorry for the late reply. just got back from a long leave of absence)
> --
> moondaddy@.nospam.nospam
> "Glen" <Glen@.discussions.microsoft.com> wrote in message
> news:BBCEBF2B-9146-410B-AB6D-2039A103C275@.microsoft.com...
> > Hi. I found a workaround to this problem which may help you. As far as I
> > can
> > tell, the table "keep together" property only applies to individual detail
> > rows i.e. if you have multiple detail lines, they can still span pages.
> >
> > If you can use a single detail row with multiple lines, the keep together
> > will work on those lines.
> >
> > To create a detail row with multile lines, you can use the
> > "environment.newline()" function in expressions within the detail row.
> > (This
> > function does not appear to be documented in an obvious location).
> >
> > e.g. an expression like . . .
> >
> > =Fields!line_1.value & environment.newline() & Fields!line_2.value
> >
> > will result in two lines, but using a single detail row.
> >
> > Hope this helps. It won't help with keeping your whole table on one page.
> > Reporting Services seems to be deficient in this area.
> >
> > "moondaddy" wrote:
> >
> >> I'm using SSRS sp2 and have a report which has a table which spans the
> >> width
> >> of the report. I set the 'KeepTogether' property on this table to True,
> >> but
> >> I have detail rows from this table spanning 2 pages. I thought this prop
> >> would keep them together and force a pagebreak before. There's only
> >> about
> >> 10 rows total and a height of 0.3 for each row.
> >>
> >> Also, I assume this property (when it works) will only effect the detail
> >> rows. what I really want to keep the entire table together including
> >> header, detail and footer rows. is there a way to not-allow a pagebreak
> >> anywhere in the table?
> >>
> >> Thanks
> >>
> >> --
> >> moondaddy@.nospam.nospam
> >>
> >>
> >>
>
>

Monday, February 20, 2012

kb934459 has anyone applied this post sp2 hotfix?

I'm running sql server 2005 servicepack 2 build 3042 (32bit)
has anyone had any problems with this hotfix??
http://support.microsoft.com/kb/934459Wasn't 3052 the bad release of sp2? I'vfe got 3054 on 3 boxes and no issues with them.|||How do I patch up to 3054?

I am having such a time trying to figure out which cummulative hotfix to apply. I applied the hotfix mentioned in my original post and brought my release up to 9.0.3159 - now I read somewhere that this might not be a stable release? Can you suggest what level or release should I patch my 9.0.3042 Production box to?? and how do I find it?|||Here' are links that describe the issue:
http://support.microsoft.com/kb/933508 and
http://www.mssqltips.com/tip.asp?tip=1195

After M$oft issued the first sp2, they pulled it down for a short while then put a corrected version up on the web site. you should be able to go here and get the latest sp2:
http://support.microsoft.com/kb/913089|||Thanks for all your help Tom. Looks like I'll have to install the update to SP2 mentioned in KB933508 because I have the old one - version 9.00.3042.00

Once I do that. can you tell me how to find the latest post sp2 hotfix?|||Hotfixes are usually handled by Microsoft PSM on a per case basis. Many times they require a password to open. You will have to contact Microsoft, which means being prepared to pay for the incident, but if the problem is a M$oft issue, they will not charge you for the hotfix.|||I did not know that. I thought that if someone opened an issue that they fixed with a hotfix - they then made it available to everyone.|||Microsoft does not release hotfixes because they are often very, very specific and only fix one part of a larger problem. The hotfixes do get analyzed and carried forward into service packs (SPs), but in a very different way that has much more design and QA work than a hotfix gets.

Hotfixes are intended to be "one off" solutions to a specific problem for a specific customer. Hotfixes generally should not be shared or applied unless there is a specific, critical need.

-PatP|||At http://www.sqlsecurity.com, they maintain a (pretty current) list of SQL patches and hot fixes.

The ones that are marked "PSS Only" are not intended to be made publicly available. They are available only by calling MS support and getting (from them) a link to the hotfix (which is zipped and protected by a password which changes every 7 days).

There are, however, some hotfixes which are NOT password protected and may be downloaded without calling M$.

Regards,

hmscott

PS. I should note that calling MS for any of these hotfixes does not cost anything.|||Great info. Thank you for everything!