MS SQL SERVER DBA

Ticketing tool improves communications tracking whatever is happening in the environment, reporting that what has happened within the specific duration. A Ticket is an element contained within an issue tracking system which contains information about support interventions made by technical support staff or third parties on behalf of an end-user who has reported an incident that is preventing them from working with their computer as they would expect to be able to. Tickets are commonly created in a help desk or call center environment. Typically the ticket will have a unique reference number, also known as a case , issue or call log number which is used to allow the user or support staff to quickly locate, add to or communicate the status of the user's issue or request. The Tools used by various companies are: BMC Remedy 7.0 HP Service Desk Peregrine Open View CRM Wipro E-Desk Wipro Virtual Ticket Inbuilt Ticketing Tool

Hi, Self Introduction:                      I am Vang chew bigger , currently I am working with   Citronics , Here my role is SQL Server Database Administrator , I am having 3+ yrs Exp in SQL SERVER DBA with T-SQL, I have experience on SQL Server 2000, 2005 and 2008, I have a great experience on installation and configuration of SQL SERVER versions, and also applying the patches, hot fix, services packs and RTM’s accordingly, involved in upgrading on in place and side by side as per client requirement, and also Migrating the database on SQL SERVER 2000 to 2005 and 2008, Solid experience on configuring and maintenance of High availability SQL Server solutions, including Log shipping, Database Mirroring, Replication(Transactional and Merge) and SQL Server Clustering., having experience on performance tuning on server level, database level and query level, Responsible for working with application developers in identifying, resolving and proactively working to prevent performance or oth

Detailed planning is critical to the success of every SQL Server cluster installation. Fully plan the install before performing the actual install. An expensive cluster is of little value if the supporting infrastructure is not also fault tolerant. or example, don’t forget power redundancy, network redundancy, etc. Run only a single instance of SQL Server per node. Whether you have two or eight nodes in your cluster, leave one node as a failover node. Cluster nodes must not be domain controllers, and all nodes must belong in the same domain and should have access to two or more domain controllers. All cluster hardware must be on the Microsoft Windows Clustering Hardware Compatibility List, and certified to work together as part of a cluster. Since clustering is not designed to protect data (only SQL Server instances), the shared storage device used by the cluster must incorporate f

Introduction If your mission-critical SQL Server should experience a motherboard failure, how long will it be down? One hour, four hours, a day, or longer? How much will this cost your business in lost sales or productivity? And perhaps even more important to you, what will it do to your stress level? Being a SQL Server DBA can be demanding and stressful, especially as the success of your company is often a function of your SQL Server’s uptime. While we, as DBAs, have some control over the uptime of our SQL Servers, we don’t have full control. There is not much we can do if a motherboard fails on a server, other than be prepared. As you may already be aware, there is one way to help boost your SQL Server’s uptime, and that is by clustering SQL Servers. This way, should one SQL Server fail in the cluster, another clustered server will automatically take over, keeping downtime to minutes, instead of hours or more. The purpose of this article is to