DECLARE @username VARCHAR(30);
-- Set Twitter username
SET @username = 'rhyscampbell';
-- Execute the procedure
EXEC dbo.tweet_util_twitterCounter @username, null, null;

Here’s the raw xml that is accessible by using OUTPUT parameters.

<twittercounter>
  <user_id>297689</user_id>
  <user_name>rhyscampbell</user_name>
  <followers_current>255</followers_current>
  <date_updated>2009-06-06</date_updated>
  <url>http://www.youdidwhatwithtsql.com</url>
  <avatar>70800065/n571986135_2362730_9166_normal.jpg</avatar>
  <follow_days>253</follow_days>
  <started_followers>18</started_followers>
  <growth_since>237</growth_since>
  <average_growth>1</average_growth>
  <tomorrow>256</tomorrow>
  <next_month>285</next_month>
  <followers_yesterday>258</followers_yesterday>
  <rank>90877</rank>
  <followers_2w_ago>18</followers_2w_ago>
  <growth_since_2w>237</growth_since_2w>
  <average_growth_2w>17</average_growth_2w>
  <tomorrow_2w>272</tomorrow_2w>
  <next_month_2w>765</next_month_2w>
  <followersperdate>
    <date2009-05-11>227</date2009-05-11>
    <date2009-05-12>227</date2009-05-12>
    <date2009-05-15>230</date2009-05-15>
    <date2009-05-17>230</date2009-05-17>
    <date2009-05-20>232</date2009-05-20>
    <date2009-05-22>239</date2009-05-22>
    <date2009-05-24>241</date2009-05-24>
    <date2009-05-26>249</date2009-05-26>
    <date2009-05-29>248</date2009-05-29>
    <date2009-05-31>250</date2009-05-31>
    <date2009-06-02>248</date2009-06-02>
    <date2009-06-04>258</date2009-06-04>
    <date2009-06-06>255</date2009-06-06>
  </followersperdate>
</twittercounter>

Post from: youdidwhatwithtsql.com

Using TwitterCounter with Tweet-SQL

DECLARE @shrunk VARCHAR(140),
		@shaved INT;
 
EXEC dbo.tweet_util_tweetShrink 'For some strange reason I have developed a tendency to think every new version of Windows is more of a resource pig.', @shrunk OUTPUT, @shaved OUTPUT;
 
-- The shortened Tweet
SELECT @shrunk AS shrunkTweet;
-- How may characters have been shaved off?
SELECT @shaved AS shaved;

A future version of Tweet-SQL will include this functionality along with a few more cool surprises.

Post from: youdidwhatwithtsql.com

Shrinking Tweets with Tweet-SQL

EXEC dbo.tweet_src_search 'MC Frontalot', null, null;

Data from Twitter can be dealt with as an xml resultset, regular resultsets and with output parameters.

The procedure supports the full range of optional parameters offered by the api. Here’s a few examples;

lang – Restricts tweets to the given language, given by an ISO 639-1 code.

Search for Tweets containing ‘Paris’ in the French language only.

EXEC dbo.tweet_src_search 'Paris', 'lang=fr', null;

rpp – The number of tweets to return per page, up to a max of 100.

Search for Tweets mentioning “Swine Flu” and return up to 100 results.

EXEC dbo.tweet_src_search 'swine flu', 'rpp=100', null;

geocode  – Returns tweets by users located within a given radius of the given latitude/longitude, where the user’s location is taken.

Search for my favourite pub in Farringdon by users within 10 miles of EC1N 8FH.

DECLARE @geocode VARCHAR(100) = 'geocode=51.521935,-0.106859,10mi';
-- Need to url encode the geocode
SET @geocode = dbo.tweet_fnc_urlEncode(@geocode);
 
EXEC dbo.tweet_src_search 'Castle EC1', @geocode, null;

These, of course, can be chained together to procedure powerful Twitter searches. The example below will search for tweets containing ‘Fabric’, within 1 mile of EC1N 8FH, returning up to 100 results.

DECLARE @optional VARCHAR(100),
		@geocode VARCHAR(50) = 'geocode=51.521935,-0.106859,1mi';
-- Need to url encode the geocode
SET @geocode = dbo.tweet_fnc_urlEncode(@geocode);
-- Combine the rpp and geocode parameters in the optional variable
SET @optional = 'rpp=100&' + @geocode;
 
EXEC dbo.tweet_src_search 'Fabric', @optional, null;

Using Tweet-SQL you could;

• Archive Tweets containing certain terms and perform analytics.
• Monitor Twitter for mentions of certain terms.
• Auto-follow people mentioning specific subjects.

Detailed examples to follow soon.

Post from: youdidwhatwithtsql.com

Using the Twitter Search API with Tweet-SQL

• New procedure allowing the use of the Twitter Search API.
  ^?View Code T-SQL

  DECLARE @query NVARCHAR(100); SET @query = 'Tweet-SQL';   EXEC dbo.tweet_src_search @query, null, null;

• New procedures allowing profile modification.

EXEC dbo.tweet_acc_update_profile @name, 
				  @email, 
				  @profile_url,
				  @location, 
				  @description,
				  null;
EXEC tweet_acc_update_profile_colors @profile_background_color,
				     @profile_text_color,
				     @profile_link_color,
				     @profile_sidebar_fill,
				     @profile_sidebar_border_color,
				     null;

• Four new procedures implementing the new Social Graph API methods either returning data to the user or replicating the data to local tables.

-- Follower ids for the authenticating user
EXEC dbo.tweet_sog_followers null, null;
-- Same as above but copies data to a local table
EXEC dbo.tweet_sog_followersTable null;
-- Friend ids for the authenticating user
EXEC dbo.tweet_sog_friends null, null;
-- Same as above but copies data to a local table
EXEC dbo.tweet_sog_friendsTable;

• New procedure to shorten urls with TinyURL.

• New function tweet_fnc_httpformat allowing easier work with datetime values.

There’s even more to come in version 2 that will compliment the existing features of Tweet-SQL. There’s a feature freeze in place at the moment but what would you like to see in future versions of Tweet-SQL?

Post from: youdidwhatwithtsql.com

Tweet-SQL Version 2 Sneak Peek