Showing posts with label model. Show all posts
Showing posts with label model. Show all posts

Monday, March 19, 2012

"Specified method is not supported" "Update model statistics before generating&qu

I'm creating my first Report Model and I've managed to get through it, but if I select the "Update model statistics before generating" in the "Report Model Wizard", I get this error:

"Specified method is not supported"

(It would be a little less frustrating if it actually HAD specified the method <s>)

Anyone know what this is or how to fix it?

Thanks in advance,

Mike

Hi Mike,

Did you get a solution to this issue as we are experiencing it here. Thanks.

|||No, never did...

"Specified method is not supported" "Update model statistics before generating&qu

I'm creating my first Report Model and I've managed to get through it, but if I select the "Update model statistics before generating" in the "Report Model Wizard", I get this error:

"Specified method is not supported"

(It would be a little less frustrating if it actually HAD specified the method <s>)

Anyone know what this is or how to fix it?

Thanks in advance,

Mike

Hi Mike,

Did you get a solution to this issue as we are experiencing it here. Thanks.

|||No, never did...

Friday, March 16, 2012

"Predictable Column Name" and "Predictable Value"

Hi,

I tried to utilize Mining Accuracy to analyze my models.

Mining Model Predictable Column Name Predictable Value
--
NaiveBayesModel
DecisionTreeModel

When I want to choose an option for "Predictable Column Name" on NaiveBayesModel row or DecisionTreeModel row, there is no option/value/choice on the drop box. There is also no option/value/choice for the "Predictable Value" column.

When I clicked "Lift Chart" tab to see the accuracy chart, it gave me this error message: "No mining models are selected for comparison."

The models are as follows:

(

[CustKey] KEY,

[Gender] TEXT DISCRETE,

[BikeModels] TABLE PREDICT_ONLY

(

[Model] TEXT KEY

)

)

Please assist!

Mary

The accuracy charts provided in the product only work for scalar predictable columns. In your model, the target is the BikeModels nested table, which cannot be handled by the tools|||This is because you don't have any predictable case level columns and the accuracy charts don't support nested table outputs. Since the prediction in your case is a nested table containing multiple bike models, there's no standard way to compare the accuracy of two models.|||

Ok,

If there is no standard way for predicted columns in a nested table, is there any non-standard way or perhaps using DMX query without relying the tool to measure the accuracy of the models? Is there any online resources that discuss more about this issue?

Mary

|||

I posted this response to a similar question - hope this helps. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=110238&SiteID=1

The issue in accuracy regarding nested tables is in the definition of the question. "Accuracy" means that the model predicts correctly what you are asking. With nested tables, it's not entirely clear what an "accurate" prediction would be. For instance, it could be that a recommendation occurred within the top n answers, or it could be that the predicted value for a particular nested key was correct, etc.

Let us know if the linked response helps, or if there are other areas of "accuracy" you want to explore.

Thanks

-Jamie

|||

Yeah, it helps.Thanks!

Mary

"Predictable Column Name" and "Predictable Value"

Hi,

I tried to utilize Mining Accuracy to analyze my models.

Mining Model Predictable Column Name Predictable Value
--
NaiveBayesModel
DecisionTreeModel

When I want to choose an option for "Predictable Column Name" on NaiveBayesModel row or DecisionTreeModel row, there is no option/value/choice on the drop box. There is also no option/value/choice for the "Predictable Value" column.

When I clicked "Lift Chart" tab to see the accuracy chart, it gave me this error message: "No mining models are selected for comparison."

The models are as follows:

(

[CustKey] KEY,

[Gender] TEXT DISCRETE,

[BikeModels] TABLE PREDICT_ONLY

(

[Model] TEXT KEY

)

)

Please assist!

Mary

The accuracy charts provided in the product only work for scalar predictable columns. In your model, the target is the BikeModels nested table, which cannot be handled by the tools|||This is because you don't have any predictable case level columns and the accuracy charts don't support nested table outputs. Since the prediction in your case is a nested table containing multiple bike models, there's no standard way to compare the accuracy of two models.|||

Ok,

If there is no standard way for predicted columns in a nested table, is there any non-standard way or perhaps using DMX query without relying the tool to measure the accuracy of the models? Is there any online resources that discuss more about this issue?

Mary

|||

I posted this response to a similar question - hope this helps. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=110238&SiteID=1

The issue in accuracy regarding nested tables is in the definition of the question. "Accuracy" means that the model predicts correctly what you are asking. With nested tables, it's not entirely clear what an "accurate" prediction would be. For instance, it could be that a recommendation occurred within the top n answers, or it could be that the predicted value for a particular nested key was correct, etc.

Let us know if the linked response helps, or if there are other areas of "accuracy" you want to explore.

Thanks

-Jamie

|||

Yeah, it helps.Thanks!

Mary

Thursday, March 8, 2012

"Keyword not supported: 'provider'." error with Report Builder

Hi,

I'm trying to process reports with Report Builder against a SQL Server Database.

When the .Net Provider is used in the model, everything works fine.

But if I try to use another provider (the .Net Provider for OLEDB or the native OLEDB one) to connect to the data source, i've got the following error when trying to process the report in Report Builder: Keyword not supported: 'provider'.

Is this a normal behaviour of the Report Builder ?

Thanks in advance.

Grgory.

I have tried OLE DB data sources (for Sybase) on SQL Server 2005 server, and it just doesn't work. Ended up using ODBC

The same steps worked fine on SQL Server 2000 (can access Sybase through OLE instead of ODBC)

I think it's not really a Report Server issue

Tuesday, March 6, 2012

"distinct" in select query

when i use select :

select flattened

(select productid, $support from [model name].[table] )......

i have result with many record same.

so i write :

select flattened

(select distinct productid, $support from [model name].[table] )......

but when i run, it's error. ( don't know what error).

how can i do to get table record with not same record (loop)

note : it write in DTS and i use sql 2000

I assume you mean an Analysis Services query.

Try: SELECT DISTINCT [model name].[table].[productid] FROM [model name]

This should return the distinct list of products

|||

i can't use query like you show.

i want you "distinct " in DTS syntax like that:

select flattened

(select productid, productname, categoryid ,[$probability] from predict([model name].[table name], incluse_statistics) where productid > 1000)

from [model name]

prediction join

shape{....}

appen{....}

on....

How can i put Distinct to have different record?

|||

You can't use DISTINCT in that context. However, I think what you want is to be able to discriminate the records by the user. In this case, the selection will return the product id at most once per input case, but since you don't include an external id, there's no way to discriminate which prediction is for which customer.

I think you need something like

SELECT FLATTENED t.CustomerID, (select ....

This query will return the id from the source data query along with the results of the prediction.

Saturday, February 25, 2012

"could not open connection to SQL Server"?

I just installed a new SQL 2005 Server (September CTP - Developer Edition) on Windows Server 2003 (Using Virtual PC).

I have created a Data Model to be used for creating reports. When I tried to deploy the Model, I got an error along the lines of "...SQL Server does not allow remote connections...".

I then took a step back and tried to browse the report server (http://localhost/reportserver) and I got the message below:

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I also notice that when I go into the Reporting Services Configuration Manager, I see that the Initialization item in the left hand side is Not Configured (has a "red x"). When I try clicking on this item, I get a similar message to the one above.

I am very new at SQL 2005 and this is my first install of it (I have been using other installations in the past). I did some searching and found that I should use the SQL Server Surface Area Configuration utility to allow remote connections for both TCP and Named Pipes. I did this and rebooted my server and I am still getting the same error messages.

Is there something I have yet to configure?

Any and all help is very much appreciated!!!

Thanks!

Brian McCulloughRight after I posted this I realized I renamed the Computer after I installed SQL. The problem was that when I installed reporting services, it created all the connection information based on the "old" computer name.

Brian|||What did you have to do to fix it? Where is the connection information?|||In the Reporting Services Configuration Manager select the Database Setup item on the left-hand side. This is where you specify the Database connection properties for the ReportServer database. I had to change the Server Name to match the current machine name, not what I had it as originally.

-Brian|||I had a similar problem - I was able to fix it by specifying my server as computer-name\servername
Hope this helps

"could not open connection to SQL Server"?

I just installed a new SQL 2005 Server (September CTP - Developer Edition) on Windows Server 2003 (Using Virtual PC).

I have created a Data Model to be used for creating reports. When I tried to deploy the Model, I got an error along the lines of "...SQL Server does not allow remote connections...".

I then took a step back and tried to browse the report server (http://localhost/reportserver) and I got the message below:

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I also notice that when I go into the Reporting Services Configuration Manager, I see that the Initialization item in the left hand side is Not Configured (has a "red x"). When I try clicking on this item, I get a similar message to the one above.

I am very new at SQL 2005 and this is my first install of it (I have been using other installations in the past). I did some searching and found that I should use the SQL Server Surface Area Configuration utility to allow remote connections for both TCP and Named Pipes. I did this and rebooted my server and I am still getting the same error messages.

Is there something I have yet to configure?

Any and all help is very much appreciated!!!

Thanks!

Brian McCulloughRight after I posted this I realized I renamed the Computer after I installed SQL. The problem was that when I installed reporting services, it created all the connection information based on the "old" computer name.

Brian|||What did you have to do to fix it? Where is the connection information?|||In the Reporting Services Configuration Manager select the Database Setup item on the left-hand side. This is where you specify the Database connection properties for the ReportServer database. I had to change the Server Name to match the current machine name, not what I had it as originally.

-Brian|||I had a similar problem - I was able to fix it by specifying my server as computer-name\servername
Hope this helps