Is it possible to intall SQL Server 2000 Utilities without installing SQL Server itself?

Thank
remove xxx's to emailYes, just select only the client tools in the setup. Make sure you follow
the license agreement, though ;-=--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Sphynx" <xxxjoseph.dempsey@.xxxmedcath.com> wrote in message
news:26CCDD79-BBEF-4F8C-A156-0C57327A6523@.microsoft.com...
> Thanks
> remove xxx's to email|||Absolutely. Just place the install CD in the drive and de-select the
options you don't want when it comes up.
If you're using the Standard Edition on an XP or 2K Pro box you'll only get
the option to install the tools anyway.
Buck
"Sphynx" <xxxjoseph.dempsey@.xxxmedcath.com> wrote in message
news:26CCDD79-BBEF-4F8C-A156-0C57327A6523@.microsoft.com...
> Thanks
> remove xxx's to email|||Thanks...

Is it possible for a table to increase size when deleting records?

No transaction log involved, only the table itself.

Use sp_spaceused "table_name" to check the space used.

It seems the table size actually increased from the beginning to the middle of deletion, at the end of deletion, its size decreased.

Recovery mode set to be simple, autoshrink turned on.

The tables tested are about 50MB ~ several GB in size, all have the same behavior. The size increased about 5%~10%.

Since the deletion is called from another software, I want to know if it is possible for SQL Server to have this behavior or it is absolutely the 3rd party software's issue

Thanks!

First of all, you really should turn auto-shrink off. It causes lots of problems with performance and fragmentation.

You probably are seeing index and table fragmentention during the delete. What I would do would be to turn autoshrink off, then if I was very concerned about table size, I would either ALTER INDEX REBUILD or ALTER INDEX REORGANIZE after a large delete to cleanup and shrink the indexes.

|||When you delete a record in SQL Server, the record normally does not get deleted immediately. What happens is that we set a bit in the record to indicate that the record is deleted (this is called the ghost bit).

There is a background process, ghost cleanup task, that runs every 15 seconds and tries to remove records from pages. For indexes, the ghost cleanup task will also remove pages that get empty. For heaps, the ghost cleanup task will not remove pages that get empty

So if your table is a heap, and you are doing a lot of deletes, it is possible that the size of your table does not get smaller. In case of heaps, we will only deallocate pages when we have a table lock on the heap.

There is one other corner scenario where during deletes a record can actually grow in size. For this scenario, you need to have snapshot isolation enabled on the database. When you delete a record during snapshot isolation, we will ghost the record, but we will add version related information (14 bytes) to the record so that snapshot isolation works correctly. Any ghosted records that are part of active transactions cannot be removed by the ghost cleanup task. So in this case, during a delete, you will actually need more space than before, as we need to store the version information for each record as well, potentially adding 14 bytes per record.

For heaps, this might even get worse. If a record gets ghosted and grows with 14 bytes, we might actually have to forward the record to another page if it does not fit on the current page anymore, meaning that you might see a lot of extra space being used. Again, this only happens when snapshot isolation is turned on and you have a lot of pages in the heap that are almost full. Also, the average record size needs to be less than 32 bytes for this to happen, otherwise we do some things in the engine to avoid the forwarding.

Hope this helps,

Is it posible to have publications with diferent schedules?

I have 1 Publisher Server that uses itself as the distributor for 3
different publications.
The publications are all transactional and all publications use Push
subscriptions to replicate their articles.
I have 2 Subscriber servers. Each subscriber server receives 3 push
subscriptions, 1 from each of publications of the Publisher Server.
My Question is can I have different Distribution Agent Schedules for each of
the different publications?
In other words, can publication_1 can be distributed with a schedule of 1
try every day, publication_2 with a schedule of 2 tries evey day and
publication_3 with a constant (inmediate) distribution shedule?
I have tried tihs, when I create the push subscriptions I specify diffrent
schedules for each subscription but when I look in the Agents folder under
Distribution Agents I can only find an entry that says
'multiple-publications' and only has One Schedule.
In contrast under SnapShot Agents there are one entry for each of the
publications, each with a schedule.
Thanks for any help or info.
You sure can, however you need to use the independent_agent option on your
publication.
sp_changepublication 'publicationName','independent_option','true'
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Adrian320" <Adrian320@.discussions.microsoft.com> wrote in message
news:06C20D17-F2BA-4AE9-BF42-C019A5DBDDEB@.microsoft.com...
> I have 1 Publisher Server that uses itself as the distributor for 3
> different publications.
> The publications are all transactional and all publications use Push
> subscriptions to replicate their articles.
> I have 2 Subscriber servers. Each subscriber server receives 3 push
> subscriptions, 1 from each of publications of the Publisher Server.
> My Question is can I have different Distribution Agent Schedules for each
of
> the different publications?
> In other words, can publication_1 can be distributed with a schedule of 1
> try every day, publication_2 with a schedule of 2 tries evey day and
> publication_3 with a constant (inmediate) distribution shedule?
> I have tried tihs, when I create the push subscriptions I specify diffrent
> schedules for each subscription but when I look in the Agents folder under
> Distribution Agents I can only find an entry that says
> 'multiple-publications' and only has One Schedule.
> In contrast under SnapShot Agents there are one entry for each of the
> publications, each with a schedule.
> Thanks for any help or info.
|||Thanks, I'll try that right away.
Just out of curiosity is that parameter asked in the publication wizard, by
any chance?
"Hilary Cotter" wrote:

> You sure can, however you need to use the independent_agent option on your
> publication.
> sp_changepublication 'publicationName','independent_option','true'
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "Adrian320" <Adrian320@.discussions.microsoft.com> wrote in message
> news:06C20D17-F2BA-4AE9-BF42-C019A5DBDDEB@.microsoft.com...
> of
>
>
|||I have never tried it, but I assumed you could create different schedules
for each of the subscriptions under the publication.
Does it not work ? Do they all run in continuous mode ?
"Adrian320" <Adrian320@.discussions.microsoft.com> wrote in message
news:06C20D17-F2BA-4AE9-BF42-C019A5DBDDEB@.microsoft.com...
> I have 1 Publisher Server that uses itself as the distributor for 3
> different publications.
> The publications are all transactional and all publications use Push
> subscriptions to replicate their articles.
> I have 2 Subscriber servers. Each subscriber server receives 3 push
> subscriptions, 1 from each of publications of the Publisher Server.
> My Question is can I have different Distribution Agent Schedules for each
of
> the different publications?
> In other words, can publication_1 can be distributed with a schedule of 1
> try every day, publication_2 with a schedule of 2 tries evey day and
> publication_3 with a constant (inmediate) distribution shedule?
> I have tried tihs, when I create the push subscriptions I specify diffrent
> schedules for each subscription but when I look in the Agents folder under
> Distribution Agents I can only find an entry that says
> 'multiple-publications' and only has One Schedule.
> In contrast under SnapShot Agents there are one entry for each of the
> publications, each with a schedule.
> Thanks for any help or info.
|||with the parameter Hilary said, yes it works. Without it you have only one
schecule for each subscriber/publication, helas you can't have without the
parameter activated varios schedules for the same subscriber in differente
publications.
Adrian
"Hassan" wrote:

> I have never tried it, but I assumed you could create different schedules
> for each of the subscriptions under the publication.
> Does it not work ? Do they all run in continuous mode ?
> "Adrian320" <Adrian320@.discussions.microsoft.com> wrote in message
> news:06C20D17-F2BA-4AE9-BF42-C019A5DBDDEB@.microsoft.com...
> of
>
>
|||Now my heads hurting..
Can you give me an example..
Say in your case we have Publisher1 and Subscriber1,Subscriber2 and
Subscriber3
You have 2 publications Pub1 and Pub2
Pub1 has 3 subscriptions to the 3 subscribers
and Pub2 has 3 subscriptions to the 3 subscribers
So if i go to each of the subscriptions for Pub1, can I not create seperate
schedules for the distribution agent ? Or am I not following something
Please use the example and help me understand.
"Adrian320" <Adrian320@.discussions.microsoft.com> wrote in message
news:E90BCEA8-CED8-428E-BF92-9A440E23FD66@.microsoft.com...[vbcol=seagreen]
> with the parameter Hilary said, yes it works. Without it you have only one
> schecule for each subscriber/publication, helas you can't have without the
> parameter activated varios schedules for the same subscriber in differente
> publications.
> Adrian
> "Hassan" wrote:
schedules[vbcol=seagreen]
each[vbcol=seagreen]
of 1[vbcol=seagreen]
diffrent[vbcol=seagreen]
under[vbcol=seagreen]
|||no, but it does show up in your publication properties in the subscription
options tab. Chances are however you will need to use sp_changepublication
to enable it.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Adrian320" <Adrian320@.discussions.microsoft.com> wrote in message
news:8A96C8B2-0FF9-47E6-B4CE-6FB0B12D2273@.microsoft.com...
> Thanks, I'll try that right away.
> Just out of curiosity is that parameter asked in the publication wizard,
by[vbcol=seagreen]
> any chance?
> "Hilary Cotter" wrote:
your[vbcol=seagreen]
each[vbcol=seagreen]
of 1[vbcol=seagreen]
diffrent[vbcol=seagreen]
under[vbcol=seagreen]
|||No, if pubs and pub2 are in the same publication database, there will be a
single distribution agent by default, going to each subscriber. What
replication will do is share an agent for the same type from the same
publication database to the same subscription database.
With the shared agent, there can be no different schedules. With the
independent agent option you can set multiple schedules.
HTH
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:u23zm$48EHA.2452@.TK2MSFTNGP14.phx.gbl...
> Now my heads hurting..
> Can you give me an example..
> Say in your case we have Publisher1 and Subscriber1,Subscriber2 and
> Subscriber3
> You have 2 publications Pub1 and Pub2
> Pub1 has 3 subscriptions to the 3 subscribers
> and Pub2 has 3 subscriptions to the 3 subscribers
> So if i go to each of the subscriptions for Pub1, can I not create
seperate[vbcol=seagreen]
> schedules for the distribution agent ? Or am I not following something
> Please use the example and help me understand.
> "Adrian320" <Adrian320@.discussions.microsoft.com> wrote in message
> news:E90BCEA8-CED8-428E-BF92-9A440E23FD66@.microsoft.com...
one[vbcol=seagreen]
the[vbcol=seagreen]
differente[vbcol=seagreen]
> schedules
> each
> of 1
> diffrent
> under
the
>