Showing posts with label assuming. Show all posts
Showing posts with label assuming. Show all posts

Wednesday, March 21, 2012

deployment and reports

Hi,

When I deploy a report i am assuming the report is deployed to the reporting service DB (ReportServer). Then when i try to view report in a browser I presume the following happens:

Navigate to http://localhost/Reports and click report you want to view

A web service call is made to retrieve report data from a DB eg Northwind

The data is the rendered based on the defined formatting in the RDL file and displayed in browser.

If this is correct does anyone known where the report is deployed to (DB or Web service) I cannot see the rdl files in any of these places and if I delete my project report viewing still works.

I know you can view all reports if you are in SQL management studio and go connect->reporting services but this is not a DB. Is this the web service and if so why cant i see files in IIS?

Thanks for replies

It's because they're not stored as files. When you deploy any files to the report server, they are stored in a table called Catalog and are serialized into an image column called Content.

Report Manager, Management Studio or whatever just connect to the web service and query it about which reports are stored in the database. The web service is basically the interface into the database.

Wednesday, March 7, 2012

Deploying a website with user authentication - getting errors

I have built a site that uses form-based authentication. Am I correct in assuming that the users and passwords will be stored in the SQLServer database in the aspnetdb.mdf file? The website works great and the authentication works how I want it to. However, I've tried to copy over the file onto a remote machine. The first page is a login screen and this is displayed without any problems but as soon as I attempt to log in I get an error message of:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)


I'm wondering if this is something to do with the fact I installed SQLServer Express edition on the remote machine. The website works no problem on the local machine in debug mode of Visual Studio 2005 (Professional Edition). I followed instructions to enable remote connections on SQLServer Express from a Microsoft support doc. If anybody can point me in the right direction I'll be very grateful as I've hit a wall here.

Did you check the connection string in web.config if it is pointing to the right server. Also, if you are using aspnetdb.mdf, you should have at least SQL Server Express edition installed on the machine hosting the website.

|||

Hi. Thanks for replying. The only connection string I have in my webconfig file is for an Oracle database that I access elsewhere in the website. Since the original website works in the debug mode of Vis Studio 2005 without any other connection string then I just copied the webconfig file over to the remote server as it was. Does that mean I have to add a connection string to the aspnetdb.mdf file? (The server has SQLServer Express installed on it.)

|||

Have a look at this and try adding a connectionstring to the server.
https://help.maximumasp.com/SmarterTicket/Customer/KBArticle.aspx?articleid=878

You might have to attach the local mdf file using this in the connection string.

AttachDBFilename=|DataDirectory|aspnet.mdf 
connectionStrings> <remove name="LocalSqlServer" /> <add name="LocalSqlServer" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient"/></connectionStrings>

Friday, February 17, 2012

Dependency Network Graph Question

I have some problems in understanding the dependency network graph which is built in the association rules algorithm. My questions are:

1) Assuming an arrow goes from Node A to Node B ( A --> B), is Node A dependent from Node B or is Node B dependent from Node A?
2) Are only rules used with one element on each side of the rule (itemset size = 2) or is the graph also influenced by rules with more elements?
3) it is said that the slider on the left side is related to the probability of the rules. when viewing my rules table I don't understand why some rules are viewable later then other ones because they have the same probability. Is there another parameter influencing this slider? Which one?

I would be grateful for your help!

Regards, David

1: read it as A -> B, that means that the presence of A imples the presence of B.

2: The dep net currently only uses rules generated from two itemsets

3: I believe the slider is more the importance of the rule than the probability. A rule A->B where both occur 100% in the data isn't very interesting, so I think that's what you are seeing.