Browse by Tags

• access
• analysis
• computing
• cpu
• disks
• dmv
• error
• Hardware
• Integration
• management
• memory
• named pipes
• remote
• replication
• security
• sql express
• ssas
• ssis
• ssrs
• tcp
• transactional
• tuning
• x64

• sys.dm_os_schedulers - useful to find on whether your SQL Server engine is weakening!

  The system DMV sys.dm_os_schedulers is an useful DMV to find such as running tasks & active workers threads etc. This is required to monitor the system state is heavily loaded or not, in particular this view will help you identify if there is any Read More... Posted Friday, August 17, 2007 11:04 PM from SSQA.net | (Comments Off) Filed under: SQL Server, performance, SSMS, memory, cpu, dmv, analysis, disks

• Dust out few tasks to gain transactional replication performance in SQL 2005

  Coming to the basics of Transactional Replication, that starts with a simple snapshot of publication database data. Similar to the name the process is carried upon the fashion of transactions and subsequent data changes and schema modifications made at Read More... Posted Thursday, August 16, 2007 7:20 PM from SSQA.net | (Comments Off) Filed under: SQL Server, performance, Hardware, Integration, SSMS, ssas, replication, transactional, tuning

• Whats with 64 bit computing on SQL Server

  What advantages we took when deployed the 64-bit computing within SQL Server As you aware 64 bit computing with 64-bit processors have become the standard for systems ranging from the most scalable servers to desktop PCs. The way to take full advantage Read More... Posted Sunday, August 05, 2007 12:41 AM from SSQA.net | (Comments Off) Filed under: security, SQL Server, performance, SSMS, x64, management, computing, ssis, ssrs, ssas

• An error has occured while establishing a connection to the server. When connecting to SQL Server 2005,this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.(provider:Named Pipes ....)

  Error: An error has occured while establishing a connection to the server. When connecting to SQL Server 2005,this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.(provider:Named Pipes Provider,error:40-Could Read More... Posted Thursday, July 26, 2007 10:49 PM from SSQA.net | (Comments Off) Filed under: security, SQL Server, performance, SSMS, tcp, sql express, error, access, named pipes, remote, management