The "Twitter Source" is used to extract data such as status updates (known as "Tweets",) followers, hashtags, and retweeted or favorited "tweets" within an SSIS package. See the Social OAuth Connection Manager page to learn more about setting up this component's connection manager.
Twitter is available for SQL versions 2012 and higher.
• Connection Manager - In this field, users can create a new connection manager or select a pre-existing one configured earlier.
• Api End Points - In this field, users select the Api they wish to connect to (such as User Timeline, Followers/List, etc.) Selecting an endpoint will auto-populate that field's parameters and commonly used Output Columns
• API Query - This field defines the query to be used in the API. Although several end points have been pre-configured, users can type in or paste custom calls that are not included with the component. These calls can be found by clicking the View Api Document link and copy & pasting the Resource URL located on the page of the selected API..
• Root Json Path - Because Twitter returns the raw data in Json format, users will need to define the root path when creating custom queries. This can (usually) be found in the View Api Document link.under "Example Result."
• # Seconds to wait between API round trips - For security reasons, Twitter places a 200 count limit per call at runtime and only 15 calls can be performed within 15 minutes. This limitation can cause a "too many requests" error when querying a large dataset such as a user's follower's which has 10,000 users. To avoid this error, users can set a timer that will pause between calls.
• Query Parameters - User-defined parameters (such as screenname or count number.) Parameters can be set dynamically by entering the variable name (example: <@User::ScreenName>.)
• Output Columns - In this window, users can add and remove columns and define their name, token path (defined within the raw data), data type, length, precision, scale, and code page.
• Preview Data - Pressing this button will return the results and raw data based on the user-defined settings.
• Results - In this window, users can see a preview of the first few rows of data based on their configuration.
• Raw Data - This window displays the Json data in raw form. Developers can use this to help determine a root and token path.