Articles

External Article

PostgreSQL Constraints: Learning PostgreSQL with Grant

One of the most important aspects of data management is the ability to ensure that the data in your database is well defined and consistent. Some aspects of that are ensured through the relational data structures you design. Another piece of control is using the correct data type. Then, we get to constraints. A constraint is a way to validate data prior to adding it to your database. This is one more tool in the toolbox that helps you maintain good data.

2023-03-22

External Article

The future of AI in solving database challenges

The conversation around Artificial Intelligence (AI) is not a new subject to the database space, but the recent rise in machine learning tools like ChatGPT have sparked increased focus on new ways to simplify existing DBA challenges.

Join Redgate’s own DevOps Advocate, Steve Jones, along with webinar guests Kellyn Pot’Vin-Gorman (Principal Cloud Solution Architect, Microsoft) and Brian Randell (Product Marketing Director, Github) to discuss how AI could help manage complex database ecosystems.

2023-03-22

Blogs

Should You Use CHOOSE(): #SQLNewBlogger

By

I was experimenting with CHOOSE() recently after I was asked a question. In a...

T-SQL Tuesday #204 – Are blogs still relevant? (Roundup)

By

I did not expect 27 responses to my T-SQL Tuesday #204 invitation, but it...

Build vs Buy AI: When to adopt, partner, build or buy

By

Should you adopt an off-the-shelf AI tool, partner with a specialist, build in-house, or...

Read the latest Blogs

Forums

Weird problem altering logins with sysadmin account

By Brandie Tarvin

Has anyone ever seen this before? I have sysadmin permission on a server. I...

Switching Schema II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Switching Schema II

A Practical Approach to Automating SQL Server Email Notifications

By Kunal Rathi

Comments posted to this topic are about the item A Practical Approach to Automating...

Visit the forum

Question of the Day

Switching Schema II

I run this query:

SELECT 
 s.name AS schemaname
 , o.name AS objectname
 FROM sys.objects o
 INNER JOIN sys.schemas s ON s.schema_id = o.schema_id
 WHERE o.name = 'Beer'
I get two rows back for the objects, named dbo.beer and etl.beer. Both the tables have identical schemas and are not partitioned. There are 25 rows in dbo.beer and 0 rows in etl.beer. I run this code:
ALTER TABLE dbo.beer switch TO etl.beer
What happens?

See possible answers