SQL Server数据库AND视图中的表数是否有限制? [英] Is there a limit to the number of tables in a SQL Server database AND view?
问题描述
我正在使用SQL Server Standard Edition上的数据库，该数据库每天加载数据-随着表的增长和索引I/O的加入，SQLBulkInsert的性能正在降低(即使禁用/重建，它也会较慢)
I'm working with a database on SQL Server Standard edition that loads data every day - performance of the SQLBulkInsert is slowing down as the table grows and indexing I/O kicks in (even with disable/rebuild, its getting slower)
因此，向我建议的另一种方法是创建一个引用每个日常表(例如最后30个表)的视图.应该只是SELECT * FROM x UNION ALL SELECT * FROM y...
So, an alternative suggested to me was to create a view that references each one of the daily tables (or the last 30 for example). Should just be a case of SELECT * FROM x UNION ALL SELECT * FROM y...
可包含的表数或视图定义的长度是否有限制?
AND
数据库中的表数是否有限制?
Is there a limit to the number of tables that can be included, or the length of the view definition?
AND
Is there a limit to the number of tables in a database?
或者-有更好的方法来做到这一点(无需花费任何金钱，否则我将移至SQL Server Enterprise并使用分区表！)
OR - is there a better way to do this (without spending any money or I'd move to SQL Server Enterprise and use partitioned tables!)
推荐答案
Well, for limits, you can look at Maximum Capacity Specifications for SQL Server
作为另一种选择，我将使用分区表和分区索引.
As another option I would look at using partitioned tables and partitioned indexes.
这里要注意的重要事情之一是
One of the important things to note here is
已分区表和索引的数据分为以下几个单位: 可以分布在数据库中的多个文件组中.数据 被水平划分，以便将行组映射到 单个分区
The data of partitioned tables and indexes is divided into units that can be spread across more than one filegroup in a database. The data is partitioned horizontally, so that groups of rows are mapped into individual partitions
基本上说可以将分区分布到各种逻辑文件组中.这应该为您提供可观的性能改进.
Which basically states that you can spread the partitions accross various logical file groups. This should provide you with coniderable performance improvements.
这篇关于SQL Server数据库AND视图中的表数是否有限制?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
