all groups > sql server (alternate) > april 2005 >
You're in the

sql server (alternate)

group:

Splitting of database


Splitting of database Tommy.Vincent NO[at]SPAM gmail.com
4/29/2005 1:16:51 AM
sql server (alternate):
hi
I am new to SQL.I have database of 30GB.I have just heard about
spliting Databases which helps in Performance.So please can any one
guide me in what are the steps involved in it.
Anxious to know How does it work if i split my database in two
different location.
We are using SQl 2000.
Operating System - Windows 2000 server

regards
Re: Splitting of database robin9876 NO[at]SPAM hotmail.com
4/29/2005 1:27:37 AM
It depends on the database usage and growth, as there are two options
or a combination of both of these.
One where you can have multiple files and the data is spread across
these. The other option is to have different files for larger tables,
heavily accessed tables and/or non clustered indexes.
Re: Splitting of database Simon Hayes
4/29/2005 3:00:08 AM
If you mean physically splitting the database, then you can use disk
solutions like NAS or SAN to spread the databases across many disk -
this is normally invisible to SQL Server. Within MSSQL itself, you can
use filegroups to do more or less the same thing.

At the logical level, you can partition data across different databases
- see "Using Partitioned Views" and "Federated SQL Server 2000 Servers"
in Books Online for more details.

Having said all that, 30GB is not a big database, so if you're having
performance problems there are probably better things to look at first
- use Profiler to identify long-running queries, the Index Tuning
Wizard to get ideas on improving your indexes etc.

If you can give some more details of what your performance problem is,
someone may be able to make a suggestion. But often performance
problems can't be easily solved in a newsgroup, because you need to do
a lot of monitoring and tracing to help identify the issue.

Simon
AddThis Social Bookmark Button