Original database must have contained unallocated space. Even though the data is only 2GB it will try to create the data and log file with original size specifications.

You must have a regular log backup in place that truncate inactive portions of the log.

You can use DBCC sqlperf('logspace') to find percent used for the log file

R u running trace? .

Then stop it

Select * from fn_trace_getinfo(null)

what is the lastwaitype in sysprocesses also take a not of hostname and program which is executing this query.

Database...

You are not backing up. The above command truncate the log file without backing up.

Just find out what query is running and what resource it is waiting for. Its OK for a process to go suspended unless it does not wait for too long

You can use striped backup but its is sometimes risky

Backup database database name to disk='C:\backupfile_1.bak',disk='D:\backupfile_2.bak','E:\backupfile_3.bak

You need all these files for proper restore. Any corruption in single file can make the...

http://www.sqlservercentral.com/articles/T-SQL/61979/

It might not be that easy but you can compare the features and create a template based on that. Few key concepts are resources supported, features available and budget.

If you have no issues with First node, (ie is ur first server is now acting as single node cluster), you are safe.

Did you read this link?

http://msdn.microsoft.com/en-us/library/ms191545(SQL.90).aspx

Not clear enough. Can you please tell what you are trying to achieve?

Are you trying to create a single node cluster?

If you put database in single user, and took the tail log backup, you might want to use the same window to execute further statements.

However you can use sysprocesses...

Use dm_db_index_usage_stats view to get some idea regarding this. Note: this view is flushed on each restart