Showing posts with label mining. Show all posts
Showing posts with label mining. Show all posts

Wednesday, March 21, 2012

Is it possible to create reports in SSRS 2005 by mining data in SQL Server 2000

All,

I have found a lot of comments on the net but nowhere was I able to have a direct answer to this question:
My client has a complex database deployed on SQL Server 2000. He wishes to create reports based on this data using SSRS. Another division of the same company just implemented SQL Server 2005 and SSRS 2005.
I wish to know if SSRS 2005 is able to create reports based on data from SQL Server 2000?

Thank you.
S
Sure. You'll have no problems reporting against 2005 and 2000 together...

Wednesday, March 7, 2012

Is it a Compatible bug in SQL Server 2005 ?

Hi, all here,

I use SQL Server 2005 standard edition ,

I choose to use table(table stored in Oracle9i) as source for mining structure, and I use

Oracle Provider for OLE DB(or Microsoft OLE DB Provider for Oracle).I set one column as logic key and this column stored chinese data.Deployment was successful. When I processed the mining structure,

an error happened:

Warning 0x80202066:Data Flow Task :Connot retieve the column code page info from OLE DB provider.If the comopenent supports the "DefaultCodePage" property,the code page from that property will be used .Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.

But I created the same mining stucture and processed it successfully in SQL Server 2000. Is it a Compatible bug in SQL Server 2005?

It looks like the OLE DB provider for Oracle requires a code page to be specified because there is locale-specific (Chinese) data in the column.

There is a similar posting on the SSIS forum which you may find useful:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PageIndex=2&SiteID=1&PostID=107027

HTH,

Akshai

|||

hi,Akshai,

thanks!

I had modified the Propertie:CheckDistinctRecordSortOrder in my SSAS,

and the mining model had been processed successfully!