Solved

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

Posted on 2013-01-28
3
333 Views
Last Modified: 2013-01-28
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
Comment
Question by:dmaclean2
  • 2
3 Comments
 

Author Comment

by:dmaclean2
ID: 38829882
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
 
LVL 15

Accepted Solution

by:
Eyal earned 500 total points
ID: 38829901
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
 

Author Closing Comment

by:dmaclean2
ID: 38830056
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

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

Everyone has problem when going to load data into Data warehouse (EDW). They all need to confirm that data quality is good but they don't no how to proceed. Microsoft has provided new task within SSIS 2008 called "Data Profiler Task". It solve th…
Entering time in Microsoft Access can be difficult. An input mask often bothers users more than helping them and won't catch all typing errors. This article shows how to create a textbox for 24-hour time input with full validation politely catching …
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
Via a live example, show how to extract insert data into a SQL Server database table using the Import/Export option and Bulk Insert.

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now