I'm quite new to DTS, and have to modify a number of existing local
DTS packages as part of an ongoing development project. Naturally,
I'm doing these on a test server first, but so far I've failed to find
any utility which will simply copy the package definition from the
test server to the live one (or any other server, come to that)
Since some of these packages are quite complex, it is going to be very
laborious (and error prone, surely?) to have to re-write these locally
on the production server.
Is there a way of doing this, or am I missing the point somewhat?
i have an application that runs on sql server, that is all working fine on the development environment, and nearly ready for deployment in production.
a large part of this application is based on complex dts packages.
is there a straightforward way to migrate all of these packages AND change all the connections to point to the live box rather than the development box, without painstakingly changing all the connection objects (in around 100 packages!!)?
I have 100+ SQL servers registered in SQL EM. Is there a way to migrate these servers to a new PC (registry keys?) or do I have to individually register each one in the new PC? Thanks in advance for any response.
I am using ssma to migrate database from oracle 9i to sql server 2000. I successfully migrated oracle tables,views,procedures,functions etc.. But can you please help me on how to migrate packages and triggers? Here i can able to view the headings like"Triggers", "packages", "Indexes" in SSMA. But none of my oracle objects are displaying under these headings. what could be the problem?
If I use the DTSMigrationWizard.exe, to migrate my existing DTS packages from SQL Server 2000 to SQL Server 2005 will it delete the DTS packages on the 2000 server?
On this one server I have 65 DTS packages and I want to migrate them all at once if possible but still keep the DTS packages on the 2000 server.
I have a bunch of packages that all have the ProtectionLevel set to EncryptSensitiveWithUserKey (I created this as I was learning about SSIS - which I still am). I now need to put them all up on a server.
What is the best way to move them up there and still be able to run them? Actually anyone with access should be able to run them.
I've done some searching on this, and I am still having a problem finding clear information on creating packages locally and then moving them to a server. I've seen some stuff about Package Configurations and I think I can figure out how to start this from scratch, but not how to "fix" what I've already done.
I'm looking for a way to copy/migrate all of my SSIS packages from 1 SQL2005 server to another SQL2005 server. I see export/import options but they are for 2000 DTS packages. And it seems like I can only do this one package at a time, which is tedious. Anybody out there who's done all packages at once? Thanks!
Now my brain isn't quite where it should be right about now - so hopefully you will be able to put me at rest.
I have been building a new server with SQL2000 on it. Some of the stuff on our existing server is going to be migrated across - however I for the life of me cannot make any sense of how to move stuff (like DTS packages) from one server to another.
moving the Database's - no problems, but all the other guff in the tree (in Enterprise Manager) I cant seem to get.
I have 2 servers. DWTEST and DWSQL1. I developed my packages connecting to DWTEST in the design time. I have 32 packages, one of them is the master one and the others are child packages.
package PM calls P1, P2, P3,.......P31
i have 2 data source in my project. RDS and S0, both setup to connect DWTEST in the design. i defined rds_connection_string and s0_connection_string variables in my master package and created an XML config file and put those variables into that config file.
built the project into directory C:PROJECTSDEVELOPMENTS1_REUSABLE_DATA_STORES1_REUSABLE_DATA_STOREinDeployment
when i deploy my packages into DWTEST and run them as a SQL Server Agent job they work because data sources are signing to DWTEST already.
when i am deploying them(using the same manifest file in the deployment directory i wrote above) into the server DWSQL1, i select config file source as:
When i run SQL Server Agent Job i defined in DWSQL1(forcing it to use DWSQL1 data source in step definition), my master package PM connects to DWSQL1, and my child packages don't use my config definitions and connect to DWTEST which is defined in the design time.
How can i force all my packages to connect DWSQL1 server using the same built files in deployment directory WITHOUT editing my packages(recreating config files or changing the definition of Data Sources and then built the project again) in Visual Studio?
I've run into a problem with SSIS packages wherein tasks that write or copy files, or create or delete directories, quit execution without any hint of an error nor a failure message, when called from an ASP.NET 2.0 application running on any other machine than the one where the package was created from. By all indications it appeared to be an identity/permissions problem.
Our application involves a separate web server and database server. Both have SQL Server 2005 installed, but the application server originally only had Integration services. The packages are file system-deployed on the application server, and are called using Microsoft.SqlServer.Dts.Runtime methods. For all packages that involve file system tasks, the above problem occurs.
When the above packages are run using the command prompt (either DTEXEC or DTEXECUI) the packages execute just fine. This is expected since we are using an administrative account. However when a ShellExecute of the same command is called from ASP.NET, the same problem occurs.
I've tried giving administrative permissions to the ASPNET worker process user to no avail.
I have likewise attempted to use the SQL Server Agent job approach but that approach might not be acceptable for our clients since it means installing SQL Server 2005 Database services on the application server.
I have read the relevant threads in this forum, namely http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1044739&SiteID=1 and http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=927084&SiteID=1 but failed to find any solution appropriate for our set up.
We manage some SSIS servers, which has only SSIS and SSIS tools installed on them and not the sql server DB.
SSIS packages and configuration files are deployed on a NAS. We run the SSIS packages through DTEXEC by logging in to the server.
We want to allow developers to run their packages on their own on the server, but at the same time we dont want to give them physical access on the server i.e we do not want to add them into RDP users list on server properties. We want them to allow running their packages remotely on the server.
One way We could think of is by using powershell remoting and we are working on that. But is there any other way or any tool already present for the same.
I have a report that was designed using SQL Reporting Services that sits on a SQL reporting server. It's nothing too exciting, it is essentially a three page application with legal jumbo on pages 2 and 3 and applicant data in fields on page 1.
We use rectangles to force page breaks to page 2 and to page 3.
When running the report on the report server, it shows and prints fine.
When running the report from the QA website internally, it shows and prints just fine.
When running the report from the production website from a machine internally, it shows and prints just fine.
When running the report from outside of the company network, the report is jacked. It obliterates large chunks of text, crams text together, and creates blank pages.
I need help in determining where I even begin with trouble shooting this!
can anyone tell me if they know of a way to automate the update process from development servers to live server, with little interference from an administrator
I have a development team that are constantly updating their databases along with their ASP code, and want to publish changes an a weekly basis. They have asked me for a way to take their new structures, tables, procedures etc, and copy them to the live servers, but NOT to interfere with existing customer data.
Funny I know – and I hate the idea btw :(
Any references, contacts, 3rd party tool recommendations welcome,
I am in the middle of a major migraton project, moving from x86 SQL 2000 to IA64 SQL 2005. I have a business need to link to several legacy servers. I have a number of problems I am trying to solve.
1) Linking a Kerberos server to a non-Kerberos server. 2) Linking x64 or IA64 servers to x86 servers. 3) Linking SQL 2005 to SQL 2000.
Two of the errors I am encountering are: ------------------------------ TCP Provider: An existing connection was forcibly closed by the remote host. Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. OLE DB provider "SQLNCLI" for linked server "SCDC250DB" returned message "Communication link failure". (Microsoft SQL Server, Error: 10054) ------------------------------ And ------------------------------ The OLE DB provider "SQLNCLI" for the linked server "SCDC250DB" reported an error. Authentication failed. Cannot initialize the data source object of OLE DB provider "SQLNCLI" for linked server "SCDC250DB". OLE DB provider "SQLCLI" for linked server "SCDC250DB" returned message "Invalid authorization specification". (Microsoft SQL Server, Error: 7399)
If someone has worked through these problems before, I would appreciate it if you could direct me to the relevant documentation to resolve these issues.
Thanks!
Brandon Forest
Database Administrator
Data & Web Services Team
Sutter Connect Information Technologyforesb@sutterhealth.org
I have DNN installed on one server and now i need to move whole site to another server. I have moved the FTP files, and changed the conn string in config. How can i move the database? I dont have the database publishing webservice installed so i will need some other way. Does anyone know of a simple way to migrate from one sql server to another?
I'll be doing a migration of all my exisitng SQL7 databases to SQL2000. We are planning to buy new servers for the upgrade. What is the best way to move the entire database?
A) Use copy DB wizard? B) Create own DTS package to move everything? C) Script the entire DB and run it on the new server and then move the data? D) Do a backup and restore it onto the new server?
What are the best options? Are there anything that i should be aware of?
Hi I need to move some DTS packages from SQL7 to SQL2K What is the best way to do this? I realise the problem is because a SQL7 master database cannot be restored to a SQL2K master database Is there some way these can be scripted out of 7 and the script run in 2K
I am exploring the feasibility of migrating from DB2 (v7) to MSSQL server 2005. My current applications are using UDB, but the DBA wants to change to MSSQL. I believe the impact is huge. For example, how to create schema in MSSQL, how to migrate the data...
Anyone had the experience before? Could kindly suggest some reference for such a migration? Thanks!
I'm migrating from DB2 to SQL 2005 workstation. I have tried all kinds and type of migration tools. The best way so far is using the import wizard to created an SSIS package. One little problem so far. I cannot get past the "Text was truncated or one or more characters had no match in the target code page" error. I get quite a few rows before it stops. I've looked for any "invalid characters" in the source data. The row it seems to stop on doesn't make sense. Is there a way to modify the SISS package file to not stop on truncation errors? Or, can I determine the proper code page to use? I've adjusted column data types and lengths but can't find a combination that works.
- Copying to [tsi].[TSI].[CNOTES1] (Error) Messages Error 0xc020901c: Data Flow Task: There was an error with output column "CNLINE" (20) on output "OLE DB Source Output" (11). The column status returned was: "Text was truncated or one or more characters had no match in the target code page.". (SQL Server Import and Export Wizard)
Error 0xc020902a: Data Flow Task: The "output column "CNLINE" (20)" failed because truncation occurred, and the truncation row disposition on "output column "CNLINE" (20)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component. (SQL Server Import and Export Wizard)
Error 0xc0047038: Data Flow Task: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Source - CNOTES1" (1) returned error code 0xC020902A. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure. (SQL Server Import and Export Wizard)
Error 0xc0047021: Data Flow Task: SSIS Error Code DTS_E_THREADFAILED. Thread "SourceThread0" has exited with error code 0xC0047038. There may be error messages posted before this with more information on why the thread has exited. (SQL Server Import and Export Wizard)
Error 0xc0047039: Data Flow Task: SSIS Error Code DTS_E_THREADCANCELLED. Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown. There may be error messages posted before this with more information on why the thread was cancelled. (SQL Server Import and Export Wizard)
Error 0xc0047021: Data Flow Task: SSIS Error Code DTS_E_THREADFAILED. Thread "WorkThread0" has exited with error code 0xC0047039. There may be error messages posted before this with more information on why the thread has exited. (SQL Server Import and Export Wizard)
Hy all, my english is not so good so i try to explain... I have this environment
2 Servers, one is sql 2000 an the other is sql 2005 (cluster) My server 2000 is very old and we dont want to upgrade(hardaware) them and it have a lot of DTS´s packages (actually only DTS packages). I need to rewrite every package to SSIS, but my priority is take off this server transfering de DTS packages to SQL2005 and use in legacy mode.
How do i do this ?..In this moment i just want to transfer the packages to 2005 and use in legacy mode..there´s a diference between migrate and use in legacy mode ?
Hi, I was able to create an MSSQL database with the ASPNETDB.MDF file. But how do I get the Login Control to point to the MSSQL rather than the App_DataASPNETDB.MDF file?
Hello all, I have an application in which the database is currently in MySQL. The app is being re-written(in .net 3.5) and I would like to move the data to SQL Server 2005. What is the best may to get the data from MySQL to SQL Server. Any good tools out there? Idealy, I would be able to manipulate the data during the move, as I have plans for some schema changes, but I suppose I could always make them after migrating. Please suggest any tools or methods, with your thoughts. I will evaluate any suggested tools. Also, SSIS is available for me, is that the best way?
I am trying to migrate the default repository that is created when you install OLAP on a server. I have done this on my local server and several other servers without a problem. When I goes through the steps to migrate the repository it says it completes sucessfully but leave the repository pointing at the mdb file. On the other servers it has updated the pointer to the SQL database. I am running SQL2000 SP2, AS SP2 and W2000. The only difference I can find it that the server where it doesn't work also has two named instances on it. Any help would be appreciated.
Here is the scenario: We have an existing production non clustered SQL 2000 server instance that we need to migrate to a new clustered SQL 2000 server instance. We need to accomplish this without affecting the FQDN that applications use to call this server. I found this article on a solution to rename the server after an xcopy of the entire db structure. Here is the link http://vyaskn.tripod.com/moving_sql_server.htm. The other issue that we are trying to resolve is the time it takes for the snapshots of replication to run (in our case almost a full day). That is why this approach looked like it may be a good solution for us.
Here is the question: Is it possible to move our existing database to a new clustered environment without having to change the FQDN that other applications use to access this database and without having to reinitialize replication?
