| Author |
Topic |
|
arkiboys
Master Smack Fu Yak Hacker
1433 Posts |
 Posted - 2012-04-30 : 07:35:16
|
| The ssis package uses a flat file connection manager in which I have used a text qualifier " which is double quotes.The column separator is set to be , which is commaEverything works fine in Dev.After carrying out alot of testing, I see that in PROD, this double quotes does not seem to be recognised.For example, if a column is like "Hello, I have a comma"It splits it into two columnsAfter alot of re-search, I think the problem is that the prod server is indeed not able to understand the double quotes.How can I solve this issue in PROD machine please?The DEV server in which the ssis package works has the following version:Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor) The PROD server in which the ssis package DOES NOT work has the following version:Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor) Any thoughts please?Thanks |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-04-30 : 10:25:13
|
| have you set text qualifier correctly in the flat file connection manager?------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
arkiboys
Master Smack Fu Yak Hacker
1433 Posts |
Posted - 2012-04-30 : 10:55:32
|
| yes, but it seems I have to install SP1 on the prod machine and that is why it does not understand the " for text qualifier |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-04-30 : 11:02:04
|
| i didnt understand why you still have RTM version in prod though. In ideal scenario you should be applying service packs to prod------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
arkiboys
Master Smack Fu Yak Hacker
1433 Posts |
Posted - 2012-04-30 : 11:19:40
|
| do you think applying sp1 will fix this issue in prod? |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-04-30 : 11:23:35
|
| you can definitely try that. Particularly look for SSIS versions in both servers and then take a call------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
arkiboys
Master Smack Fu Yak Hacker
1433 Posts |
Posted - 2012-04-30 : 11:54:10
|
| Thanks |
|
|
|
arkiboys
Master Smack Fu Yak Hacker
1433 Posts |
Posted - 2012-04-30 : 11:59:31
|
quote:
Originally posted by visakh16
you can definitely try that. Particularly look for SSIS versions in both servers and then take a call------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/
How can I check the ssis versions on both machines? |
|
|
|
yosiasz
Master Smack Fu Yak Hacker
1635 Posts |
Posted - 2012-04-30 : 13:26:03
|
| is this a physical machine or virtual the prod server? if you are leery about applying sp1 and if your prod server is virtual you could clone it/back it up or whatever, bring it to a pre prod env disconnected from network, apply sp1, test out your SSIS using a local version of that file.or create an identical server in pre prod, back up and restore prod db to this new server and test things out.<><><><><><><><><><><><><><><><><>If you don't have the passion to help people, you have no passion |
|
|
|
|
text qualifier