2,099 reputation
1723
bio website 127.0.0.1
location Frankfurt Am Main, Germany
age 26
visits member for 2 years, 8 months
seen yesterday

-


2d
awarded  Popular Question
Oct
22
comment Index file - size changed
I'm unclear on what metric exactly you're referring to. Disk space usage? Allocated space? Unallocated space? A rebuild can reduce allocated space. it will never shrink a file on disk.
Oct
21
comment What happens in this strange SQL Server Mirroring situation?
@SeanGallardy when S2 is further along in time there is no way to roll back to the state that S1 is in. How would a negotiation fix that? Assume that S2 has taken a write that S1 does not have as stated in the question.
Oct
20
comment What happens in this strange SQL Server Mirroring situation?
That's true and I agree with what you've said provided the principal hardens first. The docs are in conflict about that information.
Oct
20
comment What happens in this strange SQL Server Mirroring situation?
It's a thought experiment. I'm thinking about where in the CAP theorem option space SQL Server synchronous Mirroring lies. "Hardening" is the act of physically writing a log record. All the talk about log buffers is a red herring. That's an in-memory data structure (which can disappear at any time).
Oct
20
comment What happens in this strange SQL Server Mirroring situation?
The documentation is inconsistent. "My" link tells us: "The principal server writes the transaction to the database and, concurrently, sends the log record to the mirror server.". "Your" document states that the principal hardens first. That would make my scenario impossible but it would allow the mirror to fall behind slightly.
Oct
20
comment What happens in this strange SQL Server Mirroring situation?
When I say "harden" I mean "hardening of the commit record". This is the only record that counts.; There is no difference between hardening and considering the transaction committed. If immediately after hardening the power fails the transaction will be considered committed after startup. The in-memory state is lost. SQL Server has forgotten that maybe it need acknowledgement from the mirror.
Oct
20
comment What happens in this strange SQL Server Mirroring situation?
And then? There is no way to consolidate the replicas. They have conflicting writes. Also, the network could be down so that the replicas cannot talk to each other.
Oct
20
asked What happens in this strange SQL Server Mirroring situation?
Oct
19
awarded  Civic Duty
Oct
19
answered Additional space required for INDEX REORGANIZE
Oct
19
revised Strange query results for DELETE with ROW_NUMBER
added 12 characters in body
Oct
19
comment Strange query results for DELETE with ROW_NUMBER
This is a one-off data migration script. I'm not personally interested in a workaround but it would be a useful addition to the question. It would be a useful answer.
Oct
18
accepted Strange query results for DELETE with ROW_NUMBER
Oct
18
asked Strange query results for DELETE with ROW_NUMBER
Oct
17
comment Why does a UNIQUE constraint allow only one NULL?
The NULL behavior of the standard is really awkward. Back when this indexing behavior was decided they obviously did not hold the standard in high regard. They still don't do that but standards compliance apparently has become more important to the team.
Oct
17
answered What backup/restore strategy can I use for the following scenario
Oct
15
comment Dramatic decrease in SQL Azure performance after scaling to new edition
If you'Re curious you can test allocated buffer pool size by scanning the same table repeatedly and adding small amounts of data. Eventually the scan will suddenly take much longer. At that point measure the table size.
Oct
15
awarded  Organizer
Oct
15
revised SQL Server data files in Windows Azure: filegroups and partitioning still applicable?
removed fluff