The Unpopular SELECT Statement

  • VincentRainardi

    SSCrazy

    Points: 2905

    Comments posted to this topic are about the item The Unpopular SELECT Statement

  • David Christal

    SSC Rookie

    Points: 36

    I'm unable to download the cube backup file. The link doesn't seem to work.

    http://www.sqlservercentral.com/Files/sales.abf/409.abf

  • abba-602531

    Right there with Babe

    Points: 721

    I was able to download the sales.abf file but every time I tried to restore it in SSAS, I would get an error:

    An existing condition was forcibly closed by the remote host

    Despite the error, the database would appear under the databases dropdown. But I couldn't do anything with the database, not even delete it. If I tried to drill down I would get another error (whose message I can't recall and I don't to install it once again).

    The only way I could drop the DB was to stop SSAS from Services and delete 2 files and 1 folder: Sales.0, Sales.0.db and master.vmp from

    C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data.

    Debbie

  • fuller.artful

    Right there with Babe

    Points: 795

    Hi Vincent,

    I liked reading through your article, and then decided to follow you step by step. I was able to grab and restore the backup file, etc., and to run the SQL statements to create the Sales database. So far, so good. I got the Product Dimension set up, by using the dropdowns not by dragging it. But I have another problem, which I suspect concerns SSAS more than your project. But having nowhere else to turn, I'm turning to you.

    Unlike in your image, on my monitor in the large pane (Details) it says, "The query could not be processed. The data provider didn't supply any further error information."

    The moment I try to move anything to where you suggested, I immediately get the error message: "Error H_Result E_Fail has been returned from a call to a COM component."

    Any suggestions?

    Thanks in advance,

    Arthur

    P.S.

    A good read, and I'm eager to go through all the steps and make it work with my own stuff.

    Arthur Fuller
    cell: 647-710-1314

    Only two businesses refer to their clients as users: drug-dealing and software development.
    -- Arthur Fuller

  • JJ B

    SSCarpal Tunnel

    Points: 4570

    Awesome intro! Not having any need for data warehousing at my agency, I haven't had a chance to learn much about the topic. However, I have a feeling that I will be getting into it some day. I have been curious. This was a great intro. You explained the basic concepts in a quick and easy to grasp manner. Thanks.

  • Steven Harris-463201

    SSC Veteran

    Points: 228

    I have the same issues. I cannot even restore the database. Additionally, the scripts provided don't seem to work or I am not running them in the correct place.

    Have you gotten any further in getting this to run? I would like to see it working.

    Thanks,

    Steve

  • fuller.artful

    Right there with Babe

    Points: 795

    I had no trouble getting the scripts themselves to work. To do so, I opened Management Studio, then opened the scripts (DDL and Populate) in turn, then executed them. Then I switched to Business Intelligence Studio, began the Restore and then realized that I would have to switch a flag indicating whether to permit browsing to a new directory. Rather than do that, I simply moved the backup file to the directory indicated. Then I proceeded and the database restored fine.

    It was after that that my problems began. I have proceeded further and am now convinced that my setup of BI is toast. I tried creating a new project and got as far as defining a new data source, when I got an error message.

    Unfortunately, my master copy is off-site, so all this will have to wait until tomorrow (for me at least).

    As for you, try my steps above. Make sure that you create the database in Management Studio not Intelligence Studio. Just do File | Open then browse to where you stored the DDL and Populate scripts, then run the DDL first and then the Populate. Then switch to Business Intelligence and restore the backup file.

    Arthur

    Arthur Fuller
    cell: 647-710-1314

    Only two businesses refer to their clients as users: drug-dealing and software development.
    -- Arthur Fuller

  • Steven Harris-463201

    SSC Veteran

    Points: 228

    Arthur,

    Thanks ... that helped. I was able to run the scripts and they created the database and populated the tables on the database engine side. However, I still cannot restore sales.abf file on the analysis side. I get an error "unable to read data from the transport connection: an existing connection was forcibly closed by the remote host." when I try to restore the file. This requires me stop the analysis services, delete the physical directory, start the services and then delete the sales database that was partially created.

    I not sure what to try. Any thoughts?

    Thanks,

    Steve

  • VincentRainardi

    SSCrazy

    Points: 2905

    Hi all, thanks for all your responses.

    Debbie, I attached sales.abf in zip format. I hope you would be able to restore the multidimensional database from this file into your SSAS server.

    David, did you mean "An existing connection was forcibly closed by the remote host", rather than "existing condition"? Probably this was caused by the database was not restored/created properly. Would it be possible to try to restore it from the attached zip file. If this doesn't work, try creating a new SSAS project in BI Development Visual Studio than deploy it to your SSAS server. This is to validate if your SSAS server can create and host a database. I found that the SSAS on the November edition of SQL Server 2008 is not stable; is this is the version that you are using? Or are you using 2005?

    Arthur, did you get the error that you mentioned in the SQL Server Management Studio (SSMS) when you try to do step 4.3, which is "Let’s drag to Drop Totals or Detail Fields Here, drag Month to Drop Row Fields Here, drag Product Category to the Select dimension area and set it to Book"? Or did it happen in BI Development Studio (BIDS) when you load the SSAS project? If this error happens in BIDS, try using SSMS. Like the error that David had, it seems that the error that you had, "Error HRESULT E_FAIL has been returned from a call to a COM component" is not related to SSAS. Perhaps we can try verifying your environment first, by creating a new SSAS project on BIDS and deploy to the SSAs server? Then we can try dragging the attribute to the right hand side area on figure 6.

    Arther, I just read your 2nd post, which was your response to Steve. So you restored the SSAS project into your BIDS. Step 4.3 of my article (figure 6) is done using SSMS, not using BIDS. Perhaps you want to try browsing the cube (and issuing MDX statements) using SSMS?

    Kind regards,

    Vincent

    Kind regards,

    Vincent

  • Steven Harris-463201

    SSC Veteran

    Points: 228

    Vincent,

    Hopefully you can help me. When I try and restore the sales.abf file I get the following error:

    The connection either timed out or was lost. (Microsoft.AnalysisServices)

    Additional Information:

    >Unable to read from the transport connection: An existing connection was forcible closed by the remote host. (System)

    >>An existing connection was forcile closed by the remote host (System)

    This require me to delete the physical files and then the database from the system.

    Thanks,

    Steve

  • VincentRainardi

    SSCrazy

    Points: 2905

    Reposting the attachment... (sales_abf.zip)

  • VincentRainardi

    SSCrazy

    Points: 2905

    Hi Steve, I just reposted the sales_abf.zip, which seems to be successful this time.

    Try downloading it. Then on step 3.4 (restore database window on SSMS) restore it as different database name, for example sales2. It seems to me that the error has no relation with the restore process. If restoring as different DB name doesn't work, you can verify that your your SSAS environment works properly by deploying a project from BIDS.

    Kind regards,

    Vincent

  • Steven Harris-463201

    SSC Veteran

    Points: 228

    That got me further ... I now get the following error:

    The following system error occurred: Access Denied. (Microsoft.AnalysisServices)

    Is there a password or other security option I need to set?

    Thanks,

    Steve

  • Steven Harris-463201

    SSC Veteran

    Points: 228

    Vincent,

    Thanks for sticking with this ... 🙂

    Unfortunately that didn't work. I now get an error:

    The ddl2:MemberKeyUniqueElement at line 97, column 10600 (namespace http://schemas.microsoft.com/analysisservices/2003/engine/2) cannot appear under Load/ObjectDefinition/Dimension/Hierarchies/Hierarchy.

    Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\c:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Sales2.0.db\Dim Date.1.dim.xml'.

    Errors in the metadata manager. An error occurred when loading the Sales cube, from the file, '\\?\c:\Program Files\Microsoft SQL ServeMSSQL.2\OLAP\Data\Sales2.0.db\Sales.2.cub.xml'. (Microsoft.AnalysisServices)

    What are the steps to testing the deployment you suggested.

    Thanks,

    Steve

  • VincentRainardi

    SSCrazy

    Points: 2905

    Hi Steve,

    there is no security that you need to setup when restoring sales.abf or when opening the analysis services project. When and where did the "access denied" error happen?

    I'm also trying to understand when and where the other error that you mentioned (The ddl2:MemberKeyUniqueElement at line 97) happened. It looks like an XMLA error. Did this error occur when you try to execute sales.xmla to create the cube?

    To deploy an analysis services project, open BIDS. Create a new SSAS project. Create a data source pointing to the sales database created by DDL.sql. Create a data source view from this data source. Create a cube by using Create Cube Wizard. Then right click on the solution and choose deploy.

    Alternatively, you can also create a cube on SSAS server by executing sales.xmla from SQL Server Management Studio. When doing this, don't click on "New Query" but click on "New XMLA Query" button on the tool bar.

    If you describe where and when the errors occured, I will try to help you further.

    Kind regards,

    Vincent

Viewing 15 posts - 1 through 15 (of 30 total)

You must be logged in to reply to this topic. Login to reply