It's probably possible if you give users direct access to the SQL CLI prompt, but that's a very bad idea. What are you trying to accomplish, specifically? You should always take in input, make sure to sanitize it, and only then incorporate it into the SQL command and run that.
<a href="http://xkcd.com/327/">xkcd</a> has a humorous but real example of the huge security problems you introduce by not properly sanitizing input.
Last Wiki Answer Submitted: March 25, 2009 3:21 pm by YuvalShavit905 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
Microsoft SQL Server doesn’t provide a way to do this. All inputs have to be supplied by the user before the code is executed against the database. If you are using Oracle however it can prompt the user for input when using SQLPlus. (You didn’t specify the platform you are using)
What ever front end you are using should handle the input of data from the user. Let the database simply handle the data processing and storage.
Microsoft SQL Server doesn’t provide a way to do this. All inputs have to be supplied by the user before the code is executed against the database. If you are using Oracle however it can prompt the user for input when using SQLPlus. (You didn’t specify the platform you are using)
What ever front end you are using should handle the input of data from the user. Let the database simply handle the data processing and storage.