I found an interesting article by Kalen Delaney aka SQL Goddess (as I call) about a topic stating ' why do people bash Microsoft? ' The article was printed in SQL Server Magazine: Last week, I read a post from one of my colleagues, which shared a coworker’s opinion that SQL Server isn't a...
We have been struggling to uninstall the Cumulative Update package 7 on a development SQL Server! As it is an important aspect of installation to rollback or to have a backout plan tested if you are performing any kind of installation against your Production Server, not to mention its a best practice...
Secured by default, secured by design is the buzzword and catchy stuff for any Enterprise IT administrators. Then it comes about standards and policies to follow such as ISO , with the recent threats (last 10 years) and vulnerabilities within IT world it is most important factor you need to follow as...
IN continuation to the post Rollback_of_CumulativeUpdate-hotfix-ServicePack I was asked about any procedure or steps on installing Cumulative update package 7 for SQL Server 2005 Service Pack 2 on Active node SQL 2005 cluster. The simple answer is all of such hotfix/Service Pack/Cumulative Update packages...
The main difference betwen 32 bit and 64 bit server is Memory, you may be aware about 'Lock Page in memory' privilege to be granted to the SQL Server service accout within 32 bit based servers. This is a operating system based privilege that is required by SQL Server service account to allow...
To cut the long story short, during a recent implementation of Cumulative Update 6 and 7 on a particular 'application domain' server we have had major application issues due to a mix up of application code & these SQL cumulative update fixes. Actually this server was not under our support...
Windows Server 2008 is on full fledged wave now after it has been launched in February and it is obvious that many questions will be flying around about supportability & manageability for existing SQL Server versions such as 2005 at the moment. Think about managing the SQL Server 2005 Failover Clustering...
Whenever a performance issue occurs on the SQL Server database best option for diagnosing and troubleshooting common problems by using publicly available tools such as Profiler, System Monitor (Perfmon), and Dynamic Management Views (DMVs) in SQL Server 2005 (onwards). What to detect? Use SYSMON to detect...
Choosing a better plan to reduce outage to your database application is a beginner to provide High Availability to your application, irrespective to database or server. You may be aware that SQL Server 2005 version provides the database mirroring which is an advantage to avoid the costs and pre-requisite...
When you think about high availability in SQL Server then you would think about Clustering and in addition to this within 2005 version we have Database Mirroring too that can provide automated failover support to your database server applications. By default you can see a failover cluster as a combination...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
05-08-2008
Filed under: sql server, performance, high availability, best practices, cluster, support, database mirroring, instances, multiple, failover, scalability