Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts

Friday, February 17, 2012

default tempdb size

Hello All,
SQL 2K W/SP3
Is it possible to change default tempdb size to something else other than
2MB so everytime server restarts, tempdb does nto go back to 2 MB?
Thanks,
BivaYep. You can also change location for the db files. Info is stored in
master..sysaltfiles, and you change it using ALTER DATABASE (see Books
Online for details).
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Biva" <biva.yauchler@.redprairie.com> wrote in message
news:40102f2f$0$43850$39cecf19@.news.twtelecom.net...
> Hello All,
> SQL 2K W/SP3
> Is it possible to change default tempdb size to something else other than
> 2MB so everytime server restarts, tempdb does nto go back to 2 MB?
> Thanks,
> Biva
>|||Biva,
ALTER DATABASE should work just fine.
Russell Fields
"Biva" <biva.yauchler@.redprairie.com> wrote in message
news:40102f2f$0$43850$39cecf19@.news.twtelecom.net...
> Hello All,
> SQL 2K W/SP3
> Is it possible to change default tempdb size to something else other than
> 2MB so everytime server restarts, tempdb does nto go back to 2 MB?
> Thanks,
> Biva
>

Tuesday, February 14, 2012

default replication mechanism

Hi,
I did'n want to use default replication mechanism when I initially set up
transactional replication between 2 servers (sql server 2000 sp3). However,
now I need to change replication to use default mechanism for some operations
(inserts/updates/deletes) of existing articles.
1. Is there any way to do that without dropping whole publication (for the
articles which didn't replicate updates to the other side)?
2. Also, is there any way to generate sp_MSins... stored procedures without
synchronizing data between publisher and subsciber (option "created stored
procedures during initial synchronization of subscriptions")? I have 2 large
databases, and initializing subscriptions (synchronizing data) just to
generate these stored procedures wouldn't make lot of sense.
Thanks
Pedja,
here's the answer to the second question:
http://msdn2.microsoft.com/en-us/library/ms187946.aspx
For the first question, I'm not quite sure what you're asking. Do you want
to add an article to an existing publication? If so, you can do this from
the GUI, run the snapshot agent and synchronize. This will just add the new
article and not reinitialize the others.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks for the answer.
For the first question, since I replicated inserts, but not delets and
updates in the old setup, these two fields are grayed (unavailable). What I
am asking is is there a way to enable them (check them to use generated
stored procedures), without droping and recreating publication (unchecking
and checking just that article doesn't work)?
"Paul Ibison" wrote:

> Pedja,
> here's the answer to the second question:
> http://msdn2.microsoft.com/en-us/library/ms187946.aspx
> For the first question, I'm not quite sure what you're asking. Do you want
> to add an article to an existing publication? If so, you can do this from
> the GUI, run the snapshot agent and synchronize. This will just add the new
> article and not reinitialize the others.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Pedja,
not as far as I know. I think your best bet would be to do a nosync
initialization.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)