Starting and Stopping SQL Server Part 2
Continuing with his series, Andy Warren looks at what it means for SQL Server 2000 to run as a service and some of the options you have for starting, stopping, and restarting your server.
Continuing with his series, Andy Warren looks at what it means for SQL Server 2000 to run as a service and some of the options you have for starting, stopping, and restarting your server.
Most SQL Server 2000 DBAs have heard of Notification Services, but are they aware of how it works and what it's capabilities are? This is a great platform on which to build any type of messaging/notification/subscription application. New author and PASS board member Joe Webb brings us a look at this add on for SQL Server.
This paper describes the new CLR integration features of SQL Server 2005 and how database application developers and architects can take advantage of them to write user-defined procedures, functions, and triggers, as well as define new types and aggregates
The integration of SQL Server 2000 with version control is basically nonexistent. Managing and keeping track of your changes and files is a cumbersome task, and prone to have mistakes occur. There is a product that can help you with this called dbGhost and Jeremy Brown takes a look at this product and how it works.
Have you ever needed to audit your SQL Server 2000 database for changes to a table? A simple auditing solution is presented here by new author Tiago Silva using an INSTEAD OF trigger.
Are you looking to move your Oracle databases to SQL Server? You should be and when you convince your management to do so, Microsoft has a tool to help. New author Suresh Maganti of Scalability Experts brings us a look at how this works.
A deadlock is an inevitable situation in the RDBMS architecture and very common in high-volume OLTP environments. A deadlock situation is when at least two transactions are waiting for each other to complete. The Common Language Runtime (CLR) of .NET lets SQL Server 2005 provide developers with the latest way to deal with error handling. In case of a deadlock, the TRY/CATCH method is powerful enough to handle the exceptions encountered in your code irrespective of how deeply nested the application is in a stored procedure.
Are you up for a quick game of who's the best DBA? A little humerous diversion on one of the big holidays in the US.
A view is a virtual table that consists of columns from one or more tables. Though it is similar to a table, it is stored in the database. It is a query stored as an object. Hence, a view is an object that derives its data from one or more tables. These tables are referred to as base or underlying tables.
SQL Server 2000 error handling isn't the most mature system for dealing with unexpected events. It has been much enhanced in SQL Server 2005, but many people will be using SQL Server 2000 for a long time. RAISERROR is one of those functions that can really aid in troubleshooting, but is often underutilized. David Poole brings us some hints on how this can help you out in your code.
By Vinay Thakur
Continuing from Day 3 where we covered LLM models open/closed and their parameters, Today...
By Steve Jones
One of the nice things about Flyway Desktop is that it helps you manage...
By HeyMo0sh
Microsoft Fabric (not to be confused with the more general term “fabric” in DevOps)...
I'm fairly certain I know the answer to this from digging into it yesterday,...
Hi Team, I am trying to refresh the Azure Synapse Dedicated pool from production...
hi everyone I am not sure how to write the query that will produce...
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 *
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t; See possible answers