creating a report model based on a view

in my report model project, i'm able to successfully create and deploy a report model based on a data source view that is in turn based on a table object in my data store.

but if i try to create a report model that's based on a a data source view that is in turn based on a view in my data store, well then, the report model that gets created comes up blank - i.e. shows no objects.

What gives? Is it not possible to create a report based on a view? that can't be right!

NewJoizey wrote:

What gives? Is it not possible to create a report based on a view? that can't be right!

It is possible. But it's a little tricky to set up a model.

|||

that doesn't make sense. - i am sure that people must all the time set up a report based on a view that already exists. maybe there's another way that the procedure i'm trying to accomplish here?

|||

NewJoizey wrote:

i am sure that people must all the time set up a report based on a view that already exists.

Yes. You just have to set up a model with the proper relationships for your database first. Otherwise, it doesn't know what your data looks like.

It's like trying to construct a building without drawing up the blueprints.

Have you created a report before using business intelligence studio?

|||

yes I have successfullly created reports across different data stores, but it only seems to work based on tables, not views

I'm confused because I have an existing view that lives in my db. when I click "data source views" in my report project, i can clearly see all my database defined views in the wizard, and so I point the data source view (in my report project) to my desired view (database) I click finish and everything looks fine.

in my report project environment, i set up my report model based on my newly defined data source view, and under where it says "model" there's nothing zero zip nada, whereras my other report models clearly show all of the fields.

If there are extra steps to be able to do this properly, MS certainly doesn't make it very clear!

|||

I recommend this to you:

http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?culture=en-US&EventID=1032273699&CountryCode=US

Creating a database from script - permissions problems

We deploy our app via ClickOnce. Rather than shipping the .mdf and .ldf, the app detects whether the database is there and creates it via script if it's not. The script was originally generated from SQL Exrpess Mangement Console, etc.

In the past, we've made the stipulation that the user must have administrator access to the machine. However, we now need to find a workable solution for users who are not administrators on their machine. Currently, we use the following connection string before attempting to run the db creation script:

conn.ConnectionString = "Server=.\\sqlexpress;Integrated Security = true;User Instance=false";

The script fails when trying to execute "CREATE DATABASE [myDatabaseName] ON PRIMARY "

with the error:

"CREATE DATABASE permission denied in database 'Master'"

How can we get around this permissions issue in the most automated way possible?

TIA!

Hi,

you will need to have a user with dbcreator permissions, otherwise you won′t be able to make an entry in the sysdatabases (Creating a database). Can you use any administrative SQL Server login to connect to the database and make this possible ? The connection string has to include the userid as well as the password then.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Creating a .NET Stored Procedure in Sql Server 2005 Express Edition

Could somebody tell me how do we create a .NET Stored Procedure in Sql Server 2005 Express Edition and deploy and debug it against the database from Visual Studio 2005 or Visual Web Developer? Can some one also let me know which approach is faster among .NET stored procedure or T-SQL stored procedure?

Regards...

Shashi Kumar Nagulakonda.

I can't help you with the first question.

The answer to the second question is obviously it depends. As far as I know (and I know very little about .NET sps), given the same task, the T-SQL sp should execute faster. Now that doesn't preclude that yes, you can write a really bad T-SQL sp that performs worse than a well written .NET sp, but as far as I know the .NET sp's work on sets of data very similiarly to a cursor, and therefore will experience the same speed (or lack thereof). Not to mention the overhead of loading the .NET runtime into memory, and doing all the jitting. Then again, some things would be much easier in .NET because T-SQL isn't a full programming language, so the .NET sps have a much greater versitality.

Again, I have actually no experience with using, writing, or debugging .NET sp's. If someone more knowledgable wants to chime in, please do so.