How many of you register a server in Enterprise Manager? Now how many of you click the "save password" box? Probably most of you. Are you aware of the security risks associated with this? James Travis looks at one of potential problems here and other security issues relating to SQL-DMO.
Another look at how the next version of SQL Server will integrate and work with .NET technologies.
Although Brian likes that Microsoft delayed the next release of SQL Server for quality, he disagrees with the release strategy. See his opinion and argue your own!
It's been some time and he apologizes. This next part of this series from Steve Jones looks at selective auditing changes to data on the server using a combination of methods presented in previous articles in the series. Read on if you have problems tracking changes to data on some tables, but don't want to implement a solution that tracks every change.
Error handling is one of those things that is simple to do in SQL Server, but most people don't do it and it's not the most rebust thing. Here's another way that you can implement error handling in your stored procedures from a new author Amit Jethva.
Have you ever built a join graphically using Access or Visual Studio? Did you know that you can do this with the native SQL Server tools? And it's easy! Follow along as Dale Corey shows you how.
The fourth and final installment in this series, this week Andy discusses how using XML can reduce the load you put on your network and on your server. This is a high level article that discusses concepts. We think you'll find a good idea or two in this one!
Lumigent Technologies today announced that they are a recommended supplier to provide data auditing solutions for risk management to customers of Microsoft SQL Server 2000 through their Entegra product. Enterprises that depend on SQL Server databases can now rely on Entegra as a trusted auditing solution to enable compliance with regulatory requirements.
The error handling in SQL Server leaves something to be desired, especially compared with other RDBMSes and languages. The standard method of testing for errors can leave your code bloated and hard to read. Stefan Popovski looks at another method of handling errors.
What's wrong with SQL Server? Lots of things to some people, but here's a look at where this product is positioned in the marketplace against the other RDBMSes.
By Brian Kelley
If you want to learn better, pause more in your learning to intentionally review.
By John
If you’ve used Azure SQL Managed Instance General Purpose, you know the drill: to...
By DataOnWheels
Ramblings of a retired data architect Let me start by saying that I have...
Comments posted to this topic are about the item Faster Data Engineering with Python...
Comments posted to this topic are about the item Which Result II
Comments posted to this topic are about the item JSON Has a Cost, which...
I have this code in SQL Server 2022:
CREATE SCHEMA etl;
GO
CREATE TABLE etl.product
(
ProductID INT,
ProductName VARCHAR(100)
);
GO
INSERT etl.product
VALUES
(2, 'Bee AI Wearable');
GO
CREATE TABLE dbo.product
(
ProductID INT,
ProductName VARCHAR(100)
);
GO
INSERT dbo.product
VALUES
(1, 'Spiral College-ruled Notebook');
GO
CREATE OR ALTER PROCEDURE etl.GettheProduct
AS
BEGIN
exec('SELECT ProductName FROM product;')
END;
GO
When I execute this code as a user whose default schema is dbo and has rights to the tables and proc, what is returned? See possible answers