Tag Info

Hot answers tagged

9

rowversion is just an alias for timestamp. Under the covers, they are the exact same thing. If you're using the GUI (prior to 2012), you have to use timestamp. (Peripheral hint: please stop using the GUI.) But it doesn't stop there. Even if you generate this table using DDL: CREATE TABLE dbo.x(y ROWVERSION); The data type in the metadata will be ...


8

The top levels of the plan are concerned with removing rows from the base table (the clustered index), and maintaining four nonclustered indexes. Two of these indexes are maintained row-by-row at the same time the clustered index deletions are processed. These are the "+2 non-clustered indexes" highlighted in green below. For the other two nonclustered ...


5

When the script is generated in Profiler 2005, the default value saved for the logical operator is 1='OR', so the trace will capture more information than we initially intended. exec sp_trace_setfilter @TraceID, 8, 1, 0, N'HOSTNAME1' -- OR exec sp_trace_setfilter @TraceID, 8, 1, 0, N'HOSTNAME2' exec sp_trace_setfilter @TraceID, 8, 1, 0, N'HOSTNAME3' ...


3

You're on the right track - the XML index is the problem. Obviously, there's a primary as well as a secondary XML index. When performing a DELETE against the base table (ETLHeaders) the data have to be deleted from every index of this table, too. This overhead can be significant, especially for XML indexes. The index causing the long duration is the ...


2

After you enable the CDC on a database 2 jobs are created for that database: cdc.DBName_capture (which will start the change data capture collection agent) cdc.DBName_cleanup (which will clean up the change tables periodically) the default retention is 3 days (data older than 3 days is removed) the default schedule for this job is daily at 02:00 AM The ...


1

When I have encountered similar problems to this in the past, I have used the query that marc_s provides here: Know relationships between all the tables of database in SQL Server It should give you a good place to start? Here it is replicated in case the other thread is removed in the future (credit - marc_s): SELECT fk.name 'FK Name', tp.name 'Parent ...


1

You would have to check running queries on the remote server. You could isolate linked server queries by filtering on your linked server name with the following dmv query. SELECT [s].[session_id] AS [spid] ,[s].[status] ,[s].[login_name] AS [loginName] ,[s].host_name AS ...



Only top voted, non community-wiki answers of a minimum length are eligible