select cast(” as xml).value(‘xs:hexBinary(sql:column(“hexbin”) )’, ‘varchar(max)’) from
(
select 0×5400650073007400 as hexbin
) as t;

SELECT item_description FROM items
WHERE item_description Like ‘[c]%’;

For fifth example, it would be

SELECT item_description FROM items
WHERE item_description LIKE ‘[cp]%’;

You wrote: “There are few valid cases of the Shrinking database as well, but that is not covered in this blog post. We will cover that area some other time in future. ”

I’ve recently dropped an enormous log table from a database, and since the database is not meant to be that big again, within a foreseeable future, the obvious thing to do would be to shrink it.

Please write an article about shrinking databases in a correct and controlled manner. There are enough of the ranting “do not shrink”, that some people devote themselves to.

I have worked at two companies at least that take production versions of their database and restore it on a Dev server, having an older version of SQL Server than production because they purchased the production server after the release of the new version and did not have the media to install the older version on production.

The reason for restoring back on a dev box is to capture real time user interactions with the database. Both companies had a scrub process. This made debugging production database issues much easier as well.

Man you are the man! this part solved my doubt! thanks!
I had two records on each table and it was bring me 4 as result.
lacks more one key on inner join condition. thanks.