Package1 and Configfile1
Package2 and Configfile2
and so on...
Currently i am running it manually one by one on SMS using integration services.
I have assigned to automate the process or consolidate into a single package.
I can automate it using execute package tasks without config file. there is no option
in the execute package task to point to the right config file.
here is the idea, we are trying to automate our weekly import process. we are running the sub packages with it own configuration file in sequence. i want to integrate the process in to a main package ?
i also want to create a job to run this main package. do i need any configuration file for the main package?
i know how to do it in sql2000 but i don't know in sql2005. can anyone point me in the right direction that would be great
I have seven SQL servers with 1 or 2 databases on each. I need to move the databases and consolidate them down to one or two servers. I am new to this and hear about detaching and attaching the databases. Is this the way to go? If so, can someone tell me how. I am sure it's not as simple as copying the way things are done in the Windows environment.
I need some advice and I think I have a possible solution, I just need some approval that it is the right thing to do!
I have 73 Databases which I look after and they are all SQL 2000 and SQL 2005 DBs and backuing up these DBs is becoming an Administration nightmare. So what I was planning is to recreate all the backup jobs jobs on a SQL 2005 Server and monitor them from there!
Is this a good idea or should I think of something else?
Can anyone point me in the direction of some best practice resources for consolidating Sql 2005 on a 64 but Unisys platform?
The web seems a bit sparse unfortunately and most of the best practice information seems oriented around 2000. This is a great article but Im not sure how much has changed in 2005 http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/64bitconsolidation.mspx .
Hi guys, can you please tell me what are steps we need to take in order to consolidate two datamarts into one? My issue us that we have two datamarts and the client wants the data in these two marts to be in one mart. Please help. I will be grateful if you refer me to any documentation if possible.
Can anyone point me in the direction of some best practice resources for consolidating Sql 2005 on a 64 but Unisys platform?
The web seems a bit sparse unfortunately and most of the best practice information seems oriented around 2000. This is a great article but Im not sure how much has changed in 2005 http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/64bitconsolidation.mspx .
1) Are there any "hooks" available to insert processing when a subscriber is about to copy data from a replicating site?
2) Is it possible for a subscriber to change only his local copy of the data - without replicating the changes back to the publisher?
I realise that once the data changes in one place it isn't really replicated anymore, and I realise that my limited knowledge of the subject might well mean I'm not even asking the right questions. Therefore, I shall try to describe as best I can my scenario.
I wish to use many servers for transactional input (to distribute the workload) and use replication to publish the inputted data to a subscribing central site. One of the tables I wish to replicate has an identity column as primary key, but the records should otherwise be unique - i.e. no two records should differ only in the value of the key. Another table, which should also be replicated, uses this id value as a foreign key.
I can use the identity increment and seed to guarantee no key violations will occur when copying data to the central server. However, there is another issue: Several servers can create the same record but with different id values.
I need to "merge" such records by deleting duplicate entries in the table with the identifier as primary key, and update the foreign keys correspondingly. To clarify (I hope!), here's an example of what data I might have on the central site after copying data from two input sites:
TRANSACTION table
amount = 200, metadata_id = 1001 // Replicated from server INPUT_1
amount = -117, metadata_id = 2001 // Replicated from server INPUT_2
METADATA table:
id=1001 Actitiy=Sales, Country=USA
id=2001 Activity=Sales, Country=USA
What I would like is basically for the central site to identify that metadata 2001 is really the same as metadata 1001, update the foreign key in the TRANSACTION record accordingly and not import (or delete, if this "merging" is done in a post-treatment) the duplicate metadata record.
If anyone can offer any advice on how to achieve this I would appreciate your input.
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 copy a large data table from one database to another every night, but I only want to copy the data since the last time the DTS job ran. I am going to create new job that writes the date of the update to a date table.
I then want the DTS job to compare the invoice date from the datawarehouse table to the last date in the Date table, and only write the data with a newer date.
I know the script if the values were in the same table - but how do I use two different tables?
I need write a code to delete DTS Packages. I'm try using the SQL-NS Objects, but not work's fine. To work first i need execute the package and after delete. Exist another method to do this task??
Can we compile the stored procedures as a package in SQL SERVER as we do it oracle and can anyone tell me how to encrypt the stored procedure so that no one can see the source code.I know with encryption option which doen't show the stored procedures in the syscomments table.
I have created a dts package on a server using the Data transformation services local package interface. I need to move this package to another server running SQL 7 but I cannot figure out how to move this package. I tried the Import/Export wizard but no luck with (license errors). any ideas from anyone? Thanks
I am actually told to move the DTS package from PreProd environment(Server A) to Production (Server B). Once the DTS packages are migrated then I have to email the DTS guid. I am not sure what I should write in the email. LOL
Hi all,I am creating SSIS packages which has flat files as data source and destination is SQLServer2005.I have successfully created packages for around 100 files. In future if the server is changed or/and the same flat file is moved to another location i cannot execute this created packages. I have to redo my work or i have to edit my packages which is a tedious job.Totally i am having around 750 files and each should have corresponding packages. Is there any better way to handle this changes.
Ummm.... else i put it in another way. Is it possible to create a Front end application in which the user gives the Server name,user name,password and the physical location of the flat files and when submitting this, SSIS package has to be created for the flat file which the user has given.
I browsed the net and found a link where they have given a way to create SSIS package using a program. Can anyone explain in detail about this.http://lakshmik.blogspot.com/2005/05/how-to-programmatically-create-ssis.html Thanks in Advance.
Hi, I'm building a portal for supervisors can view their agents errors. We have a team that have been using Access to import data and QC it. I want to get these records into SQL but at the same time, the agents need to import their own work. I've create a DTS package that will import the data into the SQL table from a folder the agents have access to. I tried to create the strored proc to be run from the ASP page however it's not working and I'm having a hard time figuring out why. Here is the procCREATE PROCEDURE DTS AS exec master..xp_cmdshell 'dtsrun /KEMTSQL02 /ADJUSTMENTS /E'GODoes anyone know what I'm doing wrong? Any help would be great. Thanks!
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 am currently running SQL7 sp3 and will be moving the database to SQL2k. I have restored the database without any problems, but have not moved the dts packages. What would be the best solution: script the packages, save the packages to the 2k db, or just build from scratch? Any feedback would be appreciated. Thanks! -J-
I am obviously new to creating DTS packages, and I am trying to create a new package. I looked in BOL for DTS samples and was able to install them from the CD. Now I have several DTS files on my hard drive. How can I open them in SQL Designer, or get them to show up in Enterprsie Manager? Any help would be appreciated. I really need help with DTS Designer basics, but cannot find anything.
Many times here I have read about scripting DTS packages to copy them to another server. How is this done? Under "All tasks/Generate SQL Scripts" there is no option for DTS. Sould I be looking elsewhere??
I am building a new server and I have got the databases from the old server imported. I would like to import the dts packages so I don't have to re-create them. Does anyone know an easy way to do this?