Sql Server 2008/SSIS: Transfer Sql Server Objects Failing, No Useful Debug Information Generated -


I am trying to copy a SQL Server 2008 database from a production server to the development server. I have set up a new empty target database, and a transfer SQL server objects are added to the control flow panel. I have configured the task to use the SMOServer connection (both of the tests are OK). I have tried to copy all the items and have just copied those people I want to. I have set it to drop the destination first, though there is nothing in the target database.

Still refuses to do this work and it does not fully generate any error information, despite the fact that I have tried to find every logging option that I can find. All I get success in the verification phase is a series of warning that some sections of objects are not present to copy (which is correct), "hang" in the "yellow area" (i.e., the work box is Yellow is highlighted in.)

How can the world be so simple, straightforward, and often copied as a database, so hard darn? What am I doing wrong? In addition to using SSIS, I mean :).

p.sh. Every time - every time - I try to use SSIS to do something that is easy to drop-dead, it ends with being the royal pitt. IMHO is one of the worst written pieces of Microsoft's development software That has ever been offered on the world. I believe that anyone who keeps his charge in Redmond, he will sit in front of me ... so that the 10,000 sun can experience the heat of anger and despair.)

Edit:

In response to Diego's response, let me tell you that I do not have access to the cisdomin on the server where the source database is Is on a third party hosting service.

Also, for this problem, my "solution" target server includes import data from within SQL Server Management Studio. This is not a good work - except for all keys, triggers, spreads etc. Gives - at least my core data has been exceeded.

But I also went into a problem because I was using "non-integrated security" on the source server but integrated safety on the destination / target server. There is nothing to point to the problem in doing anything like this in the wizard, but it has been revealed that it will cause the SSIS package generated to fail. Safety approaches on both "ends" of the transaction have to match.

Sometimes 10,000 suns are not enough:) I understand your frustration, SSIS actually To deal with the situation can actually be different, but it is a very powerful tool.

However, I will ask you to start by checking permissions. Earlier I had problems, from which I was selected "Drop Destination objects first" and my user was not allowed to make a login, so they were previously dropped and when it was time to recreate them, the package failed Staying logged in without leaving an example and locking me with SQL

In fact, I would have written something on the component, before deletion, to check, if I want to hide the object There was permission to stop such situations.

Yes, by the way, try running your package with a SYS administrator user, for example

Comments

Popular posts from this blog

Python SQLAlchemy:AttributeError: Neither 'Column' object nor 'Comparator' object has an attribute 'schema' -

java - How not to audit a join table and related entities using Hibernate Envers? -

mongodb - CakePHP paginator ignoring order, but only for certain values -