Database does not have any edition,Database have compatibility option in the advanced option of database

like 80 for 2000 , 90 for 2005 ,10 for 2008

Install Service Pack 1 for the SQL Server 2008 R2 and CU # 7 is available also

Select st.text,sp.* from sys.sysprocesses sp

cross apply sys.dm_exec_Sql_text(sp.sql_handle) st

order by sp.cpu desc

this query provide...

Depending (there is that word again) on the volume of data changes a setup involving transactional replication can utilize infinitely more network and system resources than periodically running a well-crafted...

Execute your query and then execute this query on another server

Select st.text,sp.* from sys.sysprocesses sp

cross apply sys.dm_exec_sql_text(sp.sql_handle) st

order by sp.cpu desc

it will tell you bottleneck

mostly only CPU usage depend on...

Start cmd as [RUN as Administrator] then execute it

1-Install the latest service pack for the SQL Server 2005

2-Is your network break after some interval ?

3-Have you define catalog in the connection String ?

select * from sys.dm_os_performance_counters

where counter_name = 'Page life expectancy'

provide value of this counter,RAM allocation is depend on the load of the server,this counter will tell you SQL Server required RAM...

For Logshipping Issue

http://aureus-salah.com/2011/05/10/sql-server-logshipping-issue/

Its better to install 1 by 1

Use Audits and Database Audit Specification

http://msdn.microsoft.com/en-us/library/cc280472.aspx

http://technet.microsoft.com/en-us/library/cc280404.aspx

And you can use EVENT_DATA also

http://technet.microsoft.com/en-us/library/ms173781.aspx

http://msdn.microsoft.com/en-us/library/ms187909.aspx

http://www.microsoft.com/sqlserver/en/us/product-info/competitor-compare.aspx

Transaction Processing Performance Council

http://www.tpc.org/

http://www.tometasoftware.com/MySQL-5-vs-Microsoft-SQL-Server-2005.asp

http://www.postgresonline.com/journal/archives/51-Cross-Compare-of-SQL-Server,-MySQL,-and-PostgreSQL.html

Migration Help

http://www.microsoft.com/sqlserver/en/us/product-info/migration-tool.aspx#MySQL

you need any 1 of them SERVER IP or is there DNS in your organization then SERVER NAME can use also

IP is best

can create SSIS as well and whole code can be in a single agent job

schedule a job with email on another SQL Server

exec xp_cmdshell 'ping serverip\servername'

if you not get the ping then email to you otherwise not,I might be schedule on OS level also...

Diskpart might be help

http://support.microsoft.com/kb/325590