The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
SQL Serevr Integration Services
Posted: 20 Mar 07 11:06 PM
|
fiogf49gjkf0d Lets start a good thread. I want to know why there are so many 3rd party vendors selling Import tool COntact Process tools etc. Cant integration Services do all that and I can avoid all the added expense and use a tool that will build my resume skills. All responses willbe appreciated.
Please send private emails they are appreciated. Im in a quest for the right way to do this with limited tools. |
|
|
|
Re: SQL Serevr Integration Services
Posted: 21 Mar 07 1:36 AM
|
fiogf49gjkf0d I've never understoof why so many companies will spend a ton of money on tools that do the same thing as tools they already own!
Absolutely SSIS (or even DTS - not to mention SQLNS as well) can do all of that. It can handle any scenario that you throw at it and a whole lot more than the 3rd party tools available. Not only that, you'll sure find a lot more resources on SSIS/DTS than you would on the 3rd party tools out there. The real benefit that some of the 3rd party tools will provide is to provide a simplified way to get a certain job done that is specific to the application you're integrating with. SSIS/DTS is a tool where you start from the ground up, nothing specific about the application you're building a job for, just a generic development playground. This can be intimidating to some and the simplified, application specific tools can make a job easier, but there is a cost with simplification - and that is a loss in flexibility.
Personally I'd rather go the route of using industry standard tools, that I can use with *any* app, than to use one that is application specific in any way. Those are skills that will apply *anywhere*. Not only that but the tools and what is available to work with is so much more complete.
But then again, I've always been a fan of SSIS/DTS. I find the non-proprietary approach so much more simple than learning some other 3rd party tool - not only that, but these are things I already own, no need to shell out more money for a tool that has similar, but limited capabilities in comparison.
-Ryan
BTW, why not keep the discussion here instead of private e-mails so we can all be a part of it  |
|
|
|
Re: SQL Serevr Integration Services
Posted: 21 Mar 07 7:01 AM
|
fiogf49gjkf0d Thanks for the reply.
You are saying that SSIS can do what Scribe does and more? If so I can pictue in my head how to import all my legacy data using SSIS. The one part I dont know of is how do I get a driver to make the SLXId's for SQL 2005 and can the driver make the SLXIds and know what tables to hit..
You are also saying SSIS can do the Contact Process instead of knowledge Sync. I can picture all the queries and concepts in my head. I just dont see how I can initiate events to happen unless I some how program buttons in SLX or timed events in SSIS. Are there any books or resources I can read on this topic for pointers.
Thanks
kevin |
|
|
|
Re: SQL Serevr Integration Services
Posted: 21 Mar 07 8:32 AM
|
fiogf49gjkf0d Originally posted by K Mill
Thanks for the reply.
You are saying that SSIS can do what Scribe does and more? ....
kevin |
|
To make a point about Scribe:
At one time, Scribe was the only game in town that really did it all. Now that has all changed.
Scribe is quickly becomming the NON-choice in the SalesLogix world due to several factors.. one being the extremely expensive licensing system they use. Not only do they count regular Slx Licenses.. but the actually include retired users! So you can have a 50 License Slx system w/200 retired users.. you then need a 250 user Scribe license.
Scribe is focusing on the MSCRM's of the world and not SalesLogix.
Inaport is focusing on the Sage SalesLogix world..
.. and then there are tools like SSIS (and it's earlier cousin DTS)...
..mix in custom import programs and integration tools like Dynalink..
If you focus on one tool you will end up in a corner since you have no control over the vendor (of the tool).
--
rjl |
|
|
|
Re: SQL Serevr Integration Services
Posted: 21 Mar 07 8:36 AM
|
fiogf49gjkf0d
Im confused are you saying use one product SSIS to do all that I need or do not use SSIS because I have no control over the Vendor.
As a side Note: I recently used reporting Services for all my reports no need for Crystal IReports etc.... Plus I have all the free lisceneses I want with reporting Services. |
|
|
|
Re: SQL Serevr Integration Services
Posted: 21 Mar 07 8:43 AM
|
fiogf49gjkf0d There IS no one product/program that solves it all..
SSIS is just one approach that some folks use.
--
rjl |
|
|
|
Re: SQL Serevr Integration Services
Posted: 21 Mar 07 10:18 AM
|
fiogf49gjkf0d
Seems odd that is all. All Saleslogix is to me is a viscous circle of 3rd party gimmicks that you need to learn and program. So inefficient!!!!!! |
|
|
|
Re: SQL Serevr Integration Services
Posted: 21 Mar 07 10:34 AM
|
fiogf49gjkf0d Hi Kevin,
Yes, SSIS can do what Scribe does and more. Personally, I think anyone who doesn't use it for imports is just plain crazy  but that's just me. As far as creating the SLX table ID values, it got really easy with the addition of the AUTOINCREMENT key feature added in the SLX provider. You just omit the ID value and the SLX provider creates on for you.
As far as using SQL as a replacement for KnowledgeSync, you'll want to look into SQLNS (SQL Notification Services). I'll use a combination of SQLNS and SSIS as well to make things really complete. If you google for SQLNS you'll find several good introduction articles to get you started.
To complete the picture SQL Reporting Services is just awesome. You can easily create reports that users can subscribe to and get e-mailed automatically when certain data changes (or on a predefined schedule). Really powerful stuff and SO easy to use and build.
These are all tools that people already own, that are such great and powerful tools, yet so many still insist on shelling out more money for lesser tools (IMO). |
|
|
|
Re: SQL Serevr Integration Services
Posted: 21 Mar 07 10:39 AM
|
fiogf49gjkf0d Originally posted by K Mill
Seems odd that is all. All Saleslogix is to me is a viscous circle of 3rd party gimmicks that you need to learn and program. So inefficient!!!!!! |
|
Not the case at all. I've used only industry standard tools for working with SLX for years (SSIS/DTS, SSRS, SQLNS, etc). It all works great. However, there are tools out there that are specific for SLX that many like using because it does simplify some work as it is written specific for SLX, but I'd rather stick with the tools I already own, have endless resources for help (books, websites, etc), and are using skills I can continue using outside of the SLX world as well
-Ryan |
|
|
|
Re: SQL Serevr Integration Services
Posted: 21 Mar 07 5:44 PM
|
fiogf49gjkf0d Just to add my slant on this.
If you are a SalesLogix novice, or you do not understand the structure of the SLX database intimately (that is, how the main tables link together and what the various fields mean). you will find it very difficult to start with a blank SSIS project and build an import routine. The integrity of the SLX database (apart from primary keys) is not enforced at the database level - so if you are going DIY rather than using tried-and-tested tools, you need to know how to maintain integrity and do it through the code that you write.
But once you get going, I agree that these tools are the way to go. You're in a programming environment and not bound by third-party application limitations. It's just that there are people out there that need to do imports and don't have the time or inclination to learn how to code using DTS/SSIS - there is a steep learning curve if you're not a developer.
P |
|
|
|
Re: SQL Serevr Integration Services
Posted: 22 Mar 07 8:27 AM
|
fiogf49gjkf0d Originally posted by Phil Parkin
Just to add my slant on this.
If you are a SalesLogix novice, or you do not understand the structure of the SLX database intimately (that is, how the main tables link together and what the various fields mean). you will find it very difficult to start with a blank SSIS project and build an import routine. The integrity of the SLX database (apart from primary keys) is not enforced at the database level - so if you are going DIY rather than using tried-and-tested tools, you need to know how to maintain integrity and do it through the code that you write.
But once you get going, I agree that these tools are the way to go. You're in a programming environment and not bound by third-party application limitations. It's just that there are people out there that need to do imports and don't have the time or inclination to learn how to code using DTS/SSIS - there is a steep learning curve if you're not a developer.
P |
|
Phil,
You hit it on the head directly....
The major mistake that new users/developers/ect.. make about SalesLogix is that it's a DB application and that the app is using all the "features" of the db engine.
SalesLogix is (basically) Database Engine Agnostic and relies on itself to maintain referential integrity. It holds it's "business rules" within itself. It will (AFAIK) always remain that way.
SalesLogix is NOT unique when it comes to 3rd party tools (and the businesses built around them).
If someone wants to advance their career in the DB world as a db person, SalesLogix is not necessarily the place to be.
If you want to advance your career in the "relationship management" space, SalesLogix is a GREAT place to be!
--
rjl |
|
|
|
Re: SQL Serevr Integration Services
Posted: 03 Sep 08 4:27 PM
|
| When using SSIS to bring data into SalesLogix from outside sources, does the imported data automatically get logged for synchronization if the SSIS connections are made through the SalesLogix OLE DB Provider? |
|
|
|
Re: SQL Server Integration Services
Posted: 03 Sep 08 6:55 PM
|
The answer is a qualified yes.
You need to write your INSERTS and UPDATES in such a way that there is no reliance on the external data. So this method works:
1) Read external data into a DataReader
2) Loop round DataReader and perform RBAR inserts/updates - one record at a time with explicit (literal) values
This method does not work:
UPDATE [SLX table]
SET field1 = ExternalData.Field1, field2 = ExternalData.field2 etc etc
This method does not work because the UPDATE instruction syncs to the remotes and then fails to execute - because the external data is not present on the remote machines.
Phil
|
|
|
|