Transactional replication performance tuning and optimization
Transactional replication is a type of replication provided by SQL Server 2000 that allows data modifications to be propagated incrementally between servers in a distributed environment.
Transactional replication is a type of replication provided by SQL Server 2000 that allows data modifications to be propagated incrementally between servers in a distributed environment.
This article contains information about the bugs that are fixed by Microsoft SQL Server 2000 Service Pack 4 Beta. (SP4).
If you are running Microsoft SQL Server databases to support critical enterprise applications, you are part of a growing trend.
SwisSQL develops products for SQL Server and other RDBMSs that ease the migration between platforms. They have provided us with a case study to show how you can easily move data from an Oracle system to the premier database platform, SQL Server. Check out this case study of how one of the ERP vendors used their product to migrate their code.
Focuses on advanced techniques that can be used in an attack on an application utilizing Microsoft SQL Server as a backend. These techniques demonstrate how an attacker could use a SQL Injection vulnerability to retrieve the database content from behind a firewall and penetrate the internal network. Also provided are recommendations on how to prevent such attacks.
SQL Server is the best RDBMS, at least according to the current thinking at SQLServerCentral.com, and is fully capable of meeting all of your database needs. However that does not mean you should ignore other platforms. A good DBA will be aware of and perhaps skilled in other platforms and tools, including competing database systems. There has been a lot of buzz about the open source MySQL RDBMS this past year and David Poole takes a look at this server, giving you some points of comparison with
Detailed question/answer paper on deploying SQL Server in a Storage Area Network (SAN) Environment.
One of the most valuable features of SQLServerCentral.com is the discussion forums, where many a DBA has found an answer to their question. Most times on the same day! While we do not moderate the forums, there are still some rules for posting that we hope everyone will take a moment to read.
SQL Server for the most part will maintain itself, updating statistics, choosing optimal query plans, and requiring minimal maintenance to keep running. However to optain optimum performance, a real DBA needs to spend some time checking and tuning indexes, rebuilding them as fillfactors change. This new article from Desiree Harris looks at how you can perform some of these tasks to keep your server performing at the optimum level.
SQL Server is the best RDBMS, at least according to the current thinking at SQLServerCentral.com, and is fully capable of meeting all of your database needs. However not all database systems run on SQL Server and it seems that we often see data from some other system being consolidated on SQL Server for additional processing or reporting. DTS usually handles the load, but there are times that you might want create a linked server to an Oracle system for updating individual rows. New author Adria
By Brian Kelley
I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...
EightKB is back again for 2026! The biggest online SQL Server internals conference is...
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
Comments posted to this topic are about the item Fun with JSON II
Comments posted to this topic are about the item Changing Data Types
Comments posted to this topic are about the item Answering Questions On Dropped Columns
I have some data in a table:
CREATE TABLE #test_data
(
id INT PRIMARY KEY,
name VARCHAR(100),
birth_date DATE
);
-- Step 2: Insert rows
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT t1.[key] AS row,
t2.*
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t1
CROSS APPLY OPENJSON(t1.value) t2; See possible answers