Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 343
  • Last Modified:

Problem constructing a dynamic SQL statement - date and numeric parameters cause error; string parameters OK

The web application uses a set of Microsoft tables and stored procedures. In this case, I want to repeatedly invoke aspnet_Membership_CreateUser. I have a SELECT statement that provides the parameters to pass to that sp.
And I have a set of code modeled on one I found on the web that provides the logic to go through that recordset row by row and call the sp.

The problem is that the construction of the specific SQl statement to execute (@SQLExec) fails for the two date parameters, '@CurrentUTCDate' and '@CreatedDate'

Here is the error message for '@CurrentUTCDate'
Msg 241, Level 16, State 1, Line 33
Conversion failed when converting date and/or time from character string.

I have tried every combination of quotes I can think of and none of them work.

The attached file is a stripped-down duplicate of my current stored procedure.
Test-generate-membership-proc.sql
0
Douglass MacLean
Asked:
Douglass MacLean
  • 2
1 Solution
 
Douglass MacLeanCTOAuthor Commented:
As an added reference to my question, here are the parameters required by the stored procedure that I am trying to call
CREATE PROCEDURE [dbo].[aspnet_Membership_CreateUser]
    @ApplicationName                        nvarchar(256),
    @UserName                               nvarchar(256),
    @Password                               nvarchar(128),
    @PasswordSalt                           nvarchar(128),
    @Email                                  nvarchar(256),
    @PasswordQuestion                       nvarchar(256),
    @PasswordAnswer                         nvarchar(128),
    @IsApproved                             bit,
    @CurrentTimeUtc                         datetime,
    @CreateDate                             datetime = NULL,
    @UniqueEmail                            int      = 0,
    @PasswordFormat                         int      = 0,
    @UserId                                 uniqueidentifier OUTPUT
0
 
EyalCommented:
as it says: the format of the dates are invalid as dates. convert the string dates from the recordset to yyyyMMdd HH:nn and send them in this format to the SP
0
 
Douglass MacLeanCTOAuthor Commented:
Thanks. I lost sight of that fact that a SQL statement is, by definition, a character string. All non-character data (datetime, bit, float, etc.) needs to be converted to nvarchar.

Silly me.
Good you!
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now