Can you post requirement ?

Are the primary servers and secondary servers are in same domain ?

Does the nw response between the server < 10ms without packet loss ?

Purpose of...

Please ignore my last post , it works fine.

ALTER DATABASE TESTV

COLLATE SQL_Latin1_General_CP1256_CI_AS

USE TESTV

select * from table1

Though table1 is in uppercase during creation

worked fine for me.

If this specific to one target server only, try the steps below

- Try creating dummy plan and check if you are getting the same error message.

- Also check if the...

Though at the database level your collation is Case Insensitive , if the instance level default collation is Latin1_General_CS_AI which makes all the objects in database case sensitive.

This is the...

Hi Duran,

Though the article does not mention about running it on SQL ANALYZER it is supported and could run it there.

If you want to add it to job menu in...

Was in similar situation before , one related topic on this below

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=117803

- Check the disk space where the .mdf .ndf or ldf files are located.

- If the disk space is full due .ldf

detach the database and add new disk

...

Also refer to this post in forum

http://www.sqlservercentral.com/Forums/Topic474364-146-1.aspx

-Sat

This article states the DBCC commands are aware of partitions and can be applied on partitions but does not say how to do it

http://hi.baidu.com/peacescott/blog/item/73e4b634c610243d5ab5f505.html

Please run the appropriate command from query analyser that should do it.

EXECUTE master.dbo.xp_sqlmaint N'-S ServerName\InstanceName -PlanID -WriteHistory -CkDB -SupportComputedColumn'

-Sat

Yes , client connection increase, maintainence jobs run and data grows you would see increase in memory usage.

It is normal since you have just started it.