97 reputation
6
bio website
location
age
visits member for 2 years, 9 months
seen Mar 31 at 20:55

Mar
31
comment Comparing CLR Functions in Visual Studio SSDT
I'm able to get the compare working by moving all the code to one project. This isn't what I was hoping to do, but I think it will be our best option until this is fixed.
Mar
27
comment Comparing CLR Functions in Visual Studio SSDT
I looked in the Model.xml file and these properties are not defined there. They are in the C# code: [SqlFunction(IsDeterministic = true, DataAccess = DataAccessKind.None)]
Mar
26
asked Comparing CLR Functions in Visual Studio SSDT
Aug
5
accepted Changing autogrow settings with database mirroring
Aug
5
answered Changing autogrow settings with database mirroring
Jul
31
comment Changing autogrow settings with database mirroring
I guess that is the route I'll be going down. I'm just glad I discovered this before we actually grew a file by 30,000% :)
Jul
31
awarded  Commentator
Jul
31
revised Changing autogrow settings with database mirroring
added 260 characters in body
Jul
31
comment Changing autogrow settings with database mirroring
Interesting- those two issues are the same failure mode, just triggered by different events (attaching a database, rebooting a server, failing over a mirrored database).
Jul
31
revised Changing autogrow settings with database mirroring
added 387 characters in body; edited title
Jul
31
asked Changing autogrow settings with database mirroring
Jul
1
comment What does the wait type PREEMPTIVE_XE_CALLBACKEXECUTE mean?
Yeah, the most descriptive piece of info I found was is this blog post: blogs.msdn.com/b/psssql/archive/2009/11/03/… It says more info coming in 2010 :(
Jul
1
accepted What does the wait type PREEMPTIVE_XE_CALLBACKEXECUTE mean?
Jul
1
comment What does the wait type PREEMPTIVE_XE_CALLBACKEXECUTE mean?
I'm guessing I won't get any info on that wait type, but this info is more useful anyway. Thanks!
Jul
1
asked What does the wait type PREEMPTIVE_XE_CALLBACKEXECUTE mean?
Jul
31
awarded  Popular Question
Oct
5
revised Code creates different plan when ran ad-hoc vs. in a stored procedure
added 91 characters in body
Oct
4
accepted Code creates different plan when ran ad-hoc vs. in a stored procedure
Oct
4
revised Code creates different plan when ran ad-hoc vs. in a stored procedure
added 321 characters in body
Oct
4
comment Code creates different plan when ran ad-hoc vs. in a stored procedure
Regarding parameter sniffing: could this be the case even though the sp and the ad-hoc code was compiled with the same value?