2023-03-27
357 reads
2023-03-27
357 reads
2019-06-14
1,586 reads
2018-08-07
954 reads
2016-09-30
1,260 reads
When you are inserting, updating, or deleting records from a table, SQL Server keeps track of the records that are changed in two different pseudo tables: INSERTED, and DELETED. These tables are normally used in DML triggers. If you use the OUTPUT clause on an INSERT, UPDATE, DELETE or MERGE statement you can expose the records that go to these pseudo tables to your application and/or T-SQL code.
2012-03-26
3,728 reads
Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...
By Steve Jones
Next year the PASS Data Community Summit is in DENVER! and London, but Denver...
By Steve Jones
Yesterday was the first day of sessions at the PASS Data Community Summit (after...
Comments posted to this topic are about the item Pay for Performance, which is...
Jl. Raya Utara Adiwerna No.304, 306, Pejagan, Adiwerna, Kec. Adiwerna, Kabupaten Tegal, Jawa Tengah...
Jl. P. Diponegoro No.141, Dukuhtengah, Dukuh Tengah, Kec. Ketanggungan, Kabupaten Brebes, Jawa Tengah 52663
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 one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers