Annoying omission in SQL Server Import and Export Wizard

In SQL Server 2000 - using the IMP-EXP WIZ had => on the very last screen
before the commit - there is a listing of the SOURCE SERVER NAME and the
DESTINATION SERVER NAME. For some unknown reason, this has been removed.
It is the best double check I have to make sure that I am NOT moving test
data to production but actually moving live data to a test server. NOT
having this check is truly annoying! It would be a vast improvement if this
wizard [behaved as it did in SQL Server 2000]!
Regards,
Jamie
Good suggestion. You can submit your product feedback directly to Microsoft
using via Connect (http://connect.microsoft.com/SQLServer). You and others
can vote as well.
Hope this helps.
Dan Guzman
SQL Server MVP
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:5025EC4F-9139-41FE-B715-15B73DED67D8@.microsoft.com...
> In SQL Server 2000 - using the IMP-EXP WIZ had => on the very last screen
> before the commit - there is a listing of the SOURCE SERVER NAME and the
> DESTINATION SERVER NAME. For some unknown reason, this has been removed.
> It is the best double check I have to make sure that I am NOT moving test
> data to production but actually moving live data to a test server. NOT
> having this check is truly annoying! It would be a vast improvement if
> this
> wizard [behaved as it did in SQL Server 2000]!
> --
> Regards,
> Jamie
|||Complete.
Regards,
Jamie
"Dan Guzman" wrote:

> Good suggestion. You can submit your product feedback directly to Microsoft
> using via Connect (http://connect.microsoft.com/SQLServer). You and others
> can vote as well.
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:5025EC4F-9139-41FE-B715-15B73DED67D8@.microsoft.com...
>
|||Don't forget to vote on your own submission!
Hope this helps.
Dan Guzman
SQL Server MVP
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:7E6A15C5-ADC8-4959-AC94-415821F89B2A@.microsoft.com...[vbcol=seagreen]
> Complete.
> --
> Regards,
> Jamie
>
> "Dan Guzman" wrote:

Annoying omission in SQL Server Import and Export Wizard

In SQL Server 2000 - using the IMP-EXP WIZ had => on the very last screen
before the commit - there is a listing of the SOURCE SERVER NAME and the
DESTINATION SERVER NAME. For some unknown reason, this has been removed.
It is the best double check I have to make sure that I am NOT moving test
data to production but actually moving live data to a test server. NOT
having this check is truly annoying! It would be a vast improvement if this
wizard [behaved as it did in SQL Server 2000]!
--
Regards,
JamieGood suggestion. You can submit your product feedback directly to Microsoft
using via Connect (http://connect.microsoft.com/SQLServer). You and others
can vote as well.
Hope this helps.
Dan Guzman
SQL Server MVP
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:5025EC4F-9139-41FE-B715-15B73DED67D8@.microsoft.com...
> In SQL Server 2000 - using the IMP-EXP WIZ had => on the very last screen
> before the commit - there is a listing of the SOURCE SERVER NAME and the
> DESTINATION SERVER NAME. For some unknown reason, this has been removed.
> It is the best double check I have to make sure that I am NOT moving test
> data to production but actually moving live data to a test server. NOT
> having this check is truly annoying! It would be a vast improvement if
> this
> wizard [behaved as it did in SQL Server 2000]!
> --
> Regards,
> Jamie|||Complete.
--
Regards,
Jamie
"Dan Guzman" wrote:

> Good suggestion. You can submit your product feedback directly to Microso
ft
> using via Connect (http://connect.microsoft.com/SQLServer). You and other
s
> can vote as well.
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:5025EC4F-9139-41FE-B715-15B73DED67D8@.microsoft.com...
>|||Don't forget to vote on your own submission!
Hope this helps.
Dan Guzman
SQL Server MVP
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:7E6A15C5-ADC8-4959-AC94-415821F89B2A@.microsoft.com...[vbcol=seagreen]
> Complete.
> --
> Regards,
> Jamie
>
> "Dan Guzman" wrote:
>

Announcing - SQL Server Database Publishing Wizard CTP 1

The SQL Server group at Microsoft has just launched theSQL Server Hosting Toolkit with the release of theDatabase Publishing Wizard Community Technology Preview 1.

The objective of the SQL Server Hosting Toolkit is to enable a great experience around hosted SQL Server. The Database Publishing Wizard works toward this mission by making it easy to upload a database from a development box up to a shared hoster. In its first incarnation, the Database Publishing Wizard is a command line tool that generates a T-SQL script designed to be executed in the script execution windows provided by most hosters in their database management consoles. In the coming months we'll be adding a GUI and building seamless integration between the tool and an upload service we'll provide to hosters for deployment.

Details on the Database Publishing Wizard as well as the download can be found athttp://www.codeplex.com/Wiki/View.aspx?ProjectName=sqlhost&title=Database%20Publishing%20Wizard.

We plan to be releasing advances in the Toolkit frequently so check out this first CTP and give us your feedback!

Thanks,

Dan Winn

Senior Program Manager, Microsoft SQL Server

Does the SQL Server Hosting Toolkit work alongside Visual Web Developer ?
Will it transfer ASPNETDB.MDF across to a shared SQL 2005 server - without having to write stacks of code ?
Will new ASP users be able to use it ?

Good to see that Microsoft is responding, otherwise you are going to frustrate a lot of VWD newbies ...

Just seen that DiscountASP.NET have a SQL 2005 Attach MDF Tool ... it seems they have recognised that thousands of new VWD user are having real problems moving databases from local to server.

|||

this is a great little tool, thanks for making it available! I've been looking for a utility to pull an image of a hosted database for some time but had no luck finding it. This tool actually works to pull data of a remote SQL 2000 Server.

Whatever you add in the future, please keep the command line available. That will enable this tool for backup purposes.

For a moment I was confused when I could not open the result file in vim. Apparently the format is unicode or whatever 2 byte character encoding is called. I think it would be useful if there was an option to generate plain-simple 1 byte character text files. If only because the size gets cut in half :)

|||

Thanks for your feedback Nocturnal. We'll definitely be keeping the command line. Interesting idea on the single byte text output. The problem would be potential data loss, but we might be able to detect that and throw an error...

By the way, check out the new CTP we just released athttp://www.codeplex.com/sqlhost

Thanks,
Dan

|||darn! a perfect tool for me... only if the source database supports sql server 2000. I'm pushing it the other way around, 2000 to 2005. :(|||I use it with SQL 2000. Did you try and did it not work?|||

Yeah, it didn't.

My source table is 2000, targe is 2000 as well, publish schema only. Get an error while in Gathering list of objects to script. says need 2005 or later. :( had to use the Red Gate sql compare instead.

|||

Very Very Good efforts by the team.

This tools are very much appreciated and welcomed.

I think backup, restore facilities should be included in future versions they are a must. I think dotnet panel is utilising them very smoothly.This could be a disadvantage for users if their host is providing some panels and this is a common scenerio.

----------------------------------------
A little information required here...

What if i upload a new data from my local SQL2005 to remote SQL2005. I just want my local sql2005 to be along with remote sql2005, i do not want to over write the remote sql2005. Is it possible...?

e.g:- my remote has 10 datas. I want to add 2 datas more from my local sql2005 to remote sql2005 to make it 12 datas on remote.
If i over write it will become 2 on remote, i will looose 10 datas.

I hope i have cleared. Thi facility if not added to day, should be considered for future
--------------------------------------------

I was surprised no one has mentioned the links for great tutorials for this tool by Mr. Scott Guthrie.

Any how its here...

Tutorial 1

and

Tutorial 2

Cheers!

|||thank you!|||I would like to be able to select which tables, views, functions, and stored procedures to move.|||

We are currently using the Team Edition for Database Pros plug in for VS Team Suite, along with Web Deployment Projects and Team Build for Team Foundation Server.

Do you think this new utility has a place in that kind of environment? Currently, the database project generates a SQL deployment script when we do a team build, and we can also use the database project's Schema Compare and Data Compare to sync our live databases.

|||;) Good to hear. Very appreciated. I will have a look at it|||

Same problem tried with Sql 2000 and failed :(

|||

I tried with SQL 2000 but got an errors.

DBMaster

MyBlog

Analysis Services Migration Wizard

I backedup an SQL2K OLAP database. Learned that I can not use the cab file to restore it to an SQL2005. So I've restored it to another SQL2K. Now I am trying to migrate this to my 2005. Here are my tests and results.

1. Welcome screen works fine. :)

2. I have severel SQL2K servers here which have their OLAP services running.

a.) SQL 2000 Source Server: xxxxxxxxx (no such server)
SQL 2005 Destination Server: AATIK (right server-local)
Error: Source server: The following system error occurred: .

b.) SQL 2000 Source Server: SABRI (right server)
SQL 2005 Destination Server: AATIK (right server-local)
Error: Source server: The following system error occurred: .

c.) SQL 2000 Source Server: SONAY (another right server)
SQL 2005 Destination Server: AATIK (right server-local)
Error: Source server: ActiveX component can't create object

d.) SQL 2000 Source Server: SONAY (another right server)
SQL 2005 Destination Server: xxxxxxxxx (no such server)
Error: Source server: ActiveX component can't create object

e.) SQL 2000 Source Server: SONAY (another right server)
SQL 2005 Destination Server: (local) (got bored of typing AATIK)
Error: Source server: ActiveX component can't create object

I've also tried "localhost", ".", "aatik", "aatik\aatik" etc. for destination server.

Is it a bug in Turkish for letters I and i ?

By the way SP1 is installed.

Thanks.

You can take destination out of the picture by specifying script file as a destination.

Looks like you are having problem connecting to AS2000 source server.

Take a look if you can access AS2000 sever remotely. Can you access it from Analysis Manager running on another machine?

You also have an option of running AS2000 and AS2005 on the same machine.
You can rename your AS2005 sever to become a named instance. Install AS2000 locally, restore your databases and then migrate a databases.
Uninstall AS2000 and then rename back AS2005 to be a default instance.

To rename AS2005 instance you can use ASInstanceRename.exe located in your C:\Program Files\Microsoft SQL Server\90\Tools\binn\VSShell\Common7\IDE folder.

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

|||

Thanks Edward.

Tried the scriptfile option but again got the same ActiveX error message.

Analysis Services Migration Wizard

I backedup an SQL2K OLAP database. Learned that I can not use the cab file to restore it to an SQL2005. So I've restored it to another SQL2K. Now I am trying to migrate this to my 2005. Here are my tests and results.

1. Welcome screen works fine. :)

2. I have severel SQL2K servers here which have their OLAP services running.

a.) SQL 2000 Source Server: xxxxxxxxx (no such server)
SQL 2005 Destination Server: AATIK (right server-local)
Error: Source server: The following system error occurred: .

b.) SQL 2000 Source Server: SABRI (right server)
SQL 2005 Destination Server: AATIK (right server-local)
Error: Source server: The following system error occurred: .

c.) SQL 2000 Source Server: SONAY (another right server)
SQL 2005 Destination Server: AATIK (right server-local)
Error: Source server: ActiveX component can't create object

d.) SQL 2000 Source Server: SONAY (another right server)
SQL 2005 Destination Server: xxxxxxxxx (no such server)
Error: Source server: ActiveX component can't create object

e.) SQL 2000 Source Server: SONAY (another right server)
SQL 2005 Destination Server: (local) (got bored of typing AATIK)
Error: Source server: ActiveX component can't create object

I've also tried "localhost", ".", "aatik", "aatik\aatik" etc. for destination server.

Is it a bug in Turkish for letters I and i ?

By the way SP1 is installed.

Thanks.

You can take destination out of the picture by specifying script file as a destination.

Looks like you are having problem connecting to AS2000 source server.

Take a look if you can access AS2000 sever remotely. Can you access it from Analysis Manager running on another machine?

You also have an option of running AS2000 and AS2005 on the same machine.
You can rename your AS2005 sever to become a named instance. Install AS2000 locally, restore your databases and then migrate a databases.
Uninstall AS2000 and then rename back AS2005 to be a default instance.

To rename AS2005 instance you can use ASInstanceRename.exe located in your C:\Program Files\Microsoft SQL Server\90\Tools\binn\VSShell\Common7\IDE folder.

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

|||

Thanks Edward.

Tried the scriptfile option but again got the same ActiveX error message.

Analysis Services 2005 Deployment Wizard doubts

As I understand it SSAS encrypts its data by default; however, I'm looking for strategies on encrypting data in the underlying datawarehouse. If you have a column encrypted in the datawarehouse, what are the options to expose that data, selectively of course, through Analysis Services? The only solution I've found is to bind a dimension to a view in the datasource and have that view decrypt the column. The dimension attribute could then be selectively exposed based on the role(s) the user has access to.

Is this the BEST way to do it? Are there other options and considerations? Are there any great whitepapers on this subject? I haven't found any myself.

Thanks in advance,

Terry

Havent seen any whitepapers on the subject.

Another idea for you to consider is to create a named query in Analysis Services DSV. See if you can use that to skip creating a view in relational database.

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

|||I am working with SQL server 2005 analysis and reporting services. I am

instructed to create a cube for a database using analysis services and
then replicate it so as to produce reports online by reporting services

when requested by clients. I am able to create the cube and also deploy

the report made, in HTTP separately. But the following doubts arise
during the Cube deployment:

The Cube was created as per the requirements by my team lead. Then 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 and executed it. What has to be done after this in
order to use it as a production server?

Once the production server is setup and the connection is made with the

staging server, How can we set the timings to when the updating of the
production server has to be set in terms of hours, days or weeks?

Hoping these doubts would be clarified as early as possible.

Analysis Services 2005 Deployment Wizard

Hi,
I used the deployment wizard in the analysis services 2005 to convert
the cube 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
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

Analysis Services 2005 Deployment Wizard

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,
SomuHi,
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|||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

Analysis Services 2005 Deployment Wizard

I am working with SQL server 2005 analysis and reporting services. I am

instructed to create a cube for a database using analysis services and
then replicate it so as to produce reports online by reporting services

when requested by clients. I am able to create the cube and also deploy

the report made, in HTTP separately. But the following doubts arise
during the Cube deployment:

The Cube was created as per the requirements by my team lead. Then 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 and executed it. What has to be done after this in
order to use it as a production server?

Once the production server is setup and the connection is made with the

staging server, How can we set the timings to when the updating of the
production server has to be set in terms of hours, days or weeks?

Hoping these doubts would be clarified as early as possible.

Take a look at the Synchronization functionality in Analysis Services. It allows you to synchronize on database to another using single command.

In your case I can imagine, you having updates done to a single master server, and then running sycnhronization commands against multiple servers telling them to synchronize the changes happend on the master.

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

Analysis Services 2005 Deployment Wizard

Hi,
I used the deployment wizard in the analysis services 2005 to convert
the cube 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,
SomuHi,
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