Hot answers tagged sql-server-2008
11
It is holding that memory because you used it once so, obviously, you will probably use it again. This is the way SQL Server works: it will take the memory it needs (up to the max you've allowed), and will only give it back to the OS if the OS demands it. If you're not demanding memory back from SQL Server, why do you expect it to give it up? Allocating and ...
8
One way would be to make a system procedure in master and then create a wrapper in your maintenance database. Note that this will only work for one database at a time.
First, in master:
USE [master];
GO
CREATE PROCEDURE dbo.sp_GetFragStats -- sp_prefix required
@tableName NVARCHAR(128) = NULL,
@indexID INT = NULL,
@partNumber INT ...
4
what you can do is
Find out the database that consumes highest memory in buffer pool using below :
SELECT COUNT(*) AS cached_pages_count ,
( COUNT(*) * 8.0 ) / 1024 AS MB ,
CASE database_id
WHEN 32767 THEN 'ResourceDb'
ELSE DB_NAME(database_id)
END AS Database_name
FROM sys.dm_os_buffer_descriptors
GROUP BY database_id
...
3
If you're talking SQL Server, I have some specific advice about making database changes backward compatible. The ideas and concepts are quite similar to other platforms, but the code samples won't help much.
The basic idea is this: make your changes in such a way that they don't require downtime and that they don't break existing code. For example, if you ...
3
You're getting a truncation error, meaning the data that's coming in is larger than the field size you have specified. Try increasing the destination table field size and you should be good to go.
I get these alot when I work with email addresses as the SQL import wizard defaults to 50, I always have to increase it every time I do a fresh import.
2
The length of your column in the new table is too small and the longer value from the file gets truncated as it cannot fit into the table column.
Data conversion failed. The data conversion for column ""Other
Provider Identifier Issuer_2"" returned status value 4 and status text
"Text was truncated or one or more characters had no match in the
...
1
Under the covers clustered and nonclustered indexes are the same. The clustered index just has the additional property that is is guaranteed to INCLUDE all columns. Therefore the data does not need to be maintained somewhere else. So, a clustered index and a nonclustered index that INCLUDEs all columns are virtually the same from an update cost perspective.
...
1
From my tip here:
;WITH src AS
(
SELECT
[Object] = o.name,
[Type] = o.type_desc,
[Index] = COALESCE(i.name, ''),
[Index_Type] = i.type_desc,
p.[object_id],
p.index_id,
au.allocation_unit_id
FROM sys.partitions AS p
INNER JOIN sys.allocation_units AS au
ON p.hobt_id = au.container_id
INNER ...
1
No physical truncation actually occurs, the size of the file would not get smaller.
Parts of the logfile (virtual logfile/vlf) are merely flagged as 'the content is allowed to be overwritten'. If such an event exists, and I know of none, there would be no practical duration.
If you are referring to 'auto-shrink', I would highly recommend you read this ...
1
After doing some research, including looking at this question, it appears it isn't directly possible to efficiently bulk load any of the CLR-based types, including geography. 1
You said that adding just the geography column added a significant amount of time to the load process -- this may, in fact, be entirely reasonable, depending on the amount of data ...
Only top voted, non community-wiki answers of a minimum length are eligible
