differences in record counts

Hello all,

I have a problem concerning differences in record counts between the measure group and the fact table.
for debugging such a case in Analysis Services 2000, I would have run process on the cube, copy the SQL statement that was generated and debug it using Query Analyser. in sql 2005, I tried doing that but got the sql statement without the joins to the dimensions so no much help in that...

does anyone have a suggestion on how to debug such a case?

Thanks,

Momo

In SSAS 2005, the fact table is not joined to the dimensions during processing unless you implemented a reference dimension and opted to materialize it. In this situation, you will see a join to the intermediate dimension table.

B.

|||

Bryan C. Smith wrote:

In SSAS 2005, the fact table is not joined to the dimensions during processing unless you implemented a reference dimension and opted to materialize it. In this situation, you will see a join to the intermediate dimension table.

B.

So can anyone explain why the poster is observing dropped rows?

In my case I am finding the cubes are not showing any financials. Fact tables are populated correctly. Dimensions appear to be joined correctly - but I understand this wouldnt matter anyway?

Is there a way to see how the cube process is getting its data? Is there a way to check the integrity of a data source view? What is the consequence of incorrectly joining tables in your data source view?

Debugging in AS 2000 seemed much easier!

|||

When you process the cube, you have access to the queries submitted. Take a look at those and test the row counts for each.

B.,

differences in record counts

Hello all,

I have a problem concerning differences in record counts between the measure group and the fact table.
for debugging such a case in Analysis Services 2000, I would have run process on the cube, copy the SQL statement that was generated and debug it using Query Analyser. in sql 2005, I tried doing that but got the sql statement without the joins to the dimensions so no much help in that...

does anyone have a suggestion on how to debug such a case?

Thanks,

Momo

In SSAS 2005, the fact table is not joined to the dimensions during processing unless you implemented a reference dimension and opted to materialize it. In this situation, you will see a join to the intermediate dimension table.

B.

|||

Bryan C. Smith wrote:

In SSAS 2005, the fact table is not joined to the dimensions during processing unless you implemented a reference dimension and opted to materialize it. In this situation, you will see a join to the intermediate dimension table.

B.

So can anyone explain why the poster is observing dropped rows?

In my case I am finding the cubes are not showing any financials. Fact tables are populated correctly. Dimensions appear to be joined correctly - but I understand this wouldnt matter anyway?

Is there a way to see how the cube process is getting its data? Is there a way to check the integrity of a data source view? What is the consequence of incorrectly joining tables in your data source view?

Debugging in AS 2000 seemed much easier!

|||

When you process the cube, you have access to the queries submitted. Take a look at those and test the row counts for each.

B.,

Differences between Desktop and Server Edition

Hi
I have a query concerning SQL server 7. We currently have an NT server 4.0
using SQL server, but however recently
we have been getting alot freezes from branches. I have noticed that the in
stallation on that server is desktop editon. I am not sure if this the like
y reason.
What are the differences between desktop and server edition?
Should'v the server be installed as SQL server - server edition?
Is there any optimising we can there?
ThanksThe desktop edition is required for non-server OS's (like NT workstation, or
windows xp).
The functionality is the same, but there is a limit on the number of threads
( maybe 10 I think). When there are more connections than worker threads,
then multiple connections share the same thread and response time
increases... This prevents users from putting Desktop Edition into
production when the full server should be used.
The desktop edition has lower cost than servers, but is intended ONLY for
small small number of users...To increase throughput , you buy and install
the Server Edition.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"Rakesh" <anonymous@.discussions.microsoft.com> wrote in message
news:59E83439-70FE-4C64-B2C6-164E9B6A39D6@.microsoft.com...
> Hi
> I have a query concerning SQL server 7. We currently have an NT server
4.0 using SQL server, but however recently
> we have been getting alot freezes from branches. I have noticed that the
installation on that server is desktop editon. I am not sure if this the
likey reason.
> What are the differences between desktop and server edition?
> Should'v the server be installed as SQL server - server edition?
> Is there any optimising we can there?
> Thanks|||Do you reckon that SQL server - server edition be installed.
Would we have to uninstall the SQL sever deskop edition and install SQL - se
rver edition ?
How does SQL server optimise its memory management system?
Thanks

Differences between Desktop and Server Edition

H
I have a query concerning SQL server 7. We currently have an NT server 4.0 using SQL server, but however recentl
we have been getting alot freezes from branches. I have noticed that the installation on that server is desktop editon. I am not sure if this the likey reason
What are the differences between desktop and server edition
Should'v the server be installed as SQL server - server edition
Is there any optimising we can there
ThanksThe desktop edition is required for non-server OS's (like NT workstation, or
windows xp).
The functionality is the same, but there is a limit on the number of threads
( maybe 10 I think). When there are more connections than worker threads,
then multiple connections share the same thread and response time
increases... This prevents users from putting Desktop Edition into
production when the full server should be used.
The desktop edition has lower cost than servers, but is intended ONLY for
small small number of users...To increase throughput , you buy and install
the Server Edition.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"Rakesh" <anonymous@.discussions.microsoft.com> wrote in message
news:59E83439-70FE-4C64-B2C6-164E9B6A39D6@.microsoft.com...
> Hi
> I have a query concerning SQL server 7. We currently have an NT server
4.0 using SQL server, but however recently
> we have been getting alot freezes from branches. I have noticed that the
installation on that server is desktop editon. I am not sure if this the
likey reason.
> What are the differences between desktop and server edition?
> Should'v the server be installed as SQL server - server edition?
> Is there any optimising we can there?
> Thanks|||Do you reckon that SQL server - server edition be installed
Would we have to uninstall the SQL sever deskop edition and install SQL - server edition
How does SQL server optimise its memory management system
Thanks

Differences between Desktop and Server Edition

Hi
I have a query concerning SQL server 7. We currently have an NT server 4.0 using SQL server, but however recently
we have been getting alot freezes from branches. I have noticed that the installation on that server is desktop editon. I am not sure if this the likey reason.
What are the differences between desktop and server edition?
Should'v the server be installed as SQL server - server edition?
Is there any optimising we can there?
Thanks
The desktop edition is required for non-server OS's (like NT workstation, or
windows xp).
The functionality is the same, but there is a limit on the number of threads
( maybe 10 I think). When there are more connections than worker threads,
then multiple connections share the same thread and response time
increases... This prevents users from putting Desktop Edition into
production when the full server should be used.
The desktop edition has lower cost than servers, but is intended ONLY for
small small number of users...To increase throughput , you buy and install
the Server Edition.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"Rakesh" <anonymous@.discussions.microsoft.com> wrote in message
news:59E83439-70FE-4C64-B2C6-164E9B6A39D6@.microsoft.com...
> Hi
> I have a query concerning SQL server 7. We currently have an NT server
4.0 using SQL server, but however recently
> we have been getting alot freezes from branches. I have noticed that the
installation on that server is desktop editon. I am not sure if this the
likey reason.
> What are the differences between desktop and server edition?
> Should'v the server be installed as SQL server - server edition?
> Is there any optimising we can there?
> Thanks
|||Do you reckon that SQL server - server edition be installed.
Would we have to uninstall the SQL sever deskop edition and install SQL - server edition ?
How does SQL server optimise its memory management system?
Thanks