The log will contain all the changes made since the last log backup and if there are large amounts of work being done in the database it is possible to...

With clustering the servers are physically located near each other in order to share the disks. It will protect against failure of one of the nodes in the cluster...

Sounds like the vendor has a modelling tool with a default size of varchar(255). Having the right size can save on storage but also helps prevent 'incorrect' data being...

I'd stay away from doing method 1 (NTFS compression)if you can as it does slow down SQL Server backup and recovery and also the offline backup to tape.

It's good to...

Never tried it but you can use profiler to capture the queries and then replay them (tsql_replay template), this would give an indication of how the migrated system works with...

Standard Edition can have up to 16 instances per computer, Enterprise Edition can have up to 50.

The answer is yes. On the cluster you will only have the choice of putting the databases on the clustered drives, SQL Server won't see any other disks

I guess that is a Windows cluster. If so, yes you can install SQL 2000 or 2005 on it. For 2000 you will need Enterprise Edition, for 2005...

You can see if the databases are in step by using the db mirroring monitor tool or system views The only real way of testing if the mirror works...

In 2005 you set the port in SQL Server Configuration Manager - select Network Configuraton and change the port in the properties under the TCP/IP protocol. For 2000 you...

You'll find all the Oracle documentation at http://www.oracle.com/technology/documentation/database.html including some quick start guides.

I'd try to size the database appropriately to start off with and avoid autogrow. Use autogrow as a way of allowing the database to grow in an emergency rather...

Going forward you can use profiler to capture the time when the growth happens but I'm not sure if there are any views you can use to see when it...

1) you'll have to read up on this but basically you ensure the latest logs are copied from the primary to failover, restore the logs, stop all log shipping...

Hope you find out the root cause and don't have to start swapping out servers! We don't have hundreds of clusters but 20 or so and only one node...