Hi,

I used the deployment wizard in the analysis services 2005 to convert
it into XML script. Using the SQL Management Studio I opened it as
Analysis Server scripts and used the local host as the system in the
connections windows then loaded the XML script into the Queries window
as a XMLA query. What has to be done after this in order to use it as a
production server?

Thanks,
Somu

save the script and open it on the prod server and execute it here.

but if you can, I recommand to use the synchronization feature of SSAS to
"copy" your dev database to the prod server.
this required that you have access to both servers on the local network
(windows NT security required)
this method also synchronize the data, not just the schema.

<somuthomas (AT) gmail (DOT) com> wrote

Hi,

Yes i did try it then it says "QUERY SUCCESSFULLY EXECUTED".. Can i use

the same System as dev and production server (since i have only one
system at my disposal)??


Thanks,
SOMU

Hi,
I was able to connect with a local machine but while synchronising the
dev and production servers i am getting an error "peer prematurely
closed the conn" , " error was encountered in the transport layer" Wat
should i do to over come this...

Thanks,
SOMU

I don't know why you receive this message.

you can synchronize on the same server if you have 2 instances installed.
Else you can do a backup/restore or creating the XML/A script, changing the
database name and ID and execute this script to create the "prod" version.

<somuthomas (AT) gmail (DOT) com> wrote

Hi,

While creating the XMLA script which name of database or ID should i
give???

The name of the system in which the prod version is to be run OR name
of the system where the XMLA is created???????

Thanks,
Somu

when you generate the XML/A script from the "dev" version of your database,
the current dev ID / names are used in the XML/A result.

to create a new database in SSAS based on new name and a new id, change
these ID and name in theXML/A file and execute the modified script.
This create a complete new database with the exact same structure as the
first version but with a new name.

where your execute this script will create the databse on this server.

if you have 2 distinct servers (or 2 instances of SSAS ) changing the ID /
name is not required if you want the EXACT same name on the prod server.

<somuthomas (AT) gmail (DOT) com> wrote