Viewing 15 posts - 1 through 15 (of 20 total)
This is such a broad topic, and most of the DMV's work together to give you a better insight into performance problems. The Microsoft whitepaper "Troubleshooting Performance Problems...
September 25, 2012 at 3:57 am
The sys.dm_exec_query_stats is a central DMV to find the statistics of the current performance of cached query plans.
September 25, 2012 at 2:11 am
The transaction log is used for all modifications to guarantee atomicity, durability and consistency. Read Gail's thorough article.
http://www.sqlservercentral.com/articles/Administration/64582/
September 25, 2012 at 1:51 am
GilaMonster (9/21/2012)
Statements are not atomic.
Atomicity is a database principle(all or nothing), it is not to say it can/cant belong to something like a statement. You probably meant that they...
September 21, 2012 at 9:54 am
GilaMonster (9/20/2012)
The create table doesn't roll back for the same reason the create table doesn't roll back in this example
BEGIN TRAN
CREATE TABLE SillyTable (SomeVal int)
INSERT INTO SillyTable
SELECT 1/0
COMMIT TRANSACTION
A...
September 21, 2012 at 4:25 am
Nope, he's either wrong or is using a very extreme definition of 'durable'
Yes, I think you are right on the "extreme" definition, but he is clearly wrong if he states...
September 20, 2012 at 1:43 pm
Where did you find this? I don't think that is true at all. The rollback would remove the table.
begin transaction
select 5 as Col1 into SomeSillyTable
rollback transaction
select * from SomeSillyTable
Yes, for...
September 20, 2012 at 1:39 pm
The other possible query I can think of is SELECT INTO. This wont guarantee Atomicity and Consistency as the INTO table might still be created even if the transaction...
September 20, 2012 at 12:09 pm
I do not understand what you mean by batch based. You can issue only one delete statement with the datetimestamp in the WHERE clause and it will be one batch.
If...
May 23, 2012 at 5:10 am
Try to see which transaction(s) are taking up the space and kill it if possible..
You can find out with the DMV's with something like this (ordered by log space used)
Select...
May 22, 2012 at 12:20 pm
Try using the INTO statement if you can. This will only log the allocations and not the individual rows in the simple recovery as well as the bulked loged model:
SELECT
column1,
column2
INTO...
May 18, 2012 at 11:00 am
If you've got a database where the data file is optimised for reading (say raid 5 and read caches) and a transaction log optimised for writing (say raid 10 and...
May 15, 2012 at 2:32 am
Hi Gail,
Thanks for the great article..
One question:
One side effect of this requirement that both log records and modified data pages are written to disk before the transaction commits is that...
May 13, 2012 at 5:30 am
DECLARE @ParentChild AS TABLE
(
RowID INT
, ParentID INT
, ChildID INT
, WantThisRow VARCHAR(3)
)
DECLARE @GrandChild AS TABLE
(
RowID INT
, ChildParentIDINT
, GrandchildID INT
)
INSERT INTO @ParentChild
(RowID, ParentID, ChildID, WantThisRow)
SELECT 2310, 22402, 22403,...
April 23, 2012 at 9:18 am
itskanchanhere (4/19/2012)
The more I read on Isolation levels the more I get confused
I really don’t blame you. Transactions and isolation can be a very difficult and confusing, and BOL does...
April 19, 2012 at 3:01 pm
Viewing 15 posts - 1 through 15 (of 20 total)