Thursday, February 24, 2011

Yahoo To Shut Down MyBlogLog On May 24

MyBlogLog will be closed from 24 May 2011. Yahoo also decided to close other bookmarking services like Delicious, Yahoo Buzz, AltaVista, Yahoo Picks and Yahoo Bookmarks. Yahoo bought the MyBlogLog in 2007 for $10 million to provide blogger with easy to create community for their readers.

mybloglog is closing 300x222 Why Yahoo Shutdown MyBlogLog, End of MyBlogLog
Social bookmarking web service Delicious will be next on Yahoo's agenda to be closed but Yahoo says that they are looking for buyers rather than shutting down the web sites. Well closing of MyBlogLog is bad news for those bloggers who have successful communities about their blogs on MyBlogLog.

Here's the message that was just emailed to all users:

Dear MyBlogLog Customer,

You have been identified as a customer of Yahoo! MyBlogLog. We will officially discontinue Yahoo! MyBlogLog effective May 24, 2011. Your agreement with Yahoo!, to the extent that it applies to the Yahoo! MyBlogLog, will terminate on May 24, 2011.

After May 24, 2011 your credit card will no longer be charged for premium services on MyBlogLog. We will refund you the unused portion of your subscription, if any. The refund will appear as a credit via the billing method we have on file for you. To make sure that your billing information is correct and up to date, visit https://billing.yahoo.com.

Questions?
If you have questions about these changes, please visit the Yahoo! MyBlogLog help pages.

We thank you for being a customer on Yahoo! MyBlogLog.

Sincerely,

The Yahoo! My BlogLog Team



--
********************************************************
Shahzad Afzal Malik see my blog:
http://shahzadafzal.blogspot.com/
********************************************************
Read More >>

Wednesday, February 23, 2011

Career Advice from Paris Hilton: That's Hot.

Career Advice from Paris Hilton: That's Hot.

We take a closer look at common quotes to find gems of advice for a successful contract work career.
Career Advice from Paris Hilton: That's Hot.
While an heiress is an atypical career advice guide, we've found that valuable insights to success can be found in even the most unlikely sources.
Like many indirect founts of inspiration, Paris' wisdom requires some interpretation. Fortunately, blogger Tamara Rice was up to the challenge, and has posted a series of Hilton's quotes, decoded as quality career advice. A sample:
PARIS SAYS: "Trust me, people act differently toward you when you've got jewelry on your head."
What It Means: Having "jewelry on your head" is, we're pretty certain, just a fancy socialite euphemism for "looking professional." If your online profile/portfolio picture makes you look professional, then potential employers will treat you like a professional.
PARIS SAYS: "You can see all these girls leaving a party at the end of the night and they look terrible … This is a huge mistake. People remember how you look when you leave as much as they remember how you look when you arrived."
What It Means: Paris is trying to tell you that "how you look" (i.e., your job performance and your professional behavior) at the end of a contract should be as important to you as how you looked when you were trying to land the job in the first place.
We know — when you've got a professional explaining it all to you, Paris' contractor guidance is so obvious it's, like, ridiculous. To see more 'Parisisms' merrily decoded, such as the enigmatic "The best thing about owning your own nightclub is that everything's free and you can tell the DJ to play whatever you want,"



Check out the full post at oDesk the full post.



----
Shahzad Afzal
http://shahzadafzal.blogspot.com/




Read More >>

Monday, February 14, 2011

Your friend invites you to join groupin

Welcome to Groupin

Dear Friend,

Shahzad Afzal invites you to groupin, an enjoyment platform that provides you with an opportunity to explore new products, places and events within your city on unbeatable prices you've ever imagined. Do you want to be the first to know about the best deals in your town? Do you want to win a free iphone? Then here is your chance. Don't wait, Join and gather as many friends as you can and be the winner of a brand new iphone. Just click the link below and get started Click the link below to login now:

http://www.groupin.pk/index.php?Action=groupinpk.home&ref_code=7bd8e&unqid=4d5a1f86e7aeb

Enjoy!



We respect your privacy! This message was sent to you by shahzadafzal85@hotmail.com via Groupin.pk. If you prefer not to receive email invitations from Groupin.pk, please click here.  Copyright © 2010-2011.
Read More >>

Your friend invites you to join groupin

Welcome to Groupin

Dear Friend,

Shahzad Afzal invites you to groupin, an enjoyment platform that provides you with an opportunity to explore new products, places and events within your city on unbeatable prices you've ever imagined. Do you want to be the first to know about the best deals in your town? Do you want to win a free iphone? Then here is your chance. Don't wait, Join and gather as many friends as you can and be the winner of a brand new iphone. Just click the link below and get started Click the link below to login now:

http://www.groupin.pk/index.php?Action=groupinpk.home&ref_code=7bd8e&unqid=4d5a0c8c5c77b

Enjoy!



We respect your privacy! This message was sent to you by shahzadafzal85@hotmail.com via Groupin.pk. If you prefer not to receive email invitations from Groupin.pk, please click here.  Copyright © 2010-2011.
Read More >>

Wednesday, February 9, 2011

How to use OUTPUT parameters with SSIS Execute SQL Task

How to use OUTPUT parameters with SSIS Execute SQL Task

Integration Services 2005 / SSIS (DTS) I was trying to get OUTPUT parameters to work with SSIS Execute SQL Task I encountered a lot of problems, which I'm sure other people have experienced. BOL Help is very light on this subject, so consider this the lost page in help.
The problem comes about because different providers expect parameters to be declared in different ways. OLEDB expects parameters to be marked in the SQL statement with ? (a question mark) and use ordinal positions (0, 1, 2...) as the Parameter name. ADO.Net expects you to use the parameter name in both the SQL statement and the Parameters page.
In order to use OUTPUT parameters to return values, you must follow these steps while configuring the Execute SQL Task:

For OLEDB Connection Types:

  1. You must select the OLEDB connection type.
  2. The IsQueryStoredProcedure option will be greyed out.
  3. Use the syntax EXEC ? = dbo.StoredProcedureName ? OUTPUT, ? OUTPUT, ? OUTPUT, ? OUTPUT The first ? will give the return code. You can use the syntax EXEC dbo.StoredProcedureName ? OUTPUT, ? OUTPUT, ? OUTPUT, ? OUTPUT to not capture the return code.
  4. Ensure a compatible data type is selected for each Parameter in the Parameters page.
  5. Set your parameters Direction to Output.
  6. Set the Parameter Name to the parameter marker's ordinal position. That is the first ? maps to Parameter Name 0. The second ? maps to Parameter Name 1, etc.

For ADO.Net Connection Types:

  1. You must select the ADO.Net connection type.
  2. You must set IsQueryStoredProcedure to True.
  3. Put only the stored procedure's name in SQLStatement.
  4. Ensure the data type for each parameter in Parameter Mappings matches the data type you declared the variable as in your SSIS package.
  5. Set your parameters Direction to Output.
  6. Set the Parameter Name to the same name as the parameter is declared in stored procedure.
For other connection types, check out the table on this page


Note: if you choose the ADO/ADO.Net connection type, parameters will not have datatypes like LONG, ULONG, etc. The datatypes will change to Int32, etc. Make sure that the datatype is EXACTLY the same type as the Variable in your package is defined. If you choose a different datatype (bigger/smaller/different type) you will get the error:
Error: 0xC001F009 at Customers: The type of the value being assigned to variable "User::Result_CustomerID" differs from the current variable type. Variables may not change type during execution. Variable types are strict, except for variables of type Object.
Error: 0xC002F210 at Add New Customer, Execute SQL Task: Executing the query "dbo.AddCustomer" failed with the following error: "The type of the value being assigned to variable "User::Result_CustomerID" differs from the current variable type. Variables may not change type during execution. Variable types are strict, except for variables of type Object.
". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
To fix this error make sure the datatype you select for each parameter in the Parameters page exactly matches the datatype for the variable. If you have attempted to use a connection type other than ADO.Net with named parameters you will recieve this error:
Error: 0xC002F210 at Add New customer, Execute SQL Task: Executing the query "exec dbo.AddCustomer" failed with the following error: "Value does not fall within the expected range.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Named parameters can only be used with the ADO.net connection type. Use ordinal position numbering in order to use OUTPUT parameters with the OLEDB connection type. Eg: 0, 1, 2, 3, etc.
OUTPUT parameters are extremely useful for returning small fragments of data from SQL Server, instead of having a recordset returned. You might use OUTPUT parameters when you want to load a value into a SSIS Package variable so that the value can be reused in many places. The data that is output might be used for configuring / controlling other Control Flow items, instead of being part of a data flow task.
If you were using output parameters in Management Studio, your SQL statement might look something like:
DECLARE @Name       nvarchar(125)
DECLARE @DOB        smalldatetime
DECLARE @CustomerID int
EXEC dbo.AddCustomer @CustomerName = @Name, @CustomerDOB = @DOB, @CustomerID = @CustomerID OUTPUT
PRINT @CustomerID
If you attempt to use the same syntax (highlighted above) with an Execute SQL Task you could end up with the error message:
Error: 0xC002F210 at Add New customer, Execute SQL Task: Executing the query "EXEC dbo.AddCustomer @CustomerName = @Name" failed with the following error: "Must declare the scalar variable "@Name".". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.


The only hint SQL Server 2005 Books Online gives is:
QueryIsStoredProcedure
Indicates whether the specified SQL statement to be run is a stored procedure. This property is read/write only if the task uses the ADO connection manager. Otherwise the property is read-only and its value is false.
(from SSIS Designer F1 Help > Task Properties UI Reference > Execute SQL Task Editor (General Page) ) There's a number of pages in Books Online that address Parameter use with the Execute SQL Task, but none adaquately address using output parameters. Articles which could do with updating:
  • How to: Map Query Parameters to Variables in an Execute SQL Task
  • Execute SQL Task Editor (Parameter Mapping Page)
  • Execute SQL Task Editor (General Page)
  • Execute SQL Task
  • Execute SQL Task (Integration Services)

Source:http://www.julian-kuiters.id.au/article.php/ssis-execute-sql-task-output-parameters
    Read More >>

    Popular Posts