By default, there are six achieved SQL Server Error Logs along with the ERRORLOG which is currently used. However, it is a Best Practice to increase the number of SQL Server Error Logs from the default value of six. In this tip, you will see the steps which you need to follow to increase the number of SQL Server Error Logs.
2009-09-21
2,211 reads
Python is increasingly used by DBAs as a general-purpose scripting language, despite the pressure to adopt Microsoft's PowerShell. They find it easy to learn, powerful, and reasonably intuitive. Here Timothy Wiseman, a working DBA, explains the attraction of Python and gives a general introduction to the language, suitable for anyone who has been wondering whether to give it a try.
2009-09-18
5,678 reads
This article discusses the connectivity and usage of Teradata database servers and the .NET Framework Data Provider for Teradata with Microsoft SQL Server 2008 Reporting Services (SSRS).
2009-09-18
2,924 reads
2009-09-17
5,021 reads
Marcin Policht continues his discussion of SQL Server 2005 Express Edition security related topics by describing functionality that facilitates protecting HTTP-based communication with the Reporting Services Web site by leveraging Secure Sockets Layer (SSL) encryption.
2009-09-17
2,126 reads
The key to working with null values properly is to accommodate them consistently. Learn a few tricks that will help you do just that.
2009-09-16
4,497 reads
Migrating a database is often a task fraught with complications, this series examines the key issues in a simple checklist.
2009-09-16
3,369 reads
I have seen the tip Dynamically Control Data Filtering in SQL Server Reporting Services Reports which showed how to leverage a SQL Server database table to filter sales data based on the user running the report. I have a similar requirement to implement dynamic filtering except my data is in a SQL Server Analysis Services (SSAS) cube and the users query the data with a variety of different tools. How can I implement dynamic security in my case?
2009-09-15
2,770 reads
Change data capture is a new feature in SQL Server 2008 that provides an easy way to capture changes to data in a set of database tables so these changes can be transferred to a second system like a data warehouse. This document provides guidance on how to configure change data capture parameters to maximize data capture performance while minimizing the performance impact on the production workload. The scope of this document is limited to the capture of change data and the cleanup process. Querying the changed data is out of scope for this white paper.
2009-09-15
2,531 reads
High-Availability depends on how quickly you can recover a production system after an incident that has caused a failure. This requires planning, and documentation. If you get a Disaster Recovery Plan wrong, it can make an incident into a catastrophe for the business. Hugo Shebbeare discusses some essentials, describes a typical system, and provides sample documentation.
2009-09-14
4,158 reads
By Zikato
I deployed a schema change to 30 servers using multi-server query and deploy-at-low-priority. Small...
Fabric deployment pipelines look like they solve CI/CD for Fabric content, especially for people...
By Steve Jones
We aren’t the only company that does this, but Redgate Software does try to...
Hello We recently encountered an issue where a SQL table unexpectedly grew in size...
Comments posted to this topic are about the item The New World Of AI...
Thanks in advance, I'm trying to avoid using IIF for performance reasons, but the...
What does this return on SQL Server 2025?
select bit_count(null)See possible answers