as mentioned by mister.magoo, your server collation is different to database collation. tempdb uses server collation. have a look at the collation in db properties.

the problem here looks like that @data variable is not in the scope when you execute @Cmd. you need to declare @data like

declare @Cmd varchar(max);

set @cmd...

i dont remember exactly it was for 2005 or 2008, but if you are having scripting objects, you need to recompile the scripts on x64 machine if its developed on...

can you please post the error message as it is working fine for me. I am running it...

How about this:

SELECT j.name JobName,h.step_name StepName,

CONVERT(CHAR(10), CAST(STR(h.run_date,8, 0) AS dateTIME), 111) RunDate,

STUFF(STUFF(RIGHT('000000' + CAST ( h.run_time AS VARCHAR(6 ) ) ,6),5,0,':'),3,0,':') RunTime,

h.run_duration StepDuration,

case h.run_status when 0 then...

Akkare (10/27/2010)

---

Hi

I need help for the below

Have 2 node sql cluster.what is the procedure to apply service packs and other updates on sql.

Kindly explain detail.Also explain applying SPs for...

merlin2864 (10/26/2010)

---

I have 3 queries which basically the same but hitting different DBs. One of the query do not using parallism and it is take hours to load 15m...

why don't you script them out, drop it and recreate it with new names

Paul,

In the part1, you have mentioned about SELonJN operation, how it can be enabled?

It will be really handly if you'll also post the changes you made to the indexes or...

http://www.sql-server-performance.com/articles/dba/Data_Compression_in_SQL_Server_2008_p1.aspx%5B/quote%5D

Nice reference Ashish, good link for understanding

even i faced the same problem but mine OS was win 2008 r2. what i did was cancel the current installation process and restart it and it worked.

how about you script all the objects and run a script (powershell or vb or any other language) to change the schema. we used to change the servername and databasename...

even i think it shouldnt be a problem but if any message or alert comes that any file is being shared, don't remove it.

best will be to write your own script to get the subset of the data. you can populate the parent tables first and then keep on moving down the heirarchy...

i agree with Jerry, i have also experienced similar problems. The Ideal way is to uninstall and re-install the SQL Server