network profile
| bio | website | |
|---|---|---|
| location | ||
| age | 30 | |
| visits | member for | 11 months |
| seen | May 5 at 7:33 | |
| stats | profile views | 4 |
If you want to get in touch, you can find me at marcel.nita@gmail.com.
|
Mar 20 |
awarded | Critic |
|
Nov 26 |
awarded | Student |
|
Nov 26 |
awarded | Scholar |
|
Nov 26 |
accepted | Is a clustered index locked while a (clustered index) scan is in progress? |
|
Nov 26 |
comment |
Is a clustered index locked while a (clustered index) scan is in progress? Thanks! Should've mentioned that it's an implicit transaction. I'll give your suggestions a try and get back with some results. |
|
Nov 26 |
asked | Is a clustered index locked while a (clustered index) scan is in progress? |
|
Jul 10 |
awarded | Commentator |
|
Jul 10 |
comment |
SQL Server 2008 replication scenario Have you looked into merge replication? I think it's what you want. There's no bidirectional transactional replication, except the one with updateable subscriptions, but go for merge. More straightforwards. |
|
Jul 8 |
comment |
Rebuilding Indexes, DB now 10x the size @JeffBane: Can you add this info to your question, in a quote? I can't make out what's in there. |
|
Jul 8 |
answered | Rebuilding Indexes, DB now 10x the size |
|
Jul 7 |
comment |
Physical memory usage approaching 100%(96%) So SQL Server's private working set memory is low? |
|
Jul 4 |
comment |
SQL Server query slow when paginated @usr: touche! can we see the key lookup arguments (just hover over it). |
|
Jul 4 |
comment |
SQL Server query slow when paginated @vrs: yes, but since that particular index contains only the Name column, it also has to do a key lookup on the clustered index in order to retrieve the id. So including the ID in the non-clustered index should remove the key lookup operator. |
|
Jul 4 |
comment |
SQL Server query slow when paginated @vrs: Actually, let me wait for the new query plan. I take back what I said :) (about it being better). |
|
Jul 4 |
comment |
SQL Server query slow when paginated @Lamak: I think the paging breaks it, not the ORDER BY. Never used the 2012 paging myself, but the query plan indicates towards this. |
|
Jul 4 |
comment |
SQL Server query slow when paginated @vrs: Then please include the id column in the IX_PersonSearch index and make another test. Should be far better now. |
|
Jul 4 |
comment |
SQL Server query slow when paginated On what columns is index IX_PersonSearch... made? You're getting a key lookup because you're selecting * from the table and the used index does not contain all the output columns. I think you should select only the columns you need and then include them in the non-clustered index as included columns, not index columns. |
|
Jun 25 |
comment |
When should indexes be dropped and recreated? I wish this applied in my case too. On a slightly over 1TB database running on a production environment, I can barely afford to do a nightly non-clustered index rebuild for several tables with over 500 mil. rows. I have several ETL processes running each night and the last step I do from 3:00 AM is to rebuild indexes. |
|
Jun 25 |
awarded | Supporter |
|
Jun 25 |
awarded | Teacher |
