meta user
network profile
| bio | website | plixa.nl |
|---|---|---|
| location | Netherlands | |
| age | 34 | |
| visits | member for | 9 months |
| seen | May 7 at 8:19 | |
| stats | profile views | 5 |
Doing SQL Server for 5 years now, performance tuning, data modelling, etc. Also working with .Net since version 1. Doing both in a 25 hours a day, 370 days a year with much fun and passion!
|
May 6 |
answered | Maximum memory setting in SQL Server |
|
Feb 21 |
comment |
SQL Server Mirror failover on failing storage For reference, i managed to get it to work by using 1 database with different files. On each disk i made a file and i periodically insert/truncate stuff in/from it. Don't know for sure if i can manage to get it to work without this inserting/truncating, but with i can failover much faster (no insert = failover in my case) |
|
Jan 29 |
comment |
Getting SQL Server query history You are so right! Mixed the two up (was way too early, no coffee, no good sleep, you catch the point) |
|
Jan 29 |
awarded | Commentator |
|
Jan 29 |
awarded | Teacher |
|
Jan 29 |
comment |
Getting SQL Server query history i hope you don't do this on a production environment ;) |
|
Jan 29 |
answered | Getting SQL Server query history |
|
Jan 29 |
comment |
Getting SQL Server query history You must NEVER EVER run this on a production system! This is very bad because you will clear the complete buffer cache. |
|
Nov 15 |
awarded | Scholar |
|
Nov 15 |
comment |
SQL Server Mirror failover on failing storage Apparently this is the only way :) |
|
Nov 15 |
accepted | SQL Server Mirror failover on failing storage |
|
Nov 9 |
awarded | Supporter |
|
Nov 9 |
comment |
SQL Server Mirror failover on failing storage Makes sense! However, getting all databases on separate storage isn't a solution for me in this case, since the problem originally was on a system with 2 storage subsystems, one for log and one for data. I will put this in my report for this customer though! |
|
Nov 9 |
comment |
SQL Server Mirror failover on failing storage The corrupt database was on SQL-01, that's why the failover was initiated. The tempdb on SQL-02 doesn't seem to get corrupted thought when i disable the storage |
|
Nov 8 |
comment |
SQL Server Mirror failover on failing storage @Stuart your answer can be somewhat of a solution for my problem. Using mulitple storage devices per instance, where each database will have it;s own storage subsystem. Bit expensive though.... |
|
Nov 8 |
revised |
SQL Server Mirror failover on failing storage edit |
|
Nov 8 |
comment |
SQL Server Mirror failover on failing storage Yes, following that blogpost. All the DB's are on the same drive. Strange, failover from sql-01 to sql-02 works when i disable the storage for sql-01, but back from sql-02 to sql-01 isn't working now. I really don't understand why. Also, this failover will be done after 30 seconds or something round that... |
|
Nov 8 |
comment |
SQL Server Mirror failover on failing storage Yeah, manually failovering works. That is also exactly what i want to do in this particulair case, but with the use of a WMI Alert / SQL Agent job. The errors i see are only related to not having storage ("The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000000130000 in file 'e:\MSSQL\Data\MirrorTest1.mdf'"). But that is when i try to query a certain table on that database on the server where the storage is down. |
|
Nov 8 |
awarded | Editor |
|
Nov 8 |
revised |
SQL Server Mirror failover on failing storage added witness in HS mode |
