Yeah, that why I tell them changes made to SP can only be those that are cost effective. I basically show them that the time and cost is not worth an extra bell or whistle. Luckily I'm persuasive enough to keep SP in its place as I do with Crystal, Business Objects and CF reports. Each one has its pros and cons, so the best choice for the job will require some analysis. While I wish we lived in a world where we could do everything simply in one super ERP monstrosity, I know that my wish is as impossible as living in a utopian society.
________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Aaron Rouse Sent: Friday, December 19, 2008 10:23 AM To: [email protected] Subject: [houcfug] Re: SSIS The problem here is the group manager for awhile, has not said it in a long time, was pushing towards everything being done in SP so the complex stuff as well. Many in the company still lean that way and it is making some of the few SP gurus out there quite rich. They even have ran into issues where simple stuff was done in SP and then after 6 months or so the project sponsor would want something added. They might want something simple added but it would be completely out of the box in regards to what you could do with SP and therefore have a huge price tag due to the effort to get done. Pretty sad when a simple change could cost far more than just redoing the entire thing in something else outside of SP. On Fri, Dec 19, 2008 at 10:17 AM, Kier Simmons <[email protected]<mailto:[email protected]>> wrote: I agree with your sentiment as SP nearly drove me off a cliff. The amount of stress it caused me was ridiculous, but I can get most of it to behave now. A lot of what it does would take me a good deal longer to do in CF. So all the one list simple things that come down the pipe, I develop in SP now, but I still do all the complex apps and systems in CF. ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Aaron Rouse Sent: Friday, December 19, 2008 9:42 AM To: [email protected]<mailto:[email protected]> Subject: [houcfug] Re: SSIS More power to you, I avoid SharePoint like it is the plague, I think I'd enjoy Chinese water torture over dealing with that product ever again. On Fri, Dec 19, 2008 at 9:27 AM, Kier Simmons <[email protected]<mailto:[email protected]>> wrote: Heh, we are using it here, and I've had enough time to beat it into submission. Granted I am using a 3rd party workflow dev tool called Nintex Workflow, but at least I can get ColdFusion to interact with it. Getting the SP web services to work was a bust despite the people that have figured it out some how, but I did manage to get Nintex to communicate with CF second had via XML and the web client file structure. CF is so versatile that you can always find a way around road blocks to get it to integrate with anything. I was also able to get scheduled jobs performed by our UNIX servers, Business Objects XI servers, SQL 2000 servers, SQL 2005 servers, Oracle Database, and ColdFusion servers to communicate with one ColdFusion server in order to log the start, completion and failure of each job. Plus I was able to do all the fun things that good old CF programming can provided such as warning the person that developed the job that it has failed to begin, end or just issued a failure in general. Plus escalation to the whole development group if the message is not acknowledged was easy enough. Try getting that to work in SP without losing your mind. ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Aaron Rouse Sent: Friday, December 19, 2008 9:12 AM To: [email protected]<mailto:[email protected]> Subject: [houcfug] Re: SSIS Getting SharePoint to play nice without involving ColdFusion can often times be a challenge in itself, but guess it depends on what you are doing since SharePoint seems to work "ok" if strictly using out of the box functionality. The WFF(?) that SharePoint uses for workflows is not the best thing since sliced bread though. Every SharePoint project I know of here is using third party workflow tools due to the one built in just not being up to the job. Just remember that friends do not let friends use SharePoint. On Fri, Dec 19, 2008 at 9:02 AM, Kier Simmons <[email protected]<mailto:[email protected]>> wrote: Of course if we are going to talk workflows the conversation will inevitably turn to SharePoint and ways we've all tried to get ColdFusion to play nice with it. -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Robert L. Stewart Sent: Friday, December 19, 2008 7:26 AM To: [email protected]<mailto:[email protected]> Subject: [houcfug] SSIS Ken, A lot of what had to be done in VB can now be done natively in SSIS. It is really designed as a tool for migrating data from a transactional system to a data warehouse. There is also a really good work flow capability which was very basic in DTS. Because of work flow, it is sometimes easier to do SPs than DTS. At 02:28 AM 12/19/2008, you wrote: >Date: Thurs, Dec 18 2008 7:38 am >From: "Ken Auenson, II" > > >So, I have not yet been exposed to SISS in SQL Server 2005, but I am >maintaining a few DBs that are SQL Server 2000 that had a lot of DTS >packages. >At one point, I re-wrote most of them to be straight stored procedures. >I find this to be a lot easier to maintain and a lot easier to actual work >with. >What tasks and added power to DTS and/or SISS have that you cannot do in >straight stored procedures? >In other words, what features/benifits am I missing out on? > >Thanks, >Ken Robert Stewart ProjecTools.com 713-371-9840 X1305 -- Aaron Rouse http://www.happyhacker.com/ ________________________________ This e-mail message and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination, or copying of this message and its attachments or the information contained herein is prohibited. If you have received this message in error, please notify the sender by return e-mail and delete this e-mail message from your computer. Thank you. -- Aaron Rouse http://www.happyhacker.com/ ________________________________ This e-mail message and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination, or copying of this message and its attachments or the information contained herein is prohibited. If you have received this message in error, please notify the sender by return e-mail and delete this e-mail message from your computer. Thank you. <br --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Houston ColdFusion Users' Group" discussion list. To unsubscribe, send email to [email protected] For more options, visit http://groups.google.com/group/houcfug?hl=en -~----------~----~----~----~------~----~------~--~---
