Scripting a SSAS database locks up in SQL Server 2008 Management Studio - by Terry Smith

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


3
0
Sign in
to vote
ID 418476 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 2/26/2009 12:10:12 PM
Access Restriction Public

Description

When attempting to script an analysis services database, Management Studio locks up.

Right-click a SSAS database -> Script Database as -> Create To -> New Query Editor Window 

Management Studio will lock up and the XML script will never be displayed. We have replicated this on user workstations and development servers.
Sign in to post a comment.
Posted by Microsoft on 3/30/2009 at 1:09 PM
Hi Terry.
For what it worth.

Here is simple piece of C# code that you can use to generate a create statement for your database. You wouldnt need SSMS for that and performance should be better:

using Microsoft.AnalysisServices;
using System.Xml;

Server server = new Server();
server.Connect("localhost");
Database db = server.Databases("MyDatabase");

XmlTextWriter xmlwrite = new XmlTextWriter("MyDBScript.xmla", System.Text.Encoding.UTF8);
xmlwrite.Formatting = Formatting.Indented;
xmlwrite.Indentation = 2;

Scripter.WriteAlter(xmlwrite, db, true, true);
xmlwrite.Close();

HTH
Edward Melomed.


Posted by Microsoft on 3/9/2009 at 5:07 PM
Hi,
I am the dev lead for this area. I have tried to script out a database and it works for me. Given that it takes you so long but does eventually finish, it most likely has something to do with the structure of your database. Is there anything interesting about your schema that we should know about? Is it possible to give us the generated UDM (which should not have any data) so we can recreate your database and then try to script it back out?

Thanks
Posted by Terry Smith on 3/6/2009 at 12:21 PM
"Unfortunately, without a repro, it is difficult to diagnose the problem."
-- Have you even tried? Can you not at least try to verify it with an internal Microsoft UDM? What do you expect me to do. Design a new, non-proprietery database, script it with data and send it to you?

"If this continues to be an issue for you"
-- It's been a problem every day since we have "upgraded" to SQL Server 2008. Do you think the problem will just disappear or something?

"please contact your Customer Support Service representative and work with them to get a repro"
-- Who are you then? What is this forum for? Are you not my customer service representative? Is there a 1-800-number for SSAS bugs or should I just call the Microsoft campus switchboard?
Posted by Microsoft on 3/6/2009 at 11:45 AM
Thank you for updating this issue with your information. Unfortunately, without a repro, it is difficult to diagnose the problem. If this continues to be an issue for you, please contact your Customer Support Service representative and work with them to get a repro.
Posted by Terry Smith on 3/5/2009 at 7:24 AM
A dumb is never generated, and I can't share our SSAS database. After further testing I can concur with the comment further below that the operation does complete after a very, very, very long time.
Posted by Microsoft on 3/2/2009 at 4:07 PM
Thanks for the additional information. Can you please attach a mini-dump. db, etc. for us to refer to so that we can try to repro the issue?

Thank you.
Posted by PlasticLizard on 3/2/2009 at 8:51 AM
This is killing us as well. Actually, the scripting operation *will* complete after some tens of minutes, but it is locked up for all intents and purposes.