I have a table with a column containing strings each of which has a number embedded in it...
COL
boa1
boa002
boa103
xkar1001
xkar2
ab11001
etc... from which I want to extract the highest numeric value from each occurrence of the string portion.
So for the 'boa' string I want to return 103, from 'xkar' I want to return 1001 and from 'ab' I want to extract 11001.
Could someone kindly show me how I might do this?
Thanks tonnes for any help, Roscoe
Hi ,
We are migrating SSIS packages from SQL Server 2014 to SQL Server 2016. I'm using SSISUpgrade.Exe to upgrade my packages.
I have two questions :
1) I see provider name as 'Provider=SQLNCLI11.1;Integrated Security=SSPI' which is same as for SQL Server 2014 . What is correct name for SQL Server 2016 provider name for SSIS and should this be updated in all packages in SSIS.
2) When I open a solution after upgrading the packages in folder using Visual studio 2015 , I see that project opens with name as it is still in 2014 version ( Ex ProjectA(SQL Server 2014) ) . how can I upgrade packages in such a way that when I open a solution file , I should be able to open and see all packages when project in 2016 version .
any help is appreciated.
In my machine two versions (2012 and 2014) of SQL servers installed. (SQL Server Integration Services 11.0 & SQL Server Integration Services 12.0)
I developed a package by using 'SQL Data Tool for SQL Server 2014', But I am trying to deployment it always using SQL Server Integration Services 11.0.
and I'm trying to connect integration service through SSMS by default it takes
SQL Server Integration Services 11.0.
Is it possible to use two integration services in same machine?
How can I use SQL Server Integration Services 12.0 instead ofSQL Server Integration Services 11.0.??
Srinivas Ch
I’m re-writing our SQL 2014 SSIS packages in SQL 2016. The main purpose of the re-write is to add additional error handling and intelligence to the packages. I’m looking for a little “best practice” guidance.
First I’ll give a brief explanation of our packages. They are written to process files we receive on our FTP site. We have a main “wrapper” (parent) package that does things like: copies the package to a working directory, unzip the file if necessary and then copies it to an archive directory. When the file is ready for processing, the parent package calls a sub-package (child) that does the cleansing/importing of the file, then calls a stored proc to do the final handling of the data.
I want to record errors as they occur, at whatever point they occur at, and gracefully exit the package. This means I need to write a record to a table, handled with an Exec SQL Task that calls a sproc, and then delete the file from the working directory, then send an email to people based on where the package failed. I’m wondering if the parent package should have one OnError event at the main package level or if it should have a separate OnError event for each step. I will do the same thing no matter where the error occurs – call the sproc to insert a record into the table. If the error occurs in the child package I also need to call the same sproc to insert a record into the table, but I also need the error to bubble up to the parent package so I know an error occurred. If an error occurs in the parent or the child, as the very last step(s) I need to delete the file I was processing, then call another sproc that is going to determine where the error occurred and whom to email. I’m not sure of the best way to accomplish all of this so I’m looking for suggestions.
I was thinking of having one OnError event at the parent package, and one at the child package. I can handle all the errors that way just fine, but I can’t handle the final cleanup/email step. I also don't know how to get the child package to tell the main package that an error has occurred.
Any help is appreciated. Thanks in advance.
André
Dear community,
in our company, we use an SSIS package to transfer data to our webhoster. Therefore, we created a SQL Job that runs every 5 minutes and reads a SSIS package from the local disk. We opted against installing the package on the sql server for maintainance reasons (we are administrated from mother company). Now I added an additional condition to the SQL Query and overwrote the dtsx file on the server. While executing the dtsx from within my VS 2015 at my work PC outputs the correct new result, the (overwritten) dtsx file which is read by the SQL Job still outputs the old result. Does our IT have to restart services in order to get the (overwritten) dtsx file with the updated query executed?
Thanks in advance!
Hi,
I am using OleDB source to access data from SQL Server and depending on column value, am segregating row in 3 different destinations. When the OLEDB source does not return any rows, the conditional split is throwing error and starting SQLDumper process.
Can you please suggest the solution of this issue.
Thanks
Dhiraj
Hi Guys,
I have a package that runs perfectly in development (visual studio). When I deploy the package to the server and execute it from SSISDB, it doesn't load any data. The package doesn't file, but does not find the files in the share folder.
When I create a job, everything works. I thought that running locally in visual studio is the same as exectuting from the SSISDB.
Any idea why this is happening? Great help!
Hi,
Every time I open an 2008 R2 package I get following message. Is there any way to get rid of it?
Thank you.
Remember to mark as an answer if this post has helped you.
In VB.Net from a script task I can post status info to the SSIS output window by calling Dts.Events.FireInformation. Is there a way to do the same from T-SQL in a SQL task?
Thanks,
Jnana
Jnana Sivananda
This is an infuriating problem. I have created a package which exports data to an excel destination and then uses a script task to email the extract out.
When executing the package in my local VS2012 it runs perfectly. I then deploy it to a local x64 OS/2014 SQL instance and execute it through the SSIS catalog and it runs perfectly, also fine when wrapped up in a job.
When testing this on a UAT (x64) server prior to deploying to production it failed with the above error. I realised the UAT server did not have office installed so I installed the ACE.OLEDB 12 64 bit driver. This then also worked perfectly.
Now when deploying to a production environment with the driver installed it fails with the same error. The production environment is a 64 bit OS...the package is running in 64bit runtime mode and the SQL instance is also 64 bit.
Just in case, I tried running the package through a job in 32 bit runtime mode and also tried uninstalling the 64 bit driver and installing the 32 bit version but to no avail.
What am I missing here?
Just curious what are all the best practices in industry for error handling which includes generating the exact version of source format . So that end user can correct and reload it.
Also what is the best practices of validating data in oracle db after data load? Right now I am doing the count ,distinct to find different column values and spot checking the data format. Is there any opensource tool available for data validation?
What should I expect the output as per ETL work? Right now gathering stats and generating excel for missing records.
Please share some guidance on this...
Thanks...
Hi,
We are planning to build SSIS packages that will sync tables from SQL 2016 DB to Azure DW. Only recently, we found out that MERGE is no longer applicable in Azure so our team is trying to figure out alternative ways to sync the data equivalent to MERGE without impacting the performance of the process. Kindly share your solutions and how we can implement these solutions.
Thanks in advance.
HI,
I don't know if any of you ran into this, but my SQL Server Agent has been running for the last 2 months without any issues. Since today, it stopped working.
When I try to run a SSIS package, it gives me a 'Acces to the path D:... is denied', and the job ends in failure.
When I try to run a Powershell script, it reports that the job was successful but it doesn't do the job.
Note that I can manually run those Powershell scripts, and I can manually run these packages without any problems.
Also, when I look in the Microsoft SQL Server Management Studio, the SQL Server Agent is running, I can see the green arrow on its icon.
Hi Team,
We are working on Integration project with JDE and legacy systems.
We are using SSIS for 2012 for the development.
We will explain the process that we are using for development:
The above process is working fine but intermittently we are getting issue related to date and time that we have created in SSIS.
For certain records, the date and time fields are not getting populated in flat file( even though the date and time fields are populated in SQL DB) . Rest of the fields are getting correctly placed in file. we are not getting any error from SSIS component. The date and time fields are trivial for further integration.
Please help us resolve the issue.
Thanks and Regards,
Mithila Joshi
Hello All,
I have created a SSIS package and deployed it as a project model in SSISDB Internal Catelogs and run from SQL server Agent Job. It runs for a while and then starts throwing the below error. And then restart of the SQL server makes it work again for few more
hours and again the same error appears.
I have raised the memory to fullest possible in SQL Server 2012. Its 32 bit SQL server instance. No matter increasing the memory or enabling the CLR it still runs for few hours after the SQL server restart. This cannot be a solution as there needs to be something
which has to be addressed for the Storage issue.
Please could you advice me on this?
Error : Failed to create AppDomain "SSISDB.dbo[runtime].3". Could not load file or assembly 'System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. Not enough storage is available to process
this command
Memory
Memory
Error Message
Thanks
Senthil
Hi,
Please find my below requirement and suggest me the best ideas. Before that,I am new to SSIS and Webservice integrations.
My two query is:
Please let me know if any other better suggestion other than SSIS.
Go Green.Save Earth.