The default location for the SQL Server system databases doesn't always meet the standards of many organizations. Author Chris Hedgate has taken the time to put together a short checklist on how you can move the master, msdb, model, and tempdb databases easily.
2004-11-30
21,847 reads
SQL Server was designed to make the DBA job easier, distribution of security, automated procedures, etc. But in some areas it either does not go far enough, or a feature is used for an unintended purpose. One of those areas comes into play when allowing many people to create databases. Author Eli Leiba brings us a tecehnique he uses to close the gap and track down those newly created databases.
2004-11-18
4,957 reads
SQL Server 7 revamped Enterprise Manager to be an MMC snap in with many more capabilities and functions than it had in SQL Server 6.5. Dale Elizabeth Corey brings us a look at the top ten features in Enterprise Manager that you may not be aware of.
2004-11-16
11,319 reads
SQL Server has a great scheduling system in SQLAgent. But sometimes SQLAgent won't work or isn't available. Author Andre Vigneau has built a solid system for auomtating the management of SQL Server, one that he deploys with the software that his company sells. Read about the basics of this system and get some code that might come in handy for you.
2004-11-04
5,873 reads
2004-11-02
1,857 reads
SQL Server shows lots of information in Enterprise Manager, but getting a report for someone or manipulating this data is hard from the GUI. Using T-SQL, it's easier, but sometimes not obvious how to get the data. Author Santveer Singh brings us a way to get at some of that information, the users and their database roles.
2004-11-02
23,785 reads
SQL Server 2005, the next evolution of SQL Server, should be growing the capacities as well as the capabilities of the product. With some research, Steve Jones brings you the best current information he could find about SQL Server 2005, comared with the SQL Server 7 and 2000 values.
2007-01-26 (first published: 2004-11-01)
41,912 reads
2004-10-28
1,650 reads
Blocks in SQL Server can cause untold amounts of pain and headache, mostly because they are so transient and often when you go to look for them, they have been released on whatever object you are researching. Author Eli Leiba has writeen a short piece on how you can automate the search for blocking locks and help you as a DBA be proactive in identifying them.
2004-10-28
12,403 reads
Change control in SQL Server isn't the strong point of the product. And change control of server based settings is something that you might not worry about, but which can easily cause you hours of troubleshooting time. Author Andre Vigneau deploys software to other companies and has developed a solution to deal with this problem. Read on and get some code that can help you prevent or at least fix any changes to SQL Server sp_configure parameters.
2004-10-26
11,377 reads
By HeyMo0sh
Microsoft Fabric (not to be confused with the more general term “fabric” in DevOps)...
By James Serra
I’m honored to be hosting T-SQL Tuesday — edition #192. For those who may...
By Vinay Thakur
Continuing from Day 2 , we learned introduction on Generative AI and Agentic AI,...
hi everyone I am not sure how to write the query that will produce...
Comments posted to this topic are about the item Rollback vs. Roll Forward
Comments posted to this topic are about the item Foreign Keys - Foes or...
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