Link Table

Ronia,
this could be achieved using replication (and triggers,
linked servers, DTS...). It largely depends on latency -
the delay between the change made on A and it appearing
on B, and whether the data in B is updatable. If you can
give me a bit more info on these matters, then we'll be
in a better position to advise.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Hi Paul,
Data won't be update by table B. Update will only done via Table A.
so it is only a read only .
There's a replication mode which fit with this scen.
But i am not familiar with replication. and i will ask me not to use system
account with it, I don't know how to do it.
Thanks.
Ronia.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> ?
news:8aae01c4d17a$1828d140$a601280a@.phx.gbl ?...
> Ronia,
> this could be achieved using replication (and triggers,
> linked servers, DTS...). It largely depends on latency -
> the delay between the change made on A and it appearing
> on B, and whether the data in B is updatable. If you can
> give me a bit more info on these matters, then we'll be
> in a better position to advise.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Transactional replication would be best for your
scenario. Replication uses agents which are essentially
jobs run by the sql server agent. For the security
requirements have a look in books on line
for 'replication, security', 'Role Requirements'.
To run replication you won't need the sysadmin account
but to set it up, configure it and monitor it, you will.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Ronia,
Why dont you create a view in your database "B"?
Use B
Go
Create view T
As
Select * From A.dbo.T
Go
This will let you read the data from the database A, table T.
Sriram
"Ronia" <Ronia@.mail.com> wrote in message news:<OaGb5tj0EHA.480@.TK2MSFTNGP10.phx.gbl>...
> Hi Paul,
> Data won't be update by table B. Update will only done via Table A.
> so it is only a read only .
> There's a replication mode which fit with this scen.
> But i am not familiar with replication. and i will ask me not to use system
> account with it, I don't know how to do it.
> Thanks.
> Ronia.
|||hi Sriram,
Will there be any preformance issue.. when doing this? However is they
are located within the same server is that performance will not be an
issue?...
compare with Transactional replication which will be better?
Thanks
Ronia
"Sriram" <srivish@.gmail.com> ?
news:25274ca3.0411241354.5e914fc2@.posting.google.c om ?...
> Hi Ronia,
> Why dont you create a view in your database "B"?
> Use B
> Go
> Create view T
> As
> Select * From A.dbo.T
> Go
> This will let you read the data from the database A, table T.
> Sriram
>
> "Ronia" <Ronia@.mail.com> wrote in message
news:<OaGb5tj0EHA.480@.TK2MSFTNGP10.phx.gbl>...[vbcol=seagreen]
system[vbcol=seagreen]
|||It depends...
If you require a copy of the data, so eg you can do
reports on it, while not affecting - blocking - users who
are making updates on the main table, then replication
would be suitable. It can also be used to effectively
load balance database access if the databases exist on
different drives. Also, so people use snapshot
replication to have a copy of a table that users can play
around with and modify the data indiscriminantly, knowing
that all the changes will later be overwritten.
So, what is your requirement for a copy of the data? If
it doesn't fit into one of these categories, then a cross-
database view may indeed be the solution.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Limitations of Report Builder

What functionality does Report builder NOT provide that can be achieved within Report Designer through BIDS. Basically what are the limitations of report builder, what can report builder not do?

Thanks

Can anyone help please?

I believe it is the case that you cannot open a report developed in report designer through report builder. Is this true?

|||

Report Builder is not a slimmed down version of Report Designer, it is a completely different design time experience. As such I don't think it is quite valid to try to compare them from a feature perspective because they do completely different things.

ReportBuilder is designed for people who don't know anything about the physical structure of the underlying data, and want to build "simple" reports based on predefined semantic models of the data. It is geared for users who want to think in terms of their business entities, and not tables/columns.

|||

Ok, but is it correct you cannot edit reports with report builder?

1. Whether they were built using Report Builder

2. Or where built with report designer

Thanks

|||You should be able to edit reports you have previously created using Report Builder.|||

The principal difference between Report Builder and Report Designer is the approach one would take to create report and skills level required for it.

Report Designer is a universal tool where one can create any kind of report of any kind of complexity. This requires the author to provide SQL statement that would return data, understand that data and how to group it and how to build aggregates such as Sum/Count/Average etc, design layout, attach fields from query to the layout, write VB expressions, may be custom code (again VB) or custom assemblies that would extend default function library and so on. Once such report is created, it is published and end users execute it to see results.

Report Builder is a new technology that addresses the necessity of quick ad-hoc reports that can be created easily by users without skills in any programming environments, languages and have no idea how physical database is organised. That does not mean that Report Builder is less capable, one can create very sophisticated reports with it. It's just the purpose and the scope are a bit different. Report Builder requires semantic models which currently can be built for MS Sql Server only. In Yukon SP2 model support is extended to include Oracle databases. Note that adhoc reports created in Report Builder can be saved (published) to report server. They also can be loaded into Report Designer, but once changed in RD, they can no longer be loaded back into RB.

Limitations of Report Builder

What functionality does Report builder NOT provide that can be achieved within Report Designer through BIDS. Basically what are the limitations of report builder, what can report builder not do?

Thanks

Can anyone help please?

I believe it is the case that you cannot open a report developed in report designer through report builder. Is this true?

|||

Report Builder is not a slimmed down version of Report Designer, it is a completely different design time experience. As such I don't think it is quite valid to try to compare them from a feature perspective because they do completely different things.

ReportBuilder is designed for people who don't know anything about the physical structure of the underlying data, and want to build "simple" reports based on predefined semantic models of the data. It is geared for users who want to think in terms of their business entities, and not tables/columns.

|||

Ok, but is it correct you cannot edit reports with report builder?

1. Whether they were built using Report Builder

2. Or where built with report designer

Thanks

|||You should be able to edit reports you have previously created using Report Builder.|||

The principal difference between Report Builder and Report Designer is the approach one would take to create report and skills level required for it.

Report Designer is a universal tool where one can create any kind of report of any kind of complexity. This requires the author to provide SQL statement that would return data, understand that data and how to group it and how to build aggregates such as Sum/Count/Average etc, design layout, attach fields from query to the layout, write VB expressions, may be custom code (again VB) or custom assemblies that would extend default function library and so on. Once such report is created, it is published and end users execute it to see results.

Report Builder is a new technology that addresses the necessity of quick ad-hoc reports that can be created easily by users without skills in any programming environments, languages and have no idea how physical database is organised. That does not mean that Report Builder is less capable, one can create very sophisticated reports with it. It's just the purpose and the scope are a bit different. Report Builder requires semantic models which currently can be built for MS Sql Server only. In Yukon SP2 model support is extended to include Oracle databases. Note that adhoc reports created in Report Builder can be saved (published) to report server. They also can be loaded into Report Designer, but once changed in RD, they can no longer be loaded back into RB.