My first guess would be with all the implicit conversions it has to do converting the strings '10/1/2012' and '11-30-2012' to datetime.

Can you upload the execution plans in a SQLPLAN...

DECLARE @Expiry_Date DATETIME = '2012-12-25 00:00:01.003', @Prod VARCHAR(MAX), @Product_Name VARCHAR(10) = 'Vehicles'

SET @Prod=@Product_name + RTRIM(@Product_name)

+ ' (Expires '+RTRIM(DATENAME(MM, @Expiry_Date ) + RIGHT(CONVERT(VARCHAR(12), @Expiry_Date ,107),9))+ ')'

SELECT @Prod

Output is

VehiclesVehicles (Expires December 25,...

DECLARE @Expiry_Date DATETIME = '2012-12-25 00:00:01.003'

SELECT '(Expires '+RTRIM(DATENAME(MM, @Expiry_Date ) + RIGHT(CONVERT(VARCHAR(12), @Expiry_Date ,107),9))+ ')'

Gives me an output of

(Expires December 25, 2012)

Why do you want to copy them?

What is the reasoning behind your task?

Well something is wrong as I run it I get the , in the output between the date and year which is what the convert 107 does.

What is the data...

then do what you where doing in the first place, this is how it outputs

SELECT '(Expires '+RTRIM(DATENAME(MM, GETDATE() ) + RIGHT(CONVERT(VARCHAR(12), GETDATE() ,107),9))+ ')'

(Expires December 19, 2012)

Please post code, data and expected outcome as per the second link in my signature.

Sample data would be good as well

Using the following sample data

insert into Indexing values (199),(200),(210),(220),(230),(240),(250),(251)

insert into Indexing2 (Col4) values (199),(200),(210),(220),(230),(240),(250),(251)

I get no duplicates and now stream aggregate, the only difference...

Configure it by changing Group Policy, ask your AD guys to put all your SQL servers into an OU then assign a GPO to that OU so that accounts can...

Backup all databases, script out all server wide objects, uninstall, reinstall, run all server with objects back in, restore all databases bar master

Or

Install a standard named instance, transfer everything to...

I would direct you here, someone is asking the same question

http://www.sqlservercentral.com/Forums/Topic1398222-391-1.aspx

Its all down to the XML name space in the well formed XML

The XML name space in the XML is <ShowPlanXML xmlns="http://schemas.microsoft.com/sqlserver/2004/07/showplan".....> so it knows that its a query plan and then opens it in the correct format

No offence but have you done a search on the topic?

First link I got after google'ing "install sql server 2008 on veritas cluster" seems to detail all the steps nessesary.

Always remember the clue is usually in the error message.

Translated to English

e can issue a certificate which will match the requirements of SQL SERVER 2012

The certificate must be in the local computer certificate store or the current user.

Current system...