Showing posts with label clustered. Show all posts
Showing posts with label clustered. Show all posts

Sunday, March 11, 2012

custom path for data files

Hi,
I am about to install sql 2005 in a clustered scenario. I am reading the
installation notes and it says :
On the Cluster Group Selection page, select the group that contains the
drive you want to use for SQL Server from the Available Cluster Groups. The
selected cluster group is where the SQL Server virtual SQL Server resources
are placed. If you select the group containing the cluster quorum resource, a
warning is displayed recommending you do not install to the cluster quorum
resource. You can also specify a custom path for data files in the Data Files
field. To proceed, click Next.
My question is that I have two nodes both sharing D, E & QDrive if I select
the custom path option at this point in the installaion will I be able to
select D for databases and E for logs?
http://msdn2.microsoft.com/en-us/library/ms179530.aspx
Yes. You can add E: to the cluster group, make SQL dependent on it, and use
it for data or logs.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:99A9574F-1DDF-4741-8676-FC6EB36DFAFB@.microsoft.com...
> Hi,
> I am about to install sql 2005 in a clustered scenario. I am reading the
> installation notes and it says :
> On the Cluster Group Selection page, select the group that contains the
> drive you want to use for SQL Server from the Available Cluster Groups.
> The
> selected cluster group is where the SQL Server virtual SQL Server
> resources
> are placed. If you select the group containing the cluster quorum
> resource, a
> warning is displayed recommending you do not install to the cluster quorum
> resource. You can also specify a custom path for data files in the Data
> Files
> field. To proceed, click Next.
> My question is that I have two nodes both sharing D, E & QDrive if I
> select
> the custom path option at this point in the installaion will I be able to
> select D for databases and E for logs?
>
> http://msdn2.microsoft.com/en-us/library/ms179530.aspx
|||Hi Geoff,
Thanks for this but I'm new at this and a little confused.
I have:
cluster group containing Q
group 0 containing D Drive (I would like the data files here)
group 1 containing E Drive (I would like the log files here)
When I went through the setup I was expecting to have the choice of
splitting the files but could only chose one cluster group so I chose cluster
group 0.
Now when I opened management studio to change the logs location I can only
see D, adding the E Drive to group 0 also does not allow me to see E drive
from management studio.
What am I missing?
thanks in advance
I have now installed sql and at the point when asked
"Geoff N. Hiten" wrote:

> Yes. You can add E: to the cluster group, make SQL dependent on it, and use
> it for data or logs.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:99A9574F-1DDF-4741-8676-FC6EB36DFAFB@.microsoft.com...
>
|||You are missing dependency.
Using the Cluster admin tool, take the SQL Service offline but leave the
rest of the group online. Right-click the SQL Service... Properties.
Advanced tab. Add the new disk as an item the SQL Service is dependent on.
Bring SQL back online.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:1AB63836-C0CF-4228-A1DC-9D8F28AB63FA@.microsoft.com...[vbcol=seagreen]
> Hi Geoff,
> Thanks for this but I'm new at this and a little confused.
> I have:
> cluster group containing Q
> group 0 containing D Drive (I would like the data files here)
> group 1 containing E Drive (I would like the log files here)
> When I went through the setup I was expecting to have the choice of
> splitting the files but could only chose one cluster group so I chose
> cluster
> group 0.
> Now when I opened management studio to change the logs location I can only
> see D, adding the E Drive to group 0 also does not allow me to see E drive
> from management studio.
> What am I missing?
> thanks in advance
>
> I have now installed sql and at the point when asked
> "Geoff N. Hiten" wrote:

Tuesday, February 14, 2012

Custer an index or not?

I see this as potential problem. I have Indexed columns for a Clustered
Index as follows:
Merchant_Account_ID
DateOfReport
Standard_Entry_Class_Code
This would repage my index on the daily insert of say 300+ returns where
they are going in by Merchant + Data+ Code.
I am finding a few of these, not as many as I thought :)
I want to remove the clustered aspect of the index, and still leave it as
unique. This would increase my insert performance wouldn't it?
TIA> I want to remove the clustered aspect of the index, and still leave it as unique. This would
> increase my insert performance wouldn't it?
Likely. But insert performance will be even better if you can cluster on something which it
monotonically increasing (instead of finding free space using PFS and IAM pages, SQL Server just
navigates the index, find the "end of the table" and there the row goes). Perhaps DateOFReport is,
so you can specify this as the first column in the index?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"_Stephen" <srussell@.electracash.com> wrote in message news:uaNuXscTGHA.5856@.TK2MSFTNGP11.phx.gbl...
>I see this as potential problem. I have Indexed columns for a Clustered Index as follows:
> Merchant_Account_ID
> DateOfReport
> Standard_Entry_Class_Code
>
> This would repage my index on the daily insert of say 300+ returns where they are going in by
> Merchant + Data+ Code.
> I am finding a few of these, not as many as I thought :)
> I want to remove the clustered aspect of the index, and still leave it as unique. This would
> increase my insert performance wouldn't it?
> TIA
>|||yes, removing clustered indexes always increases speed for inserts, and
usually speeds up updates for the key fields.