I have approximately 250 dts packages. I moved all of the packages over to the new server, using dts. But now I need to change the server name to point to the new server and keep the transformations. is there a better way than having to open every package and editing?
I previously installed SQL 7.0 on my machine. The name of the Server was DEVELOPMENT. Unfortunately I needed to change the computer name, but I had already created my databases and did not want to lose the information. It was suggested that I should simply change the computer name and reinstall SQl. I changed the name to DEVSERVER. This seemed to work fine. Now I am having a problem when I try to create a DTS package on the renamed server from another SQL server . I receive the following error. "A connection could not be established to Development. Specified SQLserver not found" The server which is now called Devserver, is registered on the server I am creating the package from, however the message seems to imply that the server I'm connecting to is still called Developement and cannot be found. Any ideas would be appreciated.
I had a few packages created with Windows Authentication which now needs to be migrated to run with SQL Server Authentication. I tried changing it in the connection managers but the packages failed to validate at the SCD transformations.For a few packages I had Configuration files for these packages where i tried to do it but it dint run giving the following Error Message: [Connection manager "Target"] Error: An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user <<with my network id>>.".
[Execute SQL Task] Error: Failed to acquire connection "Target". Connection may not be configured correctly or you may not have the right permissions on this connection.
My need is to load data from flat files to SQL tables. All the flat files are different. For convenience flat file name and table name is similar. I have placed a For loop container and in which I used SCRIPT TASK to read the file names from the specified folder and i populated this value to SSIS variable. All my flat file name and destination table name are given using this Script task. For the first run it executes perfectly, but for the second run it fails. The reason is due to the flat file connection manager. The file name is changed since it is taken care by my script, but the columns are not mapped it still have the previous file's columns. I do not know how to solve this.
Please tell me if there is any other way to solve this or i need to refine my process.
Actually i have more than 100 files and so i am trying to do it at one short rather than creating individual packages.
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.
Is there a way to change an image data type? I want to make a change to some deployed SQL 2008 SSIS deployed packages. I have a TSQL SELECT that searches the packages for a string. But I would like to be able to change a string. I have googled it but cannot find anything.
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.
Please can anybody help me in transferring existing SSIS Packages saved in a shared folder location from development server 2ED to Live server TWD1. Both has SQL server 2005 running and has visual studio 2005 Currently about 25 SSIS packages are executed from the development server transferring data on Live server TWD1...these ETL process is called from development server but executed on live server. Now the problem is when i call these packages from the shared folder from live server it crashes.....i need to changes something to shift the whole package to the live server..and execute on live server itself instead of recreating the whole 25 process from scratch.....also i use optimize for many tables ..and run in a single trancastion....so how can i see the mappings of source and destination tables.
Please let me know the process how i can achieve this. Thanks George
I am trying to copy/update a table which is in server2 based on a similar table which is in server 1. I can't use replication, so I am thinking which are the best ways to do without affecting the performance as the source table is busy with inserts or updates. I am thinking of following options: 1. SQL server 2000 DTS packages: As I am trying to copy the data from the source table(server1) into a destination table which is a similar table in server2, if I use dts first I want to take the complete snapshot and then on I only want to copy the new transactions or updated transactions, please let me know how I can do this. 2. Does trigger affect the performance as the server1(source table) is a busy server. Please let me know. Thanks.
How do you tranfer data between two SQL Server 2005 databases???? I swear I looked all over the place, but I don't see how it is done in SQL Server 2005.
Hi, I was just wondering if SQL Server offers Packages as an option as Oracle does? I just worked on an oracle project and I thought the idea of creating packages to house stored procedures and functions to be really cool and I was wondering if SQL server offers the same option. Thanks in advance.
Hope somebody out there can help with a little problem we are experiencing.
We have an SQL Server 7 database app that has a number of DTS packages used to import data. An access 97 front end has been written to run these DTS packages. Access runs the DTS packages directly using the DTS objects.
The system works fine on the server (NT 4.0 SQL Server 7.0 sp2) but when we try to run the DTS packages from a client, we get an error 'DTS Error -2147024809 Invalid parameter'.
I've tried looking up this error message and am getting nowhere. Maybe somebody out there has come across this problem before and can hopefully shed some light on it.
I should also mention that the client machine we run it from is Access 2000 (may be the problem????) and we can't recreate the problem here, only out at the client site.
We will migrate our SQL 7.0 databases into SQL 2000 on another server. Since I have hundreds of DTS packages on my Repository, is there a better way of transferring to the other server's Repository then ... Package -> Save As -> choose server and location etc,etc...? Thanks, Suat.
I am new to this, SQL Server. I hv worked in Oracle. Now I am learning 'SQL Server'. In Oracle, it has features like Packages and functions (PL/SQL), like that in SQL Server, is there any facility available?.
Hi, all. I have more than 100 DTS packages on one server which need to be migrated to another new server. What's the easiest way to do it? I can do it by opening each package then using save as to save into another server. But I have more than 100, so it is kind of tedious to do it.
Is there a way like export those packages then import them? Or script them then run it? If yes, Let me know how.
I understand that packages can be stored in the MSDB database. However, is it possible to store packages in another database and have them managed by the SSIS service?
I have a SQL Server 7.0 backend server but I am using SQL Server 2000 EM to create DTS packages. Can the DTS packages be opened in SQL Server 7.0? We are contemplating the install of SQL 2000 but we are worried that any new DTS packages created won't work when opened on a SQL Server 7.0 server or that the SQL 2000 DTS functionality is just not compatibile with SQL Server 7.0 and will cause problems.
I have been trying to move dts packages from one server to another server. I used the DTSBackup Utility to backup all the packages. The restore will not work.
If you know how to transfer Packages please let me know.
I have been trying to get a clear explanation on what I need to do in order to be able to execute SSIS packages which I have located on an app server. Is it that I need integration services installed on the app server itself and thats it? Or can someone tell me if there is any more to it, thanks folks!
With DTS you could copy and register some DLLs onto a non-SQL Server PC and run Packages. Is this still possible with SSIS? I imagine that, at the very least, you would have to copy dtexec.exe and the *,dtsx files to the other computer.
I have created my packages and i want them to place them on the server.Do i need to place the entire project of dts packages on the server or is there any option to place executables...if so please explain....
And to run these packages on the server do i need to set them as new job at sql server agent or is there any other way i need to run on the server.
I want then to run whenever the text file gets updated is it possible to set anything for my packages to run as and when the text file gets updated..
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.