Adding password complexity and password expiration to SQL Server logins is one of best feature I quote for SQL Server version 2005 onwards, similarly such password complexity policies are designed to deter brute force attacks by increasing the number of possible passwords. When password complexity policy...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
04-30-2008
Filed under: sql server, microsoft, security, feature, password, best practice, trustworthy, computing, logins, policies, settings, check_policy, check_expiration
Do you want to lockdown your SQL Server environment? Hope you dont'! Though it is not a good practice or recommendation to perform, but will atleast prove how far your SQL Server environment has securit compliance as per the industry best practices. Before we go to know how you can lockdown or know...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
02-13-2008
Filed under: sql server, microsoft, security, tools, article, sa, procedure, best practice, downloads, bpa, lock down
How do you define the terms "Performance Monitoring"? What is your baseline & benchmarks? Have you ever used PERFMON (SYSMON) & PROFILER for serious performance issues within your SQL Server environment? The answer may be not 'yes' for all the questions above, in general getting...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
12-19-2007
Filed under: dashboard, sql server, performance, databases, microsoft, security, blog, environment, best practice, backups, monitoring, baseline, benchmarking, downloads, performance monitoring
Security, whether it is for your home or systems you have to be very careful! Ed Gibson, Chief Cyber Security Advisor from Microsoft has articulated very nice article that will talk more about these aspects, we have had a brief meeting with Ed when I was at Microsoft TVP during SQLBits conference. You...
What is your criteria on assigning ports to SQL Server? Are you leaving them to default 1433? Is your SQL Server is exposed to Internet or any external sources where there is a chance to produce mass attach or run code injection? Every DBA should give a review about these 3 points on the terms of security...