Click here to Skip to main content
15,884,353 members
Home / Discussions / Database
   

Database

 
GeneralRe: Database management Pin
PIEBALDconsult19-Jul-15 9:40
mvePIEBALDconsult19-Jul-15 9:40 
AnswerRe: Database management Pin
Richard MacCutchan19-Jul-15 22:00
mveRichard MacCutchan19-Jul-15 22:00 
AnswerRe: Database management Pin
Mycroft Holmes19-Jul-15 22:32
professionalMycroft Holmes19-Jul-15 22:32 
AnswerRe: Database management Pin
Wendelius20-Jul-15 6:50
mentorWendelius20-Jul-15 6:50 
QuestionDatabase management Pin
Otekpo Emmanuel19-Jul-15 9:38
Otekpo Emmanuel19-Jul-15 9:38 
QuestionRe: Database management Pin
ZurdoDev22-Jul-15 9:48
professionalZurdoDev22-Jul-15 9:48 
Questionlarge database Pin
V.16-Jul-15 21:46
professionalV.16-Jul-15 21:46 
AnswerRe: large database Pin
Wendelius16-Jul-15 22:03
mentorWendelius16-Jul-15 22:03 
With that amount of data, I take it you already know enough about indexing etc so let's not go to those.

Depending what problem you're solving the technique might be different. Based on your description I'd concentrate on partitioning the large table (or tables) first. Partitioning would help you to isolate the hot spot of the table to a significantly smaller amount of rows so that changes in indexes and on disk would affect a considerable smaller amount of data.

For more information have a look at http://www.postgresql.org/docs/9.1/static/ddl-partitioning.html[^]

As a side note, I hate to say this but I would also consider changing the database product Smile | :)
GeneralRe: large database Pin
V.16-Jul-15 22:10
professionalV.16-Jul-15 22:10 
GeneralRe: large database Pin
Wendelius16-Jul-15 22:20
mentorWendelius16-Jul-15 22:20 
GeneralRe: large database Pin
Mycroft Holmes17-Jul-15 14:02
professionalMycroft Holmes17-Jul-15 14:02 
GeneralRe: large database Pin
V.18-Jul-15 0:12
professionalV.18-Jul-15 0:12 
GeneralRe: large database Pin
Mycroft Holmes18-Jul-15 0:45
professionalMycroft Holmes18-Jul-15 0:45 
GeneralRe: large database Pin
V.18-Jul-15 8:25
professionalV.18-Jul-15 8:25 
GeneralRe: large database Pin
Jörgen Andersson20-Jul-15 11:01
professionalJörgen Andersson20-Jul-15 11:01 
AnswerRe: large database Pin
GuyThiebaut18-Jul-15 1:19
professionalGuyThiebaut18-Jul-15 1:19 
GeneralRe: large database Pin
V.18-Jul-15 8:23
professionalV.18-Jul-15 8:23 
GeneralRe: large database Pin
GuyThiebaut18-Jul-15 8:37
professionalGuyThiebaut18-Jul-15 8:37 
QuestionSQL Linq, updating multiple records Pin
jkirkerx15-Jul-15 10:50
professionaljkirkerx15-Jul-15 10:50 
QuestionSave value of PREPARE into a variable Pin
Jassim Rahma14-Jul-15 22:23
Jassim Rahma14-Jul-15 22:23 
AnswerRe: Save value of PREPARE into a variable Pin
Wendelius14-Jul-15 22:45
mentorWendelius14-Jul-15 22:45 
GeneralRe: Save value of PREPARE into a variable Pin
Jassim Rahma15-Jul-15 22:22
Jassim Rahma15-Jul-15 22:22 
GeneralRe: Save value of PREPARE into a variable Pin
Wendelius15-Jul-15 22:51
mentorWendelius15-Jul-15 22:51 
AnswerRe: Save value of PREPARE into a variable Pin
jschell15-Jul-15 10:45
jschell15-Jul-15 10:45 
QuestionSome help with SQL to Linq Conversions Pin
jkirkerx13-Jul-15 7:04
professionaljkirkerx13-Jul-15 7:04 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.