G
Guest
Can someone offer some insight of why parameters outside of those contained
in a SqlDataSource <UpdateParameters> section would show up in a profiler
trace?
I'm using:
<UpdateParameters>
<asparameter Name="MerchID" Type="Int32" />
<asparameter Name="Merchant" Type="String" />
<asparameter Name="ModifiedBy" Type="String" />
</UpdateParameters>
In the SQL Server Profiler I see:
exec spu_merch
@Merchant=N'test',@ModifiedBy=N'jkayne',@MerchID=1,@ModifiedDate=''2006-02-28
12:35:46:917'',@EnteredDate=''2003-10-22 10:29:36:280''
I can't seem to figure out where ModifiedDate and EnteredDate are coming from.
These are optional in my stored procedure and I'd expect to see the folowing
in my profiler trace:
exec spu_merch @Merchant=N'test',@ModifiedBy=N'jkayne',@MerchID=1
Any insight would be extremely appreciated!
in a SqlDataSource <UpdateParameters> section would show up in a profiler
trace?
I'm using:
<UpdateParameters>
<asparameter Name="MerchID" Type="Int32" />
<asparameter Name="Merchant" Type="String" />
<asparameter Name="ModifiedBy" Type="String" />
</UpdateParameters>
In the SQL Server Profiler I see:
exec spu_merch
@Merchant=N'test',@ModifiedBy=N'jkayne',@MerchID=1,@ModifiedDate=''2006-02-28
12:35:46:917'',@EnteredDate=''2003-10-22 10:29:36:280''
I can't seem to figure out where ModifiedDate and EnteredDate are coming from.
These are optional in my stored procedure and I'd expect to see the folowing
in my profiler trace:
exec spu_merch @Merchant=N'test',@ModifiedBy=N'jkayne',@MerchID=1
Any insight would be extremely appreciated!