SQL Server 2005 is out and everyone is moving to test and deploy it. However many people are still managing SQL Server 2000 instances. New author Boris Baliner brings us a few tricks to find that information you are used to from Enterprise Manager.
The Sarbanes-Oxley act has changed many IT jobs, usually requiring more work and documentation. Johan Bijnens brings us a list of some things his team has had to do to comply with SOX regulations.
Our SQL Server Security expert, Brian Kelley, brings us the first part of a new series on auditing. Most of the auditing articles we've had are based on how you audit changes to data. Brian looks at auditing from the server itself, explaining the different levels of auditing built into SQL Server 2000.
In this series of articles, Chris Kempster will discuss some of the finer aspects of SQL Server security and also touch on OS, physical and application security to open up this science for general discussion.
As yo probably know, Brian covers security topics for us and does a great job. This week he looks at the fixed roles and points out a few things you may not have thought about.
Performance tuning is an ongoing battle in SQL Server, but having a little knowledge up front when designing an application can greatly reduce the efforts. Do you know which performs better: stored procedures or triggers? There aren't many places where the two are interchangeable, but knowing the impacts of each might change the way you build an application. Read about this analysis by Vijaya Kumar.
Need to proper case names? Want a quick way to reformat a series of words? This article examines a SQL approach to quickly proper casing all words in a field.
This is an entry level look at how temp tables work in SQL along with some tips about how to use them effectively.
It has been nearly 5 years since SQL Server 2000 was released and almost seven since Query Analyzer was introduced in SQL Server 7. Surely every trick, tip, technique, or secret has been published by now? Perhaps, but this might be a new one from Yakov Shlafman. Check out what he thinks is the best kept secret.
There are probably not many SQL Server DBAs that use the semicolon as a statement separator. In SQL Server 2005, this is required in certain places and new author Kenneth Powers brings us a look at where and why you need to use this syntax.
By Steve Jones
I’ve often done some analysis of my year in different ways. Last year I...
By Steve Jones
This was Redgate in 2010, spread across the globe. First the EU/US Here’s Asia...
By John
Today is Christmas and while I do not expect anybody to actual be reading...
I have a couple of SQL Agent job steps which run PowerShell commands of...
Comments posted to this topic are about the item Database security permissions save script
I have a SQL Agent job for backing up a set of Analysis Services...
I want to use the new BASE64_ENCODE() function in SQL Server 2025, but return a string that isn't large type. What is the longest varbinary string I can pass in and still get a varchar(8000) returned?
See possible answers