Lowering priority: maintainence

Showing posts with label maintainence. Show all posts

Monday, March 26, 2012

Friday, March 23, 2012

After I run the maintainence plan, check db index...
the log will grow up from zero size to 20 GB size.
i know how to truncate
but the point is why it grow so large.
is it any problems?I assume that the maint plan includes DBCC DBREINDEX. This will rebuild all your indexes and those
rebuilds are logged to the transaction log. I suggest you read this articles regarding reindexing:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"inamori" <test@.test.com> wrote in message news:cqt9t7$s003@.imsp212.netvigator.com...
> After I run the maintainence plan, check db index...
> the log will grow up from zero size to 20 GB size.
> i know how to truncate
> but the point is why it grow so large.
> is it any problems?
>|||how about the data file
i shrink the data file from 30Gb to 15GB
after 3 hours, it grow up suddenly
can u tell me why?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> ¦b¶l¥ó
news:eENS$uX7EHA.2032@.tk2msftngp13.phx.gbl ¤¤¼¶¼g...
> I assume that the maint plan includes DBCC DBREINDEX. This will rebuild
all your indexes and those
> rebuilds are logged to the transaction log. I suggest you read this
articles regarding reindexing:
>
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "inamori" <test@.test.com> wrote in message
news:cqt9t7$s003@.imsp212.netvigator.com...
> > After I run the maintainence plan, check db index...
> >
> > the log will grow up from zero size to 20 GB size.
> >
> > i know how to truncate
> >
> > but the point is why it grow so large.
> >
> > is it any problems?
> >
> >
>|||What actions did you perform during those three hours?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"inamori" <test@.test.com> wrote in message news:cqucqh$pvv1@.imsp212.netvigator.com...
> how about the data file
> i shrink the data file from 30Gb to 15GB
> after 3 hours, it grow up suddenly
> can u tell me why?
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> ¦b¶l¥ó
> news:eENS$uX7EHA.2032@.tk2msftngp13.phx.gbl ¤¤¼¶¼g...
>> I assume that the maint plan includes DBCC DBREINDEX. This will rebuild
> all your indexes and those
>> rebuilds are logged to the transaction log. I suggest you read this
> articles regarding reindexing:
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> http://www.sqlug.se/
>>
>> "inamori" <test@.test.com> wrote in message
> news:cqt9t7$s003@.imsp212.netvigator.com...
>> > After I run the maintainence plan, check db index...
>> >
>> > the log will grow up from zero size to 20 GB size.
>> >
>> > i know how to truncate
>> >
>> > but the point is why it grow so large.
>> >
>> > is it any problems?
>> >
>> >
>>
>|||just do truncate and compress the data file
lets say
15GB used + 15 Free space
after i trucncate, 15 free space deleted
that mean 15 GB currently
but dont know why
3 hours later, 15 GB free sapce come out again
that mean grow back 30GB(15GB free + 15 used)
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23dSKeWb7EHA.3644@.TK2MSFTNGP09.phx.gbl...
> What actions did you perform during those three hours?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "inamori" <test@.test.com> wrote in message
news:cqucqh$pvv1@.imsp212.netvigator.com...
> > how about the data file
> >
> > i shrink the data file from 30Gb to 15GB
> >
> > after 3 hours, it grow up suddenly
> >
> > can u tell me why?
> >
> >
> > "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> ¦b¶l
¥ó
> > news:eENS$uX7EHA.2032@.tk2msftngp13.phx.gbl ¤¤¼¶¼g...
> >> I assume that the maint plan includes DBCC DBREINDEX. This will rebuild
> > all your indexes and those
> >> rebuilds are logged to the transaction log. I suggest you read this
> > articles regarding reindexing:
> >>
> >
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> http://www.sqlug.se/
> >>
> >>
> >> "inamori" <test@.test.com> wrote in message
> > news:cqt9t7$s003@.imsp212.netvigator.com...
> >> > After I run the maintainence plan, check db index...
> >> >
> >> > the log will grow up from zero size to 20 GB size.
> >> >
> >> > i know how to truncate
> >> >
> >> > but the point is why it grow so large.
> >> >
> >> > is it any problems?
> >> >
> >> >
> >>
> >>
> >
> >
>|||SQL Server doesn't grow the database files by itself. You need to find out what commands were
executed during these three hours that causes the database file size to grow. My guess is that you
are doing a DBREINDEX during this time period.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Test" <TEst@.test.com> wrote in message news:es1Jo4g7EHA.2572@.tk2msftngp13.phx.gbl...
> just do truncate and compress the data file
> lets say
> 15GB used + 15 Free space
> after i trucncate, 15 free space deleted
> that mean 15 GB currently
> but dont know why
> 3 hours later, 15 GB free sapce come out again
> that mean grow back 30GB(15GB free + 15 used)
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:%23dSKeWb7EHA.3644@.TK2MSFTNGP09.phx.gbl...
>> What actions did you perform during those three hours?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> http://www.sqlug.se/
>>
>> "inamori" <test@.test.com> wrote in message
> news:cqucqh$pvv1@.imsp212.netvigator.com...
>> > how about the data file
>> >
>> > i shrink the data file from 30Gb to 15GB
>> >
>> > after 3 hours, it grow up suddenly
>> >
>> > can u tell me why?
>> >
>> >
>> > "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> ¦b¶l
> ¥ó
>> > news:eENS$uX7EHA.2032@.tk2msftngp13.phx.gbl ¤¤¼¶¼g...
>> >> I assume that the maint plan includes DBCC DBREINDEX. This will rebuild
>> > all your indexes and those
>> >> rebuilds are logged to the transaction log. I suggest you read this
>> > articles regarding reindexing:
>> >>
>> >
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://www.solidqualitylearning.com/
>> >> http://www.sqlug.se/
>> >>
>> >>
>> >> "inamori" <test@.test.com> wrote in message
>> > news:cqt9t7$s003@.imsp212.netvigator.com...
>> >> > After I run the maintainence plan, check db index...
>> >> >
>> >> > the log will grow up from zero size to 20 GB size.
>> >> >
>> >> > i know how to truncate
>> >> >
>> >> > but the point is why it grow so large.
>> >> >
>> >> > is it any problems?
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>

Monday, March 19, 2012

Maintainence of Replication

Hi Dear...

I have some questions regarding replication in SQL Server 2005.

1. Is it neccessary to have same schema on each side i.e on subsicriber and on publisher?

2. Do replication helps me to replicate the changed schema (of published articals) to the subscribers?

3. If a UDT is defined on publisher and one of its dependent is selected for publication do i need to define the UDT on subscriber manually or it will automatically done for me?

4. pls anyone who can give me the detail known issues and their alternative solutions in regard of maintainence of Replication.

Regards

Mubashar Ahmad

1. Subscriber can have a either the full table, a portion of the table or not at all. You cannot replicate to a totally different schema though.

2. Yes it will replicate ALTER statements.

3. I think you have to do that manaully. However you can set a script to run before the snapshot to create it for you automatically.

4. I dont think anyone can give you that.

Martin

|||

For #3 you have options, see @.schema_option for sp_addarticle.

|||thanks both of you... i ll keep this in mind when i come back to replication.. at the moment i am on long vacations...

Maintainence of Replication

Hi Dear...

I have some questions regarding replication in SQL Server 2005.

1. Is it neccessary to have same schema on each side i.e on subsicriber and on publisher?

2. Do replication helps me to replicate the changed schema (of published articals) to the subscribers?

3. If a UDT is defined on publisher and one of its dependent is selected for publication do i need to define the UDT on subscriber manually or it will automatically done for me?

4. pls anyone who can give me the detail known issues and their alternative solutions in regard of maintainence of Replication.

Regards

Mubashar Ahmad

1. Subscriber can have a either the full table, a portion of the table or not at all. You cannot replicate to a totally different schema though.

2. Yes it will replicate ALTER statements.

3. I think you have to do that manaully. However you can set a script to run before the snapshot to create it for you automatically.

4. I dont think anyone can give you that.

Martin

|||

For #3 you have options, see @.schema_option for sp_addarticle.

|||thanks both of you... i ll keep this in mind when i come back to replication.. at the moment i am on long vacations...

Maintainence of Replication

Hi Dear...

I have some questions regarding replication in SQL Server 2005.

1. Is it neccessary to have same schema on each side i.e on subsicriber and on publisher?

2. Do replication helps me to replicate the changed schema (of published articals) to the subscribers?

3. If a UDT is defined on publisher and one of its dependent is selected for publication do i need to define the UDT on subscriber manually or it will automatically done for me?

4. pls anyone who can give me the detail known issues and their alternative solutions in regard of maintainence of Replication.

Regards

Mubashar Ahmad

1. Subscriber can have a either the full table, a portion of the table or not at all. You cannot replicate to a totally different schema though.

2. Yes it will replicate ALTER statements.

3. I think you have to do that manaully. However you can set a script to run before the snapshot to create it for you automatically.

4. I dont think anyone can give you that.

Martin

|||

For #3 you have options, see @.schema_option for sp_addarticle.

|||thanks both of you... i ll keep this in mind when i come back to replication.. at the moment i am on long vacations...

Maintainence of Replication

Hi Dear...

I have some questions regarding replication in SQL Server 2005.

1. Is it neccessary to have same schema on each side i.e on subsicriber and on publisher?

2. Do replication helps me to replicate the changed schema (of published articals) to the subscribers?

3. If a UDT is defined on publisher and one of its dependent is selected for publication do i need to define the UDT on subscriber manually or it will automatically done for me?

4. pls anyone who can give me the detail known issues and their alternative solutions in regard of maintainence of Replication.

Regards

Mubashar Ahmad

1. Subscriber can have a either the full table, a portion of the table or not at all. You cannot replicate to a totally different schema though.

2. Yes it will replicate ALTER statements.

3. I think you have to do that manaully. However you can set a script to run before the snapshot to create it for you automatically.

4. I dont think anyone can give you that.

Martin

|||

For #3 you have options, see @.schema_option for sp_addarticle.

|||thanks both of you... i ll keep this in mind when i come back to replication.. at the moment i am on long vacations...

Monday, March 26, 2012

Maintenance Plan

Maintenance Plan

Friday, March 23, 2012

Maintenance Plan

Monday, March 19, 2012

Maintainence of Replication

Maintainence of Replication

Maintainence of Replication

Maintainence of Replication

Lowering priority

Blog Archive

About Me