Databases Reference
In-Depth Information
experiencing heavy tempdb usage. The challenge prior to SQL Server 2012 was that solid-state storage
cards, like those provided by FusionIO and Texas Instruments, plug straight into a server's mother-
board to avoid all the overhead of traditional storage buses. This made it very difi cult to use them at
all in failover cluster instances and now they can be used for the discrete task of running tempdb.
The second reason you might want to use a local tempdb is to take I/O requests off your shared
storage to improve the performance of the shared storage. We used this to great effect for one
customer who was really at the peak of their SANs performance capacity; a FusionIO card was
placed in each node of several failover clusters and all tempdb activity was re-directed locally. Even
though tempdb performance was never bad before, the result was a signii cant reduction in load
against the SAN which extended its life by an additional six months.
Tempdb Initial Sizing and Autogrowth
A default installation of any SQL Server edition will create a tempdb database with an 8MB data i le
and a 1MB transaction log i le. For a lot of SQL Server installations these i le sizes won't be enough,
but they are coni gured to autogrow by 10% as needed. You can see the properties window for
tempdb on a default installation of SQL Server 2012 Developer Edition in Figure 8-16.
FIGURE 8-16
Search WWH ::
Custom Search