add entities to report model programmatically ?

Hi Friends
is it possible to add entities to a report model dynamically ,probably thru SOAP api ?
we've c# app and we want to be able to add entities dynamically .
Thanks for the helpNo, the only API's are for updating the entire model.|||Thanks BOB.
thats what i figured out finally. BUT i found a way of adding attributes to existing entities .am reading .smdl file using a c# program and adding a attribute under a specific entity.
if i re-publish the model everything worked fine as normal.

i need to do this as our clients want to report on "user defined tables" which we're not aware of when creating report model!
i have not tested my approach enough and i appreciate ur advise here. is there any better way of doing this.
Your advise really appreciated.
Thanks again|||That looks like your best option.|||

Thanks for the reply Bob.

Actually i was not sure before, now after ur post i've got some confidence to try this solution in real world. Thanks again :)

Add a second databse - benefits?

Hi, there is an existing application running on a SQL Server database.

Now I have to built a different app, which will have two common tables
with the existing database (Customers, sales)

Is there any benefit (performance mainly) creating the tables for the
new app in a new database? (On the same machine and the same instance)

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!chora (choracy@.hotmail.com) writes:
> Hi, there is an existing application running on a SQL Server database.
> Now I have to built a different app, which will have two common tables
> with the existing database (Customers, sales)
> Is there any benefit (performance mainly) creating the tables for the
> new app in a new database? (On the same machine and the same instance)

There is too little information to say anything with certainty. If the
two apps not only share the table definitions, but also the data in
the table, putting everything in the same database.

As long as the applications are access their individual tables, there
is not much interferance between them. All I can think is that autogrow
caused by one app will affect the userss of the other app two, but
autogrows should not occur frequently.

Of course, in the common tables there may be blocking issues with
improper application design.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||
Erland ,

thanks for the reply.

The databases will share the data of the two tables. The new database
will have 'read only' access to these tables.

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||Hi

If these tables are large, then you may want to make them federated and
create a partitioned view for them. This may give you a performance
improvement e.g http://vyaskn.tripod.com/federated.htm

There may also be other reasons to use a separate database such as ownership
(e.g if a third party package it may invalidate the waranty to stick extra
tables in there), security and maintainance.

John

"chora" <choracy@.hotmail.com> wrote in message
news:40d5962f$0$16472$c397aba@.news.newsgroups.ws.. .
>
> Hi, there is an existing application running on a SQL Server database.
> Now I have to built a different app, which will have two common tables
> with the existing database (Customers, sales)
> Is there any benefit (performance mainly) creating the tables for the
> new app in a new database? (On the same machine and the same instance)
>
>
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!

AD groups and database roles

We have AD and SQL Server 2005.
I have made grants to a database role called 'App Users'. I then set up
the AD group as a login, and tried to map to the proper database and the App
Users database role. This last step is failing with a 'principal cannot be
found' error. Is there any limitation to use AD groups in this way? Seems
that it should be pretty straightforward.
Thanks,
DavidDavid
I could not reproduce it , can you provide a script or step by step what
you did so far?
1) Crate a database Role called 'MyRole'
2) Create a new login called 'Test'
3) Add the the new user (mapped to the login) to the desired database
4) Add a database user to the Role
"David R" <DavidR@.discussions.microsoft.com> wrote in message
news:99E59589-24C0-44C1-9335-6B039E2F91FE@.microsoft.com...
> We have AD and SQL Server 2005.
> I have made grants to a database role called 'App Users'. I then set up
> the AD group as a login, and tried to map to the proper database and the
> App
> Users database role. This last step is failing with a 'principal cannot
> be
> found' error. Is there any limitation to use AD groups in this way?
> Seems
> that it should be pretty straightforward.
> Thanks,
> David|||Thanks for the response, but never mind. I tried it again, after having a
new group created, and it worked without a problem. Don't know why it faile
d
the first time.
David
"Uri Dimant" wrote:

> David
> I could not reproduce it , can you provide a script or step by step what
> you did so far?
>
> 1) Crate a database Role called 'MyRole'
> 2) Create a new login called 'Test'
> 3) Add the the new user (mapped to the login) to the desired database
> 4) Add a database user to the Role
>
>
> "David R" <DavidR@.discussions.microsoft.com> wrote in message
> news:99E59589-24C0-44C1-9335-6B039E2F91FE@.microsoft.com...
>
>