alan.fisher (5/31/2011)

---

Hi I have one SQL Server with about a dozen relatively small databases. I had the data and backup folders all on the same drive (C:\MSSQL10.MSSQLSERVER\MSSQL\Data &...

Hi

both 64k and 256k are optimal stripe sizes for SQL Server. The theory behind the 256K stripe size is that a larger stripe size generally incurs less I\O with 64k...

have you run DBCC checkdb against your system databases

at a wild guess i would say the original disk locations do not exist on the new server.

Does the new server have the same drive letters and paths?

If not you...

again, I'll reiterate, as long as the model database is available

do you mean orphaned database user?

for Tempdb you don't need to do anything. Tempdb is recreated each time SQL Server starts. It does however rely on the model database being available.

If you remove the...

I would run a server side trace to look for any rogue queries\procedures and monitor file growths, that would be a good starting point

just out of interest how large is the database you are moving?

well i have never bothered myself but if you query the parameter

SERVERPROPERTY('ComputerNamePhysicalNetBIOS')

this returns the actual node name the instance is active on.

Apply some logic and check this for both...

that is unfortunately a downside of clusters, wasted RAM and possibly even CPU. If you catch the system upon failover and trim the memory back then fine, what happens if...

raguyazhin (5/30/2011)

---

Hi

we migrated our SQL Server Database SQL Server 2000 EE to SQL Server 2005 SP4 EE 64 bit in our Concern.But still our user databases Compatibility Level is 80...

That's the whole point with clustering. Nodes are...

In that case I would drop and recreate the log shipping scenario.

Regional settings???