As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
What are the features that are not available in T-SQL however, they are part of SQL standard. Also, If someone can list nice features that are available in PL/SQL (ORACLE) not currently available in T-SQL (e.g. LAG and LEAD etc.) I know Denali will introduce some of those (like lag and lead) but not sure?
I know there are features (some of those are indeed nice e.g. TOP) available in T-SQL but not part of SQL Standard. I just want to find other side of story.
There really isn't a SQL "standard". However you can get O'Reilly SQL Pocket Guide, it has most of the primary differences between the SQL dialects and is well worth the 15 dollars to get. There are many small differences in between TSQL and Oracle. Too many to list here.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Im trying to understand more about SQL injection, I know how it works and how to protect against it, but I just have a few questions.
What are typical 'programming' sources of vulnerability to SQL injection exploit?
What are typical 'system' and coding mechanisms that can be used to protect against SQL injection?
I would appreciate straight answers not links as I dont find them useful.
Thank you
Sources:
Not validating your input types.
Concatenating Strings with inputs directly.
Not using PreparedStatements to guarantee that only one instruction is executed.
Solutions:
Use prepared statements.
Validate input types (may be redundant if above point is used correctly).
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Can anybody recommend me an SQL documentation tool that I can:
document SQL Server databases;
add comments to generate descriptions of tables, views, stored procedures, functions and their columns, fields and parameters.
Thank you!
Basically two valid contenders, for SQL Server, in my opinion:
Red-Gate SQL Doc
See their online AdventureWorks sample to get an impression of what those docs look like
ApexSQL ApexSQL Doc
Sybase Power Designer, Oracle SQL developer data modeler (it looks strange but it could create data model for mssql)
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am creating a database and I need to create some tables.
I would like to know which software do you use or recommend (preferably free) to generate SQL code from ER diagram.
Not free, but effective: Microsoft Visio.
It has a nice template for ER diagrams complete with relationships, primary key information, etc. I believe that it can both generate the schema in the database as well as create the diagram by pointing it at a database.
We've used Case Studio 2 for years to model a fairly complex schema - it's pretty good. We use it to create scripts for MySQL, Oracle and SQL Server. It is now called Toad Data Modeller: https://www.quest.com/products/toad-data-modeler/ There's a freeware version (not sure how this differs from the paid-for licenced version though)
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I got following question on an interview:
Which SQL mechanisms allow user to browse tables sequentially?
Cursor is a good example - but I don't think you could really argue that Cursors are truely a part of SQL - rather they just tend to come bolted in with procedural languages used on database servers - like pl/SQL and T-SQL.
You could also make an argument for Recordsets, Dynasets, DataTables and DataViews, but those aren't part of SQL itself either.
They might be referring to ORDER BY with a sequential field on the table, but if so, they've not phrased their question very well...
Martin.
"CURSOR" might be the word that you should google for.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
What are the differences between MySQL and Sql server?
What are the parameter to chose between the two?
Several questions here related to DB comparisons of various flavors:
What are the major differences between databases?
https://stackoverflow.com/questions/404776/why-isnt-postgresql-as-widespread-as-mysql
Where to find a good reference when choosing a database?
postgresSQL mysql oracle differences
The paramater to choose between the two is the price tag. How much do you "expect" to pay for your database. If its zero then MySQL is probably good enough for you, if its 10k then SQL Server is probably good enough for you.
As for the actual differences, there are too many to list.