Tag Info

Hot answers tagged

7

I don't think there is a better option than scripting your job. You can modify the script as required and reapply it to any number of SQL instances (always backup your system databases before apply scripts).


6

After continuing to dig around I finally found an article in MSDN that covers installing advanced services without installing SQL Server. That got me pointed in the right direction: The Crux of my mistake is that I thought of this as 'adding a feature to an existing instance of SQL Server 2008.' Therein lies my flaw. In the install process there is an ...


4

Yes, it is very much possible. You can define connections to a myriad of external datasources from within an SSIS package. SQL Server, Oracle, Excel, flat files, etc etc. Just remembered one gotcha when dealing connecting to Excel via SSIS in a 64-bit environment. You need the 32-bit client tools installed on your 64-bit SQL box in order to interface ...


3

SSIS is on the SQL 2005 installation disk. To install it, just pop the disk in and start the installation wizard. You can then install SSIS as a package, and just make sure you don't tick any of the database engines, or else you'll get another SQL instance installed!


3

disable or remove the foreign key constraints before the data import & then enable or add them after the import eg. remove/add --drop alter table t1 DROP CONSTRAINT fk_1 --add alter table t1 WITH CHECK add constraint fk_1 foreign key (fk) references t2 (i) disable/enable --disable alter table t1 NOCHECK CONSTRAINT fk_1 --enable alter table t1 WITH ...


3

If the packages are stored in MSDB then no, the only date/time stamp is the creation date. Modified date is not tracked. You would need to delete the package prior to redeploying in order to track a modified date, which is essentially just forcing the create date to be your redeploy date. In SQL 2005, the metadata for packages stored in MSDB is stored in ...


2

There is an a destination for Access database, as long as the Access database already exist. You would add your SQL Server 2005 and the Access database to the connection manager. Then chose the OLE DB source and destination within your data flow. It will allow you to chose the Access connection as your destination. Now if you are wanting to create the ...


2

Yes, you can transfer data between 2005 and 2008. The big gotcha you need to look out for is that the SSIS packages themselves can't be moved between the two. If you create the package in 2005, it needs to run in 2005. You can convert the package to 2008, but then it needs to run in 2008.


2

Help came from another forum: MSDN forum with correct answer "The SQL Server uses the SID's of the User, not the name. On the other Server the same User has another SID. I suggest to change the Job Owner to "sa". That should work. Later you can change the Job Owner back to CBMIWEB\johna."


2

Assuming these "external URLs" are actually resolving to local addresses, and again assuming that you don't have any DNS issues, no, this really shouldn't make a difference at all. As for high network activity, what exactly are you seeing? EDIT I'm taking a wild stab here (as I know very little of SSIS and the internal workings of MS SQL in general), but ...


2

If both instances are on the same system, the only performance "hit" you'll see when using the fully-qualified domain name is for the DNS lookup. Assuming your DNS server (or hosts file) remains accessible, the performance impact of this will be negligible. IP will use the system's loopback interface when accessing those FQDNs, so the external network won't ...


2

You need to export the package back to a file to be able to edit it. There isn't a way to edit the files which are stored in the MSDB database. If memory serves you should be able to right click on the package in Management Studio and export the package. Then add it to the project and you can then edit it.


2

you can use freeTDS (or jTDS if you use that thing called java) to give you access to your sql server from Unix/AIX. From FreeTDS you can authenticate against SQL Server & run any T-SQL you like. You can "trigger" the SSIS job by calling the sproc sp_start_job which resides in MSDB to kick off the job by name or job_id.


2

Try the 'ragged right' option mentioned here : http://weblogs.asp.net/guystarbuck/archive/2008/01/31/ssis-flat-file-export-quot-fixed-width-quot-vs-quot-ragged-right-quot.aspx


2

The projects themselves are not stored in MSDB, only the compiled packages. You have to have an existing SSIS / BI project in your file system / source control / etc in order to open/edit or deploy. If you don't have the original project you can import an existing package into a new project. Create a new Integration Services project In the Solution ...


2

After good suggestions made by bilinkc, and without knowing where bottleneck is I would try another few things. As You already noted, You should work on parallelism, not processing more data (months) in the same dataflow. You have already made transformations run in parallel, but source and destination (as well as aggregation) is not running in parallel! So ...


2

Solution to your problem is to use different subnet for the second interface than the interface used to connect the application server. So that both the communications i.e source to application server and source to database server will be isolated from each other.


2

I had this same issue. After some research and convincing the server I didn't have control over to add a Windows Authenticated account to there location and some insight from the below URL, I got it working: ...


2

You cannot run SSIS package on a release that is below the developed level of the package, so it is not possible to deploy from SQL Server 2012 to SQL Server 2008 since SSIS packages are not backwards compatible. This the SSIS engine issue. See more here: Interoperability and Coexistence (Integration Services) From the documentation: On an instance of ...


1

Have you verified you're not using a 32-bit driver on a 64-bit OS? http://support.microsoft.com/kb/942976 32 = C:\Windows\SysWOW64\odbcad32.exe   64 = C:\Windows\System32\odbcad32.exe


1

Ok well I found the problem...by default MS puts the MySQL db and table name in quotes. I remove the quotes and I can finally map the tables together. Yet another problem though...for another post.


1

If you can configure the VPN client not to change your default gateway, you shouldn't have any interruption to your internet connection. The only reason you lose your internet connection is because the VPN client adds a new default route to the VPN server at the other end of the tunnel, forcing all traffic through the VPN. Almost all VPN clients I've ever ...


1

Assuming the source server is Windows, you could add a static route to the backup server via the second interface. example interface A 192.168.1.10, Interface B (for backups) 192.168.1.11. Backup server 192.168.1.50 from an elevated command prompt, type route print and take note of the Interface List at the top of the output. Identify the interface on ...


1

Well, it turns out this was an authorization or identity issue. My application was setting Thread.CurrentPrincipal to a custom IPrincipal instance on every request. Below is a paraphrasing of the code: Public Class AppPrincipal Implements IPrincipal ... End Class ... Then in Global.asax.vb Sub Global_AcquireRequestState(ByVal sender As Object, ByVal e ...


1

The part of those log files that stood out for me was this: Source is invalid due to invalid package code (product code doesn't match) Google turned this up which looks relevant to me: http://blogs.msdn.com/b/psssql/archive/2009/07/23/sql-server-setup-prompts-with-the-installed-product-does-not-match-the-installation-source-s-part-i.aspx


1

See comments. RebEx SFTP is used.


1

SQL Server 2005 Express (and Workgroup) Edition BI Development Studio only includes the Report Designer.


1

You need to restart the SQL Server Agent. I've run into problems similar to this and that has fixed my problem.


1

Another thing can you go to Start->Control Panel->Administrative Tools->Services and ensure you have a listing for SQL Server Integration Services. If not you will need to go to Control Panel->Add/Remove Programs->SQL Server and change the options and ensure you have installed SSIS. If the SSIS service is not installed you cannot run packages correctly and ...


1

A quick search returns plenty of possible causes for this error, such as this: SSIS Error from DTEXEC: Login timeout expired. Have you worked through these already?



Only top voted, non community-wiki answers of a minimum length are eligible