network profile
| bio | website | devexpp.blogspot.com |
|---|---|---|
| location | Brazil | |
| age | 22 | |
| visits | member for | 1 year, 10 months |
| seen | Jan 16 at 10:20 | |
| stats | profile views | 3 |
Just another developer...
|
Jan 16 |
awarded | Critic |
|
Oct 30 |
awarded | Popular Question |
|
Sep 6 |
accepted | Usage of SQL Server 2008 R2 Express. Please Advise |
|
Sep 5 |
asked | Usage of SQL Server 2008 R2 Express. Please Advise |
|
Jul 1 |
comment |
SQL Select taking too much time to execute It didn't. I can't figure out why it doesn't. It has the exact column in the Where clause for the subselect. Should I also include the selected column in it, because I don't remember trying it. (which is the primary key) |
|
Jun 30 |
comment |
SQL Select taking too much time to execute I see. I only changed the server, the database is the same, with the same Indexes. Still, it doesn't seem to automatically chose to use my Indexes. It does exactly what you said: a Table Scan. |
|
Jun 29 |
awarded | Scholar |
|
Jun 29 |
awarded | Supporter |
|
Jun 29 |
awarded | Editor |
|
Jun 29 |
accepted | SQL Select taking too much time to execute |
|
Jun 29 |
revised |
SQL Select taking too much time to execute Added solution |
|
Jun 29 |
comment |
SQL Select taking too much time to execute I can't change that left join to Inner join, it would screw the results, it's a business rule: the second table not necessarily has to have a related record. Also, the column in the WHERE clause doesn't accept null values. |
|
Jun 29 |
awarded | Autobiographer |
|
Jun 29 |
awarded | Student |
|
Jun 28 |
asked | SQL Select taking too much time to execute |
