Viewing 15 posts - 49,696 through 49,710 (of 59,099 total)
pduplessis (6/25/2008)
For the SSIS bit.
1) Create connectionmanager to your data
2) Create a preparation SQL task which basically deletes the data, as per the delete statement
3) Create a dataflow. OLEDB source...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 9:41 pm
Aw crud... Bill, some of the rows have some commas in the actual data which pretty much screws up "easy". Could you recreate the zip file using Tab delimited...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 8:38 pm
Good to see you too... and thanks for the book data in a format that I can actually load easily 😀
Do you have an example set of words that you'd...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 6:32 pm
How are the words being passed and do you have a wad of example book titles we can test with? See the link in my signature for the best...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 5:45 pm
Rashmi,
How often is the hierarchy going to change?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 5:41 pm
We have lots of embedded tabs
That would certainly be a fly in the ointment. Thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 5:30 pm
Then what in the application is giving you the offset of either 5 or 6 hours? Could it be that all the times are assumed to be GMT and...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 5:23 pm
Stephanie Giovannini (6/25/2008)
Jeff, I like your schema better. Thanks for clarifying how phone numbers and addresses are ideally stored.
Heh... not sure it's the "ideal" way to do it, but I...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 5:16 pm
Since Oracle 8.3, you also can use Case... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 5:08 pm
Good code... but be careful when you get a lot of rows or the groups of rows become large. Take a look at the following article...
http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 3:48 pm
R L Reid (6/25/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 3:36 pm
The best thing to do, in most cases, it to avoid any kind of function and any kind of correlated sub-query including Cross Apply. Yeah, I know... I'm going...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 3:29 pm
Very good article... you did a heck of a good job on it. 🙂
Just a couple of observations...
You did all of this just because BCP won't export column headers......
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 3:10 pm
Wow... lots of RBAR there 😀
For starters, you can replace the following WHILE loop...
declare @cnt int
declare @UnitCount int
set @cnt=1
set @UnitCount=1
while @cnt<len(@s_Table_PkgNumber)
begin
if(substring(@s_Table_PkgNumber,@cnt,1)=', ')
begin
set @UnitCount=@UnitCount+1
end
set @cnt=@cnt+1
End
... with this...
SET @UnitCount = LEN(@s_Table_PkgNumber)-LEN(REPLACE(@s_Table_PkgNumber,',',''))+1
That one...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 7:31 am
Darned forum... please replace the smiley faces in the code with right parenthesis...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2008 at 7:12 am
Viewing 15 posts - 49,696 through 49,710 (of 59,099 total)