Reputation
267
Top tag
Next privilege 300 Rep.
Create new tags
Badges
2 5 12
Impact
~42k people reached

  • 0 posts edited
  • 0 helpful flags
  • 6 votes cast
Dec
10
awarded  Famous Question
Sep
29
accepted ANSI_NULLS and QUOTED_IDENTIFIERS mismatch
Sep
27
asked ANSI_NULLS and QUOTED_IDENTIFIERS mismatch
Sep
5
awarded  Popular Question
Jun
2
awarded  Notable Question
May
28
awarded  Popular Question
Feb
20
awarded  Famous Question
Feb
17
awarded  Popular Question
Jul
2
awarded  Curious
Feb
12
awarded  Notable Question
Jan
15
awarded  Popular Question
Jan
9
awarded  Yearling
Nov
15
awarded  Notable Question
May
31
awarded  Popular Question
May
20
awarded  Caucus
May
20
awarded  Constituent
May
14
awarded  Popular Question
Nov
21
accepted One Complex Stored Procedure Causes Estimated Cost Exception
Nov
21
comment One Complex Stored Procedure Causes Estimated Cost Exception
That makes a lot of sense, thanks. I'm not surprised a setting like that requires a heavy permission.
Nov
21
comment One Complex Stored Procedure Causes Estimated Cost Exception
@MartinSmith It is a stored procedure that's responsible for setting up a yearly process, which has quite a few tables involved. I need the inserts all to be grouped together in a transaction; it needs to be in the same stored procedure. The process is run by a windows service, so however long it takes is not an issue (but it is fairly efficient as is). I just need it to run... I'm sending an email to the administrators to cover that end, but need to be aware of what to do if that doesn't work out. Thanks.