Default MS SQL server insert query start give me syntax error

Question

0.00/5 (No votes)

See more:

My database was running fine ,I made no changes to it and all of a sudden it started giving me errors in insert query such as

Msg 102, Level 15, State 1, Line 11
Incorrect syntax near '<'.

OR varchar is not recognized as build in function. This is what I get when I run a default query OR even when I create a new table , it just not work , do I need to install something ? Please help!
IT WAS WORKING FINE A FEW DAYS BACK
I HAVE ALSO INSTALL NEW VERSION OF DATABASE MAY BE THAT IS THE ISSUE?

USE [CMS]
GO

INSERT INTO [dbo].[userRegistration]
           ([userName]
           ,[userEmail]
           ,[userPassword]
           ,[userDesignation]
           ,[userPhone])
     VALUES
ERRORS start from this part. 
           (<userName, varchar(50),>
           ,<userEmail, varchar(50),>
           ,<userPassword, varchar(50),>
           ,<userDesignation, varchar(50),>
           ,<userPhone, varchar(50),>)
GO

What I have tried:

I have done a lot of research but all of the articles advise to fix the query, do note that this is a default MS sql server query I DID NOT WRITE THIS

Posted 1-May-21 14:55pm

Asfand May2021

Updated 1-May-21 19:34pm

Add a Solution

Comments

David Crow 1-May-21 23:42pm

I'm guessing there are mismatched angle brackets.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2021-05-01T19:34:00

Simple: get rid of the '<' and '>' characters and the datatypes:

SQL

INSERT INTO [dbo].[userRegistration]
           ([userName]
           ,[userEmail]
           ,[userPassword]
           ,[userDesignation]
           ,[userPhone])
     VALUES
           (valueForName
           ,valueForEmail
           ,valueForPassword
           ,valueForDesignation
           ,valueForPhone)

And do yourself a favour ... Never store passwords in clear text - it is a major security risk. There is some information on how to do it here: Password Storage: How to do it.[^]

And remember: if you have any European Union users then GDPR applies and that means you need to handle passwords as sensitive data and store them in a safe and secure manner. Text is neither of those and the fines can be .... um ... outstanding. In December 2018 a German company received a relatively low fine of €20,000 for just that.