Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There is an entire MSDN chapter on the subject: <a href="http://msdn.microsoft.com/en-us/library/ms187445" rel="nofollow">Estimating the Size of a Database</a>. It is important to know how many non-clustered indexes you need (are you going to seek data one any of those 'code' column?) and what is the clustered index key. Each subject has, again, a topic on MSDN:</p> <ul> <li><a href="http://msdn.microsoft.com/en-us/library/ms178085" rel="nofollow">Estimate the Size of a Clustered Index</a></li> <li><a href="http://msdn.microsoft.com/en-us/library/ms190620" rel="nofollow">Estimate the Size of a Nonclustered Index</a></li> </ul> <p>Additionally you can deploy <a href="http://msdn.microsoft.com/en-us/library/cc280576" rel="nofollow">Row Compression</a> or <a href="http://msdn.microsoft.com/en-us/library/cc280464" rel="nofollow">Page Compression</a> to reduce the size of your table(s). And if you opt for Unicode columsn you can also enable <a href="http://msdn.microsoft.com/en-us/library/ee240835" rel="nofollow">Unicode Compression</a>.</p> <p>Your performance requirements will be driven mostly by your load (ie. your queries). You did not specify anything about how are you going to query the the database (ranges? aggregates, singleton lookups?, BI?) and how is the database updated (read-only?, ETL?, OLTP?). There are tipc on how to <a href="http://msdn.microsoft.com/en-us/library/ms189081" rel="nofollow">Monitor and Tune for Performance</a> but more important is to design your application for performance. There are many details, eg. read <a href="http://msdn.microsoft.com/en-us/magazine/ee236412.aspx" rel="nofollow">How Data Access Code Affects Database Performance</a> but, by a large margin, the most important task is to tune your data model (the layout of tables and indexes) to your access pattern (how are you going to query the database).</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to estimate server size requirements for SQL Server database?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRemus Rusanu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHi Remus, thank you for that very helpful answer, I will read diligently. I haven't learned enough about databases yet it seems! My second worry as you mentioned is the load from queries, there could be thousands of queries happening from users at the same time. I am going to use this grid: http://demos.telerik.com/aspnet-ajax/grid/examples/programming/filteringtemplatecolumns/defaultcs.aspx and it is my understanding that the filtering uses a paging method for queries.
      singulars
      1. PO
      1. USuser1166981
    2. COThe benchmarks for 300,000 rows per this demo: http://demos.telerik.com/aspnet-ajax/grid/examples/performance/linq/defaultcs.aspx is a little over a second to search for data in one column. Do you know whether you can estimate how large the response times could get under certain simultaneous searches based on these stats alone if you know the specs of the server?
      singulars
      1. PO
      1. USuser1166981
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload