Mapping Report Model Entities to Drill-through Reports

When you use Sql Mgmt Studio to assign a report as a drill-through target for
a model entity, you can assign reports for both "Single Instance" and
"Multiple Instance". Does anyone know what this means? I had a 2+-hour
support session with a member of MS SQL Reporting team, and he didn't know
either.
cheers,
Helen
--
Helen Warn, PhD
Agile Software Inc.
www.agile-soft.comBy default when you save the file, where the datasource is connected through
RB,
If you have opened RB through some other server then you can attach where it
is for multiple instance of the servers. Basically to update on the report
server database of multiple servers is called multiple instance and single
server is called single instance.
Amarnath
"Helen Warn" wrote:
> When you use Sql Mgmt Studio to assign a report as a drill-through target for
> a model entity, you can assign reports for both "Single Instance" and
> "Multiple Instance". Does anyone know what this means? I had a 2+-hour
> support session with a member of MS SQL Reporting team, and he didn't know
> either.
> cheers,
> Helen
> --
> Helen Warn, PhD
> Agile Software Inc.
> www.agile-soft.com|||Actually that is not what it is used for. From
http://msdn2.microsoft.com/en-us/library/ms345298.aspx
(Lesson 12: Specifying Clickthrough Report Options from BOL):
"There are two clickthrough templates for each entity: a single instance
template and a multi-instance template. A single instance template is used
when the user clicks an instance of the entity. A multi-instance template is
used when the user clicks an aggregate value and multiple instances of the
entity are displayed."
I am sure that I am not the only person who fervently wishes that the
reference sectins of the documentation contained such information.
Cheers,
Helen
--
Helen Warn, PhD
Agile Software Inc.
www.agile-soft.com
"Amarnath" wrote:
> By default when you save the file, where the datasource is connected through
> RB,
> If you have opened RB through some other server then you can attach where it
> is for multiple instance of the servers. Basically to update on the report
> server database of multiple servers is called multiple instance and single
> server is called single instance.
> Amarnath
> "Helen Warn" wrote:
> > When you use Sql Mgmt Studio to assign a report as a drill-through target for
> > a model entity, you can assign reports for both "Single Instance" and
> > "Multiple Instance". Does anyone know what this means? I had a 2+-hour
> > support session with a member of MS SQL Reporting team, and he didn't know
> > either.
> >
> > cheers,
> >
> > Helen
> > --
> > Helen Warn, PhD
> > Agile Software Inc.
> > www.agile-soft.com

Management Studio scripts for SQL 2000

When I use the generate scripts task in Management Studio to create tables
for a SQL 2000 target, the scripts do not run in SQL 2000.
I selected SQL 2000 compatibility mode. The scripts work fine on a 2000 database
running under SQL 2005 but not on the real thing.
Is there a easy way to generate scripts that run on a SQL 2000 instance?
Darren (Darren@.nospam.nospam) writes:
> When I use the generate scripts task in Management Studio to create tables
> for a SQL 2000 target, the scripts do not run in SQL 2000.
Exactly why do they not run? Because they refer to sys.objects, of because
of some other problem? I just scripted a database on SQL 2005 for SQL 2000,
and the script ran on SQL 2000.
I seem to recall that that there was a problem with scripts for SQL 2000
referring to sys.objects in the RTM release ot SQL 2005, but this was
corrected in SP1. You can find SP1 of SQL 2005 at
http://www.microsoft.com/sql/sp1.mspx.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|||Thanks. I wasn't aware of SP1.
Erland Sommarskog wrote:
> Darren (Darren@.nospam.nospam) writes:
> Exactly why do they not run? Because they refer to sys.objects, of because
> of some other problem? I just scripted a database on SQL 2005 for SQL 2000,
> and the script ran on SQL 2000.
> I seem to recall that that there was a problem with scripts for SQL 2000
> referring to sys.objects in the RTM release ot SQL 2005, but this was
> corrected in SP1. You can find SP1 of SQL 2005 at
> http://www.microsoft.com/sql/sp1.mspx.
>
>