使用sqlServer怎么实现垂直分表?很多新手对此不是很清楚,为了帮助大家解决这个难题,下面小编将为大家详细讲解,有这方面需求的人可以来学习下,希望你能有所收获。源表设计结构:-- 源表CREATE TAB
使用sqlServer怎么实现垂直分表?很多新手对此不是很清楚,为了帮助大家解决这个难题,下面小编将为大家详细讲解,有这方面需求的人可以来学习下,希望你能有所收获。
源表设计结构:
-- 源表CREATE TABLE [dbo].[DemoTab]([Guid] [uniqueidentifier] NOT NULL,[UserName] [nvarchar](30) NOT NULL,[PassWord] [nvarchar](30) NOT NULL,[UserAccount] [varchar](30) NOT NULL,[Amount] [numeric](18, 4) NULL,CONSTRaiNT [PK_DemoTab] PRIMARY KEY CLUSTERED ([Guid]))Go ALTER TABLE [dbo].[DemoTab] ADD CONSTRAINT [DF_DemoTab_Guid] DEFAULT (newsequentialid()) FOR [Guid]GO -- 原来是访问视图的(好处就是视图层不变)CREATE VIEW [dbo].[VDemoTab]ASSELECT [Guid],[UserName],[Password],[UserAccount],[Amount]FROM [dbo].[DemoTab]GO
注:拆分后各表的主键都是相同了,而且拆分后的表是规范化的。
现在拆成两张表:
注意选择一张表作为基表,其他表都有与该表的外键。
-- 分表【1】,以该表为"主表",其他拆分出的表为"子表"CREATE TABLE [dbo].[DemoTab001]([Guid] [uniqueidentifier] NOT NULL,[UserName] [nvarchar](30) NOT NULL,[Password] [nvarchar](30) NOT NULL,CONSTRAINT [PK_DemoTab001] PRIMARY KEY CLUSTERED ([Guid]))GO -- 主键默认值可以不需要,因为插入数据前需要确定主键值--ALTER TABLE [dbo].[DemoTab001] --ADD CONSTRAINT [DF_DemoTab001_Guid] DEFAULT (newsequentialid()) FOR [Guid]--GO -- 分表【2】,"子表"CREATE TABLE [dbo].[DemoTab002]([Guid] [uniqueidentifier] NOT NULL,[UserAccount] [varchar](30) NOT NULL,[Amount] [numeric](18, 4) NULL,CONSTRAINT [PK_DemoTab002] PRIMARY KEY CLUSTERED ([Guid]))GO -- 主键默认值可以不需要,因为插入数据前需要确定主键值--ALTER TABLE [dbo].[DemoTab002] --ADD CONSTRAINT [DF_DemoTab002_Guid] DEFAULT (newsequentialid()) FOR [Guid]--GO -- 若主表变更主键则级联更新或删除(主键通常是不更新的,也可省去 ON UPDATE CASCADE)ALTER TABLE [dbo].[DemoTab002] ADD CONSTRAINT [FK_DemoTab002_DemoTab001_Guid] FOREIGN KEY ([Guid]) REFERENCES [DemoTab001]([Guid]) ON UPDATE CASCADE ON DELETE CASCADEGO
如果之前是对单个表或者视图操作,拆分之后逻辑层改动可能很多,为保持改动最小,可以用联合视图操作。怎么连接表依个人情况而定。
-- 拆分后使用联合视图(INNER JOIN 也可以)ALTER VIEW [dbo].[VDemoTab]ASSELECT T1.[Guid],T1.[UserName],T1.[Password],T2.[UserAccount],T2.[Amount]FROM [dbo].[DemoTab001] T1 LEFT JOIN [dbo].[DemoTab002] T2 ON T1.[Guid]=T2.[Guid]GO
这时问题来了,要对表进行DML操作,insert , update , delete 怎么解决?因为要求主键是分散在多个表并且是相同的!
这时只能用考虑触发器来保证一致性了,触发器则定义在视图上,使用的是 INSTEAD OF 类型的触发器。
insert 触发器:
视图 [VDemoTab] 中的 [Guid] 为表 插入时值,在插入触发器中,虚拟表[inserted]的[Guid]是唯一的,所以在触发器中可以同时使用该 [Guid] 插入到多个分表中,保证了多个分表的[Guid]是相同的!
-- insert 触发器CREATE TRIGGER [dbo].[tgr_VDemoTab_insert]ON [dbo].[VDemoTab] INSTEAD OF INSERTAS BEGIN INSERT INTO [dbo].[DemoTab001]([Guid],[UserName],[Password]) SELECT [Guid],[UserName],[Password] FROM inserted; INSERT INTO [dbo].[DemoTab002]([Guid],[UserAccount],[Amount]) SELECT [Guid],[UserAccount],[Amount] FROM inserted;ENDGO
update 触发器:
同理,更新时涉及虚拟表 deleted 和 inserted,而更新是对视图[VDemoTab]更新的,所以虚拟表inserted包括了所有的字段,所以需要触发器分别更新多个分表。
-- update 触发器CREATE TRIGGER [dbo].[tgr_VDemoTab_update] ON [dbo].[VDemoTab] INSTEAD OF UPDATE ASBEGIN UPDATE T1 SET T1.[UserName] = T2.[UserName], T1.[Password] = T2.[Password] FROM [dbo].[DemoTab001] AS T1, inserted AS T2 WHERE T1.[Guid] = T2.[Guid] UPDATE T1 SET T1.[UserAccount] = T2.[UserAccount], T1.[Amount] = T2.[Amount] FROM [dbo].[DemoTab002] AS T1, inserted AS T2 WHERE T1.[Guid] = T2.[Guid] ENDGO
delete 触发器:
删除视图[VDemoTab]记录,涉及多个表则不允许删除,因此只要删除"主表"的记录即可,其他分表都会级联删除。
-- delete 触发器CREATE TRIGGER [dbo].[tgr_VDemoTab_delete] ON [dbo].[VDemoTab] INSTEAD OF DELETE ASBEGIN DELETE FROM [dbo].[DemoTab001] WHERE [Guid] IN (SELECT [Guid] FROM deleted)ENDGO
设计基本就完成了,现在进行测试。
INSERT INTO [dbo].[VDemoTab]([Guid],[UserName],[Password],[UserAccount],[Amount])SELECT NEWID(),'user01','pw01','account01',100UNION ALLSELECT NEWID(),'user02','pw02','account02',99UNioN ALLSELECT NEWID(),'user03','pw03','account03',0GO UPDATE [VDemoTab] SET [Password]='pw',[Amount]='10'WHERE [Amount] >=0 AND [Amount]<100 AND [UserName] LIKE '%3'GO DELETE FROM [VDemoTab] WHERE [UserName] = 'user03'GO SELECT * FROM [dbo].[DemoTab001] SELECT * FROM [dbo].[DemoTab002] SELECT * FROM [dbo].[VDemoTab]
看完上述内容是否对您有帮助呢?如果还想对相关知识有进一步的了解或阅读更多相关文章,请关注编程网精选频道,感谢您对编程网的支持。
--结束END--
本文标题: 使用SqlServer怎么实现垂直分表
本文链接: https://lsjlt.com/news/271081.html(转载时请注明来源链接)
有问题或投稿请发送至: 邮箱/279061341@qq.com QQ/279061341
2024-05-24
2024-05-24
2024-05-24
2024-05-24
2024-05-24
2024-05-24
2024-05-24
2024-05-24
2024-05-24
2024-05-24
回答
回答
回答
回答
回答
回答
回答
回答
回答
回答
0