Showing posts with label selecting. Show all posts
Showing posts with label selecting. Show all posts

Monday, March 26, 2012

Pratical size of a SQL Server database

Hi,
We are in the process of selecting a database for a data warehouse type
application. I want to get a feel for how big can a SQL Server database
get. As per Microsoft, it can be multiple terabytes. Can you tell me

What is the biggest size SQL server database you manage? (I understand
big is a relative term. I consider 500+ Gig as big).
Do you see any major performance problems due to size of the database?
(Given that the database is designed optimally).
Really appreciate your help.
Thanks,
JosephHave you seen:
http://www.microsoft.com/sql/techin...scalability.asp

Performance is determined by many factors other than database size. With the
right implementation SQLServer can of course scale to many terabytes.

--
David Portas
SQL Server MVP
--|||<josil20@.gmail.com> wrote in message
news:1103039384.280547.157360@.f14g2000cwb.googlegr oups.com...
> Hi,
> We are in the process of selecting a database for a data warehouse type
> application. I want to get a feel for how big can a SQL Server database
> get. As per Microsoft, it can be multiple terabytes. Can you tell me
> What is the biggest size SQL server database you manage? (I understand
> big is a relative term. I consider 500+ Gig as big).

Biggest I manage is 37 Gig. And I don't consider that all that big.

> Do you see any major performance problems due to size of the database?

No. Generally major performance problems are due to design and code, not DB
size.

The bigger issues are things like disaster recovery. DR for a 1 gig DB that
needs to be available 9-5 is far easier than a 500GB that has to be 24x&.

> (Given that the database is designed optimally).
> Really appreciate your help.
> Thanks,
> Joseph|||I think the answer depends on your server and network environment. The
biggest "database" I work with has 60 gigs of data per calendar year.
There is a separate database for each calendar year. We keep 5 years
worth of data on-line. Why separate databases? It's easier to reindex
an entire database than only a portion of one. It's also easier to
backup and restore an entire database than only a portion of one.

Suppose you have a 500 gig database. Some questions you need to ask:
a) how long does it take to back up
b) how long does it take to reindex
c) how long does it take to mount it from tape
d) how long does it take to move/copy the backup and data files across
your network
e) how long does it take to restore

There are companies like ScalabilityExperts.com who can set-up a
multiple Tbyte database for you. Being mere mortals, we just break
them out into smaller databases.sql

Wednesday, March 21, 2012

PostBack while selecting a parameter

Hi,

I'm working on a report having 2 date parameters(which uses calendar control) and a dropdownlist. But on selecting each of these parameters, the page refreshes. For eg On selecting a date from the calendar control results in a postback. The same is the case with the dropdownlist. Could you please help to resolve this issue? We need the postback to happen only on clicking the 'View Report' button.

Also, is there any way to customize the 'View Report' button. It always appears in the right hand side. Can we set the position of this button so that it appears just below the paging button?

Thanks in advance,

Sonu.

1. No, it's not possible to avoid postbacks when you enter parameters one by one.

2. There is no way to customize the position of the button but you can change the style of the button in your report manager by using the ReportingServices.css file in the following folder (probably):

C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportManager\Styles

Please refer to more details in the following link:

http://msdn2.microsoft.com/en-us/library/ms345247.aspx

Shyam

sql