Re: SqlServer 2005 Transfer Flame
- From: Mark Olbert <ChairmanMAO@xxxxxxxxxxxxxxxxx>
- Date: Fri, 01 Dec 2006 08:19:05 -0800
Charles,
I appreciate your prompt reply. The specific approach you described is of no use to me, as I am looking to transfer the entire
database (excluding the users, logins and roles) between the two servers. While the database is not large -- it has about 25 tables,
50 sprocs/udfs -- specifying the transfer on a table-by-table basis would be absurd. For one thing, the relatively complex set of
relations among the tables would make quite difficult (I know this because it's one of the things I tried in desperation, and gave
up in frustration). Not to mention that that wouldn't address the sprocs and udfs.
There has to be a better way. I want something similar to the old DTS wizard, which handled this kind of task simply and reliably
(as an aside, I made a rough estimate of the time it would take to transfer the database using the approach you outlined compared to
the old DTS wizard -- my estimate is that it would take about 10 times as long, not counting the learning curve -- this is
progress??). I see no reason why I should have to do a bunch of dataflow programming just to say "move this database from server A
to server B", particularly when that capability existed in an earlier version of the product.
As I am coming up on a deadline for testing a modification that I must put into production, I would like to move this discussion to
someplace where we can interact more than once a day (I have slightly less than a week). However, I am not interested in using a
support incident to cover the problem, because it looks like I'm dealing with a basic flaw in SqlServer2005. How do we go about
resolving this? Personal anger over the way Microsoft has mishandled this upgrade aside, I don't want to spend the next week on a
tirade about the company's failure -- I want to keep >>my<< customer happy, and let you guys spend your time fixing the shortcomings
in the product.
- Mark
On Fri, 01 Dec 2006 10:42:42 GMT, changliw@xxxxxxxxxxxxxxxxxxxx (Charles Wang[MSFT]) wrote:
Hi Mark,.
I do understand your concerns with SQL Server 2005. Many new features are
introduced into SQL Server 2005 which are not familar to customers
especially for those who have used to SQL Server 2000.
Also, I would like your understanding that Microsoft is not a monopoly in
database field, and apparently Oracle and DB2 rank prior to SQL Server in
market. Microsoft SQL Server indeed have a lot of places which need to
study from peers.
As a support engineer of SQL Server, I will try my best to assit you if you
encounter any issues. For now, I understand that you were trying to
transfer the data from your SQL Server 2000 to SQL Server 2005.
I am not clear if you have some special needs on the data transfer. Per my
experiences, it is easy to transfer data from SQL Server 2000 to SQL Server
2005 by using SSIS package which you can design in SSBIDS (SQL Server
Business Intelligence Development Studio).
For simple data transfer, you can refer to the following steps:
1. Create a SQL Server Integration Service project in SSBIDS;
2. Switch to the Data Flow panel;
3. Drag a OLE DB Source to the panel;
4. Drag a OLE DB Destination to the panel;
5. Create two OLE DB connections for the OLE DB Source and OLE DB
Destination by the following:
Right click the panel of Connection Managers, click New OLE DB
Connection.
6. Assign the connections to the OLE DB Source and OLE DB Destination;
7. Select the table which need to be transferred in OLE DB Source Editor;
8. Drag the output line to the OLE DB Destination;
9. Double click the OLE DB Destination and set the mappings between the
source and the destination.
Then you can execute the task.
Of cource, this is just a very simple scenario and only used to transfer a
table or a view.
To let me better understand your issue, could you please tell me more
detailed on your real requirements of your scenario?
I will be more than happy to establish a similar environment for
reproducing your issue.
I believe that we can find a resolution on this issue.
I would like to let you know that satisfying customer is our top goal and
sincerely I also hope that I can satisfy you on your issue.
Also, there are other ways to let Microsoft hear your voice, such as
Microsoft Customer Support Service ( CSS ) and online submitting feedbacks.
I would like to provide their links for your reference:
1. CSS ( telephone )
To obtain the phone numbers for specific technology request please
take a look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
2. Online feedbacks
https://connect.microsoft.com/sql
Please feel free to let me know if you have any other questions or
concerns. It is always my pleasure to be of assistance.
Charles Wang
Microsoft Online Community Support
======================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
- Follow-Ups:
- Re: SqlServer 2005 Transfer Flame
- From: Charles Wang[MSFT]
- Re: SqlServer 2005 Transfer Flame
- References:
- SqlServer 2005 Transfer Flame
- From: Mark Olbert
- RE: SqlServer 2005 Transfer Flame
- From: Charles Wang[MSFT]
- SqlServer 2005 Transfer Flame
- Prev by Date: RE: SqlServer 2005 Transfer Flame
- Next by Date: Re: ADO.NET vs OLE DB for Stored Procedure Execution
- Previous by thread: RE: SqlServer 2005 Transfer Flame
- Next by thread: Re: SqlServer 2005 Transfer Flame
- Index(es):
Relevant Pages
|
