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.
This article claims that by running a sql script in unix, it can perform 20x faster?
How can this be possible?
This looks like the author is comparing Apples to Oranges (no that's too similar, how about Apples to Aliens). The performance they speak of comes form the result set being displayed in a browser (as a table)
instead of waiting for hours for Brio or Toad to return results in a
browser (with a crash if the number of rows being returned was above
50,000)
As compared to the result set being displayed in a text file (who is to say that a text editor won't crash as well?)
then export to the Unix station) and produced as output the results of
the query (tab-separated text file)
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.
I have a column that holds a password..i want to do is simply mask the password with the standard password character (*) or Simply hide...
Thanks in advance....
LOL, This is not possible. You can't modify the way Management Studio shows a table!
However, usually, you don't store passwords in DDBB, but the hash.
See this:
http://geekswithblogs.net/hroggero/archive/2009/09/19/strong-password-hashing-with-sql-server.aspx
You have to use the Hashing Method,read this article (specific to MySQL)
http://dev.mysql.com/doc/refman/5.1/en/password-hashing.html
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.
i have a few thousand rows of data and i'm connecting to the db via VPN.
retreiving data over VPN is pretty slow and i'm looking for ways to
improve performance. is pagination of results a good way to go?
It always depends on how you are using pagination. If you are returning all the data and only displaying 10 rows at a time on the client then it would not change anything. If you are truly getting only 10 records at a time from the DB then it could help. However 1000's of rows should be nothing for any database platform or any network connection to provide. I would look into the query to ensure it is optimized.
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.
If I have a percenatge value (6%) what is the prefered way to store this in the database
Solution1: 6
Solution2: .06
And why would you choose it?
Go for solution 2, it makes any calculations you have to do on it easier.
if it is 6% of the total {total (100)}*{db value (0.06)} = 6
easy
This also handles if you are going to have part percentages 6.35% would be 0.0635 whereas if you stored it as an integer of 6 you could not have these part percentages. The only real drawback of doing this is if you want to output the value back to the client in readable format, you would need to multiply the database result by 100 before outputting the result.
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 choose the search engine for large project. Sunspot I liked, at least from the fact that we no need to run a cron job to reindex the data. But when I saw this http://www.vijedi.net/2010/ruby-full-text-search-performance-thinking-sphinx-vs-sunspot-solr/ I began to doubt.
It depends on user preference, so there's no straightforward answer. Maybe you could go through pros and cons of each one and decide for yourself?
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.