611 reputation
410
bio website foxtricks.com
location Belgium
age 38
visits member for 2 years, 11 months
seen yesterday

All round developer working as Software Architect for a Software company building a Backoffice solution for Banks for Risk, Accounting and MIS.

I'm mainly interested in SqlServer performance tuning, Developing C# Server side software and general Software Development best practices. (And a bit of Finance on the side)

https://github.com/FilipDeVos

http://foxtricks.com


Oct
20
comment Performance first low, then high after adding index, then keep high after drop index
use RESET QUERY CACHE for that purpose
Oct
20
comment Performance first low, then high after adding index, then keep high after drop index
Adding an index will only perform better if it is being used. Add the index and then check the query plan. If the stats are up to date and the query optimizer elects to use it there is a big chance it will improve performance. Removing statistics has no use as it will result most likely in a suboptimal query plan.
Oct
17
revised Performance first low, then high after adding index, then keep high after drop index
added 131 characters in body
Oct
17
comment Performance first low, then high after adding index, then keep high after drop index
yes, the performance improvement probably comes from having up to date statistics which trigger a better execution plan.
Oct
17
answered Performance first low, then high after adding index, then keep high after drop index
Oct
14
answered How to alter/migrate the schema of a table with tons of records
Oct
14
comment Best way to get time zone key name from SQL Server
Reading the reg key with this or SQLCLR is the only correct way I know (I personally would create a job which updates a table instead of enabling xp_regread though.). All other systems with offset etc are giving incorrect results.
Oct
14
answered Why can't I obtain OBJECT_NAME() for a temporary table?
Oct
14
revised Run multiple stored procedures in sequence
changed procname field to 513 chars to support fully qualified names
Oct
14
comment Run multiple stored procedures in sequence
good catch on the procname length, I forgot about fully qualified names.
Oct
14
comment Run multiple stored procedures in sequence
I was lazy, my apologies. ;)
Oct
14
revised Run multiple stored procedures in sequence
fixed second example up a bit
Oct
14
comment Run multiple stored procedures in sequence
I understood from the comment that the return value should be examined, not the error code. I added 3 example procs, when you run you will see that the 3rd proc is not executed and the 'do cleanup' is printed.
Oct
14
revised Run multiple stored procedures in sequence
added 195 characters in body
Oct
14
comment Run multiple stored procedures in sequence
I don't. The dynamic sql contains exec @result = proc1. The output param serves to lift the @result value outside the dynamic sql scope.
Oct
14
revised Run multiple stored procedures in sequence
renamed statement to batch
Oct
14
comment Run multiple stored procedures in sequence
print the @sql statement and check what it does. The output param is only used to pick up the return value for the cleanup step later on.
Oct
14
answered Run multiple stored procedures in sequence
Nov
30
awarded  Yearling
May
14
awarded  Caucus