SQL Server使用Merge语句当源表数据集为空时,无法进行查询的问
今天使用Merge语句时遇到了一个问题,当源表数据集为空时,merge就不工作了。
面举一个例子来具体说明一下:
有两个表SourceTable为登陆表,TargetTable为授权表,如果访问用户在登陆表中,更新授权表的授权级别,否则授权0表示游客。sql语句如下:
--SourceTable为登陆表,TargetTable为授权表
--如果访问用户在登陆表中,更新授权表的授权级别,否则授权0表示游客。
create table SourceTable(UserName nvarchar(10),Pwd int,[Level] int)
create table TargetTable(UserName nvarchar(10),[Level] int)
go
--下面是SQL Server2008新增的赋值功能,更多新功能请参见
insert into SourceTable values('user1','111',1),('user2','222',2),('user3','333',3)
insert into TargetTable values('user1',1),('user2',2)
一般情况,我们会写如下的语句:
代码如下:
declare @UserName varchar(10) = 'user2'--表示某个登陆的用户名
merge into TargetTable as tg
using (select UserName,[Level] from SourceTable where UserName=@UserName)
as sr(UserName,[Level]) on tg.UserName=sr.UserName
when matched then
update set [Level]=sr.[Level]--更新授权级别
when not matched by target then
insert (UserName,[Level]) values(@UserName,0)--表示游客
output $action;
执行结果为UPDATE,表示执行了更新操作,也正是我们想要的。
但是如果我们把@UserName赋值为'user6',希望能在TargetTable中插入一条记录,但是实际执行结果为空,显示什么都没执行。原因就是using (select UserName,[Level] from SourceTable where UserName=@UserName) as sr(UserName,[Level]) on tg.UserName=sr.UserName这个语句中,sr结果集为空,所以merge语句就不向后执行了,不知道这是不是SQL Server的bug。
下面的SQL可以解决上面的问题:
代码如下:
declare @UserName varchar(10) = 'user7'--表示某个登陆的用户名
merge into TargetTable as tg
using (select @UserName)
as sr(UserName) on tg.UserName=sr.UserName
when matched then
update set [Level]= (select top 1 [Level] from SourceTable where UserName=@UserName)
--更新授权级别
when not matched by target then
insert (UserName,[Level]) values(@UserName,0)--表示游客
output $action;

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The import steps are as follows: Copy the MDF file to SQL Server's data directory (usually C:\Program Files\Microsoft SQL Server\MSSQL\DATA). In SQL Server Management Studio (SSMS), open the database and select Attach. Click the Add button and select the MDF file. Confirm the database name and click the OK button.

For objects with the same name that already exist in the SQL Server database, the following steps need to be taken: Confirm the object type (table, view, stored procedure). IF NOT EXISTS can be used to skip creation if the object is empty. If the object has data, use a different name or modify the structure. Use DROP to delete existing objects (use caution, backup recommended). Check for schema changes to make sure there are no references to deleted or renamed objects.

To view the SQL Server port number: Open SSMS and connect to the server. Find the server name in Object Explorer, right-click it and select Properties. In the Connection tab, view the TCP Port field.

When the SQL Server service fails to start, here are some steps to resolve: Check the error log to determine the root cause. Make sure the service account has permission to start the service. Check whether dependency services are running. Disable antivirus software. Repair SQL Server installation. If the repair does not work, reinstall SQL Server.

If you accidentally delete a SQL Server database, you can take the following steps to recover: stop database activity; back up log files; check database logs; recovery options: restore from backup; restore from transaction log; use DBCC CHECKDB; use third-party tools. Please back up your database regularly and enable transaction logging to prevent data loss.

SQL Server database files are usually stored in the following default location: Windows: C:\Program Files\Microsoft SQL Server\MSSQL\DATALinux: /var/opt/mssql/data The database file location can be customized by modifying the database file path setting.

The problem was found that this time I was using the SqlServer database, which I had not used before, but the problem was not serious. After I connected the SqlServer according to the steps in the requirements document, I started the SpringBoot project and found an error, as follows: At first I thought it was a SqlServer connection. There was a problem, so I went to check the database and found that everything was normal. I first asked my colleagues if they had such a problem, and found that they did not, so I started my best part, facing Baidu. programming. The specific error message I started to solve was this, so I started Baidu error reporting: ERRORc.a.d.p.DruidDataSource$CreateCo

If the SQL Server installation fails, you can clean it up by following these steps: Uninstall SQL Server Delete registry keys Delete files and folders Restart the computer
