New answers tagged sql-server-2008
Make a list of all the databases you will need to move from the each server and their versions. Backup current databases. List what application/users will be impacted by this and what you will need to change at the application end.[connection strings info or others] On the new server make sure you have appropriate ports open, database server/ip information ...
That is correct. Windows 2008R2 Standard Edition does not support Failover cluster. The failover cluster doesn't even show up in the list of features. I just checked it. Only Ent and Datacenter supports it.
You may need to increase your Pagefile size, to be able to handle intermittent spikes in the memory commit size. We have this issue often in Azure compute where Pagefile is set WAY too low by default for memory-intensive apps. You can read more here: http://mvolo.com/low-pagefile-can-cause-503-service-unavailable-on-azure-web-roles/ This will not solve the ...
How big is this database? SQL Server likes to put the entire database in memory. It sounds, from your question, like it's a 200 MB MDF with a 250 GB LDF, or something horrifying like that. Recovery model doesn't enter into it unless they're grossly neglecting the database, which they clearly are. Set the database to simple recovery. Shrink the log ...
Yes, you would better to put TempDB log and data files in separate drives. as usual we are placing Data files for all DB|'s and log files of all DB's in separate drives as transactions writes in both the files at same time. so the same concept applicable for TempDB files also.
Top 50 recent answers are included