dbTalk Databases Forums  

XMLA script generated in UNICODE but was not in a previous versio

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss XMLA script generated in UNICODE but was not in a previous versio in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
JasonDWilson
 
Posts: n/a

Default XMLA script generated in UNICODE but was not in a previous versio - 02-22-2006 , 10:05 AM






I have a process to deploy an olap cube database to customers where I
generated an XMLA script by right clicking on the OLAP db in the object
explorer and created XMLA file. I then have a routine that modified the
connect string information in the XMLA script, saved it then executed it via
an SSIS/DTS package from the command line.
I made some changes to the OLAP cube db and had to re-generate the XMLA file
from scratch. It seems it is now being saved with a double byte character
set/UNICODE. This was not the case when I generated the previous XMLA script
perhaps with the final CTP version of SQL Server 2005.

Is this true and can I make it save the file without the double byte
character set?

I have found if I script it to the clip board, open notepad and paste it
there it is fine, but I don't want to cut and paste everything!

Thanks,

Jason

--
Jason

Reply With Quote
  #2  
Old   
Edward Melomed [MSFT]
 
Posts: n/a

Default Re: XMLA script generated in UNICODE but was not in a previous versio - 02-23-2006 , 12:28 PM






What you describe looks like a very fragile process.

Try looking at Deployment Wizard. You can run it from the command line. It
also has an option to change datasources.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights


"JasonDWilson" <JasonDWilson (AT) discussions (DOT) microsoft.com> wrote

Quote:
I have a process to deploy an olap cube database to customers where I
generated an XMLA script by right clicking on the OLAP db in the object
explorer and created XMLA file. I then have a routine that modified the
connect string information in the XMLA script, saved it then executed it
via
an SSIS/DTS package from the command line.
I made some changes to the OLAP cube db and had to re-generate the XMLA
file
from scratch. It seems it is now being saved with a double byte character
set/UNICODE. This was not the case when I generated the previous XMLA
script
perhaps with the final CTP version of SQL Server 2005.

Is this true and can I make it save the file without the double byte
character set?

I have found if I script it to the clip board, open notepad and paste it
there it is fine, but I don't want to cut and paste everything!

Thanks,

Jason

--
Jason



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.