Editorial

SQLServerCentral Editorial

The R2 Penalty

  • Editorial

An interesting point was made by a reader about the price of SQL Server licenses when R2 is released. Steve Jones comments about a penalty that some of you may find if you look to build a SQL Server 2008 server later this year.

You rated this post out of 5. Change rating

2010-02-17

259 reads

SQLServerCentral Editorial

When is 8000 too small?

  • Editorial

Over the years the page size in SQL Server has changed, growing larger to fit larger data sets. However not all functions have been modified to work with larger page sizes. Or even exceed them. Steve Jones wonders if it's time to increase the page size.

You rated this post out of 5. Change rating

2014-10-23 (first published: )

390 reads

Blogs

Learn Better: Pause to Review More

By

If you want to learn better, pause more in your learning to intentionally review.

Azure SQL Managed Instance Next-Gen: Bring on the IOPS

By

If you’ve used Azure SQL Managed Instance General Purpose, you know the drill: to...

SQL, MDX, DAX – the languages of data

By

Ramblings of a retired data architect Let me start by saying that I have...

Read the latest Blogs

Forums

Faster Data Engineering with Python Notebooks: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Faster Data Engineering with Python...

Which Result II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Which Result II

JSON Has a Cost

By Steve Jones - SSC Editor

Comments posted to this topic are about the item JSON Has a Cost, which...

Visit the forum

Question of the Day

Which Result II

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