121 reputation
2
bio website
location
age
visits member for 1 year, 5 months
seen Mar 14 at 1:19

Incredibly handsome


Apr
13
comment Can't connect SQL Server through firewall
Have you verified, on the server, what port the SQL Server is listening on?
Apr
18
awarded  Teacher
Apr
18
answered Executing Child packages without using master package
Apr
17
answered How can I convert an Oracle dump file into SQL Server?
Apr
16
comment How can I convert an Oracle dump file into SQL Server?
You should consider a different way of transferring this data as you will never find a tool that can do this.
Apr
16
comment How can I convert an Oracle dump file into SQL Server?
I am fairly certain this is totally impossible.
Feb
15
awarded  Supporter
Feb
14
comment How can I make sure the SQL Server query optimizer uses the exact tables in the query
I must ask.. WHY don't you want to use use the indexed view result? Surely performance is superior? Is it giving you the wrong result - it shouldn't be.
Nov
6
comment Performance Tuning for Huge Table (SQL Server 2008 R2)
and please... look into columnstores as suggested!
Nov
6
comment Performance Tuning for Huge Table (SQL Server 2008 R2)
But I don't suggest that you go creating multiple indexed views to speed things up - you'll run out of time and disk space eventually. It might just be one thing to put in your arsenal.
Nov
6
comment Performance Tuning for Huge Table (SQL Server 2008 R2)
If your existing query takes 5-10 minutes, then the indexed view will take 5-10 minutes. When complete, when you run the same query it will come back as though it's coming out of a table (i.e. immediately). An indexed view pre-runs a particular bit of SQL. If you submit SQL that matches it, it takes it from the indexed view, rather than running it all over again. The major advantage of an indexed view is that you don't need to change your existing queries, they will automatically use it. The disadvantage is you pretty much have to create one for a few different combinations.
Nov
6
answered Performance Tuning for Huge Table (SQL Server 2008 R2)