network profile
| bio | website | |
|---|---|---|
| location | Germany | |
| age | ||
| visits | member for | 2 years, 1 month |
| seen | 12 hours ago | |
| stats | profile views | 11 |
|
Jun 14 |
answered | How to group by when querying duplicate records? |
|
May 31 |
comment |
Are there major drawbacks/risk of using oracle blob to store files If there is no need for transactional support then let your filesystem do the job it was build for. Additionally you add a meta information file if you need to handle inconsistency later. The major drawback with blobs is a significant increase of your database backup/restore time. |
|
May 30 |
comment |
What are reasonable options for an in-memory multi-core database? Postgres in a ramdisk could even be slower. Your data is in the ramdisk (RAM) and when you query this data it is also in OS memory buffer (RAM). I don't think this would make things faster. |
|
May 30 |
comment |
Run query faster, what index to use Can you upgrade to postgres 9.2? This version can use index-only scans wiki.postgresql.org/wiki/Index-only_scans |
|
May 30 |
comment |
Why Hypertable is not supporting joins and Transaction? You can also read this. dba.stackexchange.com/questions/34892/… |
|
May 29 |
comment |
Are there major drawbacks/risk of using oracle blob to store files Do you need transactional support for this blobs? |
|
May 29 |
comment |
Handle vast amount of data in DB sql server...If you have to do some aggregation analyses over very large sequential datasets then you can store the results on a daily base to a other table. And this result can be aggregated again if need a result for the whole month etc. |
|
May 29 |
answered | Handle vast amount of data in DB |
|
May 29 |
awarded | Commentator |
|
May 29 |
comment |
Load Balancing in SQL code.msdn.microsoft.com/Cloud-Fundamentals-in-1a3ab1bd |
|
May 29 |
answered | The UPDATE permission was denied on the object |
|
May 29 |
awarded | Critic |
|
May 21 |
awarded | Constituent |
|
May 21 |
awarded | Caucus |
|
Feb 22 |
comment |
Update to session table slowcache will create contention issues I think this depends on your workload and is not generally true. My server runs with a query_cache_size=2048M and 6 cores a lot faster than without caching. |
|
Feb 22 |
comment |
Update to session table slow I bet an SELECT and UPDATE on jos_session is done on every page view. Followed by a DELETE all where time is lesser than NOW() minus some time. |
|
Feb 21 |
comment |
Update to session table slowHow can I improve the speed of these queries? Can you also provide the queries which you want to improve? |
|
Feb 21 |
answered | Does MYSQL join before LIMIT? |
|
Nov 23 |
comment |
What is Better SQL Server Configuration? ou don't need a seperate raid for the LDF, if your database is rarely updated. All other suggestions would depend on your data and usage, but you don't provide any informations. |
|
Nov 22 |
awarded | Custodian |
