Puzzled by Config files

I created a package, created an XML Config file, created a deployment utility and then deployed to server. I scheduled it with agent and I get this error (changed the package name in the error to IMPORT to make it more readable):

Description: The configuration file name "C:\Documents and Settings\chris\My Documents\Visual Studio 2005\Projects\IMPORT\IMPORT\IMPORT.dtsConfig" is not valid. Check the configuration file name. End Warning Warning: 2006-07-12 13:11:39.96 Code: 0x80012059 Source: IMPORT Description: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed. End Warning Progress: 2006-07-12 13:11:40.56 Source: Import Data Validating: 0% complete End Progress Progress: 2006-07-12 13:11:40.56 Source:... Process Exit Code 1. The step failed.

So basically its trying to point to a config file on my dev workstation. When I created the deploy utility it created a config file in the Deployment directory with the Manifest and the package. I installed from the deployment directory. When installing it asked where I wanted to install and I left it the default of "C:\Program Files\Microsoft SQL Server\90\DTS\Packages\IMPORT" and if I look in that folder the IMPORT.dtsconfig is there.

Ideas of where I went wrong? I want to make sure I understand the whole configuration file notion correctly as I am starting to roll a bunch of packages with config files out to production. I've done the tutorial and thought it was straightforward and made sense. I can fix it by editing the xml of the package and removing the line pointing to my dev box - just want to know what I am doing wrong :)

Nevermind... Found lots of other people with similar issues in diff threads on this forum. This whole config file thing is pretty confusing. When you do the install from the deployment folder it will show all the values from the config file in the deployment directory - but it doesn't use any of them when you actually run the package.

I am really not sure why they put the dtsconfig file in the deployment folder at all - all that does is confuse things. I had been placing the production config file over the one in the deployment folder and assumed it would use it... not so.

Putting SQL Server 05 database on GoDaddy server. Argh!!!

I have a simple Website and Database created in VWD exp.

I've just added a windows account to GoDaddy.com.

Unfortunately there is no way to port your database on to the GoDaddy server directly, but it says you must instead, recreate the database by copying and running SQL statements from a file called "personal-add.sql". (their "help" page: http://help.godaddy.com/article.php?article_id=695)

I can't find any such file. Can someone please let me know what I'm missing here?

Thanks.

Hi Brad -

You should take a look at the Database Publishing Wizard, available at http://www.codeplex.com/sqlhost/Wiki/View.aspx?title=Database%20Publishing%20Wizard&referringTitle=Home. We actually have a guide on how to upload databases using the tool to shared hosters like GoDaddy... see http://www.codeplex.com/sqlhost/Wiki/View.aspx?title=Tutorials&referringTitle=Database%20Publishing%20Wizard.

Let me know if you have any issues.

Thanks,

alex

|||

alex wrote:

Hi Brad -

You should take a look at the Database Publishing Wizard, available at http://www.codeplex.com/sqlhost/Wiki/View.aspx?title=Database%20Publishing%20Wizard&referringTitle=Home. We actually have a guide on how to upload databases using the tool to shared hosters like GoDaddy... see http://www.codeplex.com/sqlhost/Wiki/View.aspx?title=Tutorials&referringTitle=Database%20Publishing%20Wizard.

Let me know if you have any issues.

Thanks,

alex

Thanks for this, for those that are in the same situation as me, a useful program is The SQL Server Database Publishing Wizard

Putting Data From DataTable/DataSet into SQL Server Table?

Hello,

I created this DataTable, add rows of data to it, and then display the data on to a form via a repeater.

Dim ds As DataSet = New DataSet
Dim dtTableName As DataTable = New DataTable("dtTableName")
dtTableName.Columns.Add("Description")
dtTableName.Columns.Add("ItemNumber")
dtTableName.Columns.Add("Quantity")
dtTableName.Columns.Add("Price")
ds.Tables.Add(dtTableName)

What I need to do now is create a table in SQL Server and update the database with the data I've collect in my dataset. How do I bind and update this data to a sql server table?

Thanks!
James

Check out this walkthrough (it uses a DataGrid and DataSet):
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vbwlkWalkthroughUpdatingDataUsingDatabaseUpdateQueryInWebForms.asp

Purging TempDB

Hi DB Experts

I have a question on shrinking tempDB. Currently, I am using MS SQL 2005 Server, I have a software that used SQL DB but I had created a separate database to store my data. The tempDB is totally not used at all.

Problem - Whenever I export data into my created database on MS SQL server, tempDB also grew, I noticed that the files grew so large that it crashed the server. I am running 50GB free space on my drive where by the MS SQL server was installed.

Question - May I know are there any solution to shrink or freeze the growth of tempDB size?

Best regards

TEWCT

This statement

The tempDB is totally not used at all.

is totally wrong!

TempDb is constantly used as a staging area (or 'scratchpad') when gathering data for queries.

TempDb will continue to grow as long as there is a need. You can take the server off line (or stop the server service) and remove the TempDb database, and it will be recreated when the server starts up.

|||

You should in fact size your tempdb appropriately to increase performance.

If the export is causing your tempdb to grow to 50GB you should carefully look at the queryplans used in the export (or you are exporting a massive amount of data).

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

|||

Here's some more info on how to properly plan for TempDB sizing and also how to troubleshoot when it grows too large. The second link also includes instructions on how to limit the size of TempDB.

http://msdn2.microsoft.com/en-us/library/ms176029(sql.90).aspx

http://msdn2.microsoft.com/en-us/library/ms175527(SQL.90).aspx

Hope that helps,

-Steve

|||

Hi Steve and guys

Greetings. Thks for your advices & responses. Apologized, I am not a SQL guru. Am I right to say tempDB will definitely be used even if I created a separated DB for my application; even when I perform any simple query or update? My growth rate is about 500MB per day which I have been monitoring it over 3 days for now.

I had also performed some research from MSDN library that Steve had adviced, it seemed that it is a Microsoft methodology that SQL server behaviour;

i) TempDB size will definitely grow;

ii) DB tuning is required

iii) Factor more disk space for the growth?

iv) Restarting SQL service on regular basis

I would like to know if there is any specific way other then to re-provision and solve this SQL server tempDB growing issue?

|||

In a production server, the growth of TempDb 'should' eventually stablize. There may be regularly scheduled reports, etc., that require a large amount of space. There may be 'regular' data import/exports (ETL) activities that will require a large amount of space.

After your database is in production, and the initial 'load' activity has subsided, you may be able to reduce the size of TempDb by restarting the SQL Service -but if there is extensive data querying for reports or ETL activities, it may just grow again. So give it time, determine the 'appropriate' size, and let it be.

|||

Also have a look at this article:

How to shrink the tempdb database in SQL Server
http://support.microsoft.com/kb/307487/en-us

|||Hi guys. Thanks for your information. I will try that out and update at a later stage.

purge process from large table

Hi,
We have specific request here: there is a large table, around 5,000,000 rows
(3GB). It has unique clustered index, created on 6 of it's 10 columns. We
have to delete around 15% of rows every day, but in a way that table keeps
being available all the time. Deletion criteria is date (where
column_date<=getdate()). There is nonclustered index created on column_date
table. Since there is availability criteria, simple: delete <table name>
where column_date<=getdate() is out of the question because of exclusive
table lock on this table.
Any ideas?
Thanks,
PedjaBy "available" do you mean readable via a SELECT?
If you are using SQL 2005, you can take advantage of the new Read Committed
Snapshot Isolation level, which allows a SELECT to read the most
recently-committed version of a set of data, even while that data is being
modified.
If you are using SQL 2000, your readers can use WITH (NOLOCK) as an option
to the SELECT statements, putting the transaction into read uncommited. Your
readers won't have to wait for writers, but you may get inaccurate data.
Is it possible that you can split this delete operation so that it occurs
several times a day? That way it can delete fewer rows, resulting in less
blocking time.
"Pedja" wrote:

> Hi,
> We have specific request here: there is a large table, around 5,000,000 ro
ws
> (3GB). It has unique clustered index, created on 6 of it's 10 columns. We
> have to delete around 15% of rows every day, but in a way that table keeps
> being available all the time. Deletion criteria is date (where
> column_date<=getdate()). There is nonclustered index created on column_dat
e
> table. Since there is availability criteria, simple: delete <table name>
> where column_date<=getdate() is out of the question because of exclusive
> table lock on this table.
> Any ideas?
> Thanks,
> Pedja|||Mark,
We use sql server 2000. By available, I mean both, read/write operations.
NOLOCK hint won't help, because once it is grabbed by purge process, table i
s
being locked until it is completed (that is why I posted this question
initially), so neither reads nor writes are allowed during this time. My ide
a
was to split deletion process to batches of 1000 rows (set rowcount 1000),
but I wanted to hear some other ideas too.
Thanks
"Mark Williams" wrote:
> By "available" do you mean readable via a SELECT?
> If you are using SQL 2005, you can take advantage of the new Read Committe
d
> Snapshot Isolation level, which allows a SELECT to read the most
> recently-committed version of a set of data, even while that data is being
> modified.
> If you are using SQL 2000, your readers can use WITH (NOLOCK) as an option
> to the SELECT statements, putting the transaction into read uncommited. Yo
ur
> readers won't have to wait for writers, but you may get inaccurate data.
> Is it possible that you can split this delete operation so that it occurs
> several times a day? That way it can delete fewer rows, resulting in less
> blocking time.
> --
> "Pedja" wrote:
>|||Pedja,
you could split up your data into several tables, one table per day.
You can access them via a UNION ALL view. Then the purge is very fast,
you just re-create the view, which is a snap, and drop the oldest
table. There are some divantages: some of queries against the view
will work slower, and you will not be able to enforse unique (and
sometimes other) constraints just as easily|||Hi
Divide your deletion into small batches
SET ROWCOUNT 1000
WHILE 1 = 1
BEGIN
--Here your DML Statement
IF @.@.ROWCOUNT = 0
BEGIN
BREAK
END
END
SET ROWCOUNT 0
"Pedja" <Pedja@.discussions.microsoft.com> wrote in message
news:38445382-60B6-4327-A3FE-C5AD8BF88E41@.microsoft.com...
> Hi,
> We have specific request here: there is a large table, around 5,000,000
> rows
> (3GB). It has unique clustered index, created on 6 of it's 10 columns. We
> have to delete around 15% of rows every day, but in a way that table keeps
> being available all the time. Deletion criteria is date (where
> column_date<=getdate()). There is nonclustered index created on
> column_date
> table. Since there is availability criteria, simple: delete <table name>
> where column_date<=getdate() is out of the question because of exclusive
> table lock on this table.
> Any ideas?
> Thanks,
> Pedjasql

purge .txt log files

SS2005, SP2
Anyone has a quick way of deleting log files for db maint. plans? By default
they are text files created under the LOG directory. Tired of googling for
it 'cause there arn't many posts...I believe this is in one of the maint tasks.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
> SS2005, SP2
> Anyone has a quick way of deleting log files for db maint. plans? By default
> they are text files created under the LOG directory. Tired of googling for
> it 'cause there arn't many posts...
>|||Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the
job. They simply cleanup the actual backup files, or the backup/restore
history tables in msdb. I want something to clean up the log files otherwise
they keep accumulating...
I can write a homegrown process to handle this. But I'd be amazed that
there isn't anything out of the SSIS box that can do this.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>I believe this is in one of the maint tasks.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "YPD" <y.ding@.neu.edu> wrote in message
> news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
>> SS2005, SP2
>> Anyone has a quick way of deleting log files for db maint. plans? By
>> default they are text files created under the LOG directory. Tired of
>> googling for it 'cause there arn't many posts...|||> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the job.
I see, I though this was part of the "standard process". But Maint Cleanup Task isn't limited to
deletion of backup files. Did you try to add one more such task for deletion of the .txt files?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...
> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the job. They simply
> cleanup the actual backup files, or the backup/restore history tables in msdb. I want something to
> clean up the log files otherwise they keep accumulating...
> I can write a homegrown process to handle this. But I'd be amazed that there isn't anything out
> of the SSIS box that can do this.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>>I believe this is in one of the maint tasks.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
>> SS2005, SP2
>> Anyone has a quick way of deleting log files for db maint. plans? By default they are text files
>> created under the LOG directory. Tired of googling for it 'cause there arn't many posts...
>|||Yes, I tried but it didn't work. I also tried to fool the manit plan to
purge regular text files that were renamed just like the backup files. It's
smart enough to know what files are real backup files and what are not, and
only delete REAL backup files. interesting! Fortunately those txt log files
are tiny (1 or 2 kbs each) so leaving them uncleaned really isn't a big
deal.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:078461FC-C310-454D-BEE9-721958C7E312@.microsoft.com...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does
>> the job.
> I see, I though this was part of the "standard process". But Maint Cleanup
> Task isn't limited to deletion of backup files. Did you try to add one
> more such task for deletion of the .txt files?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "YPD" <y.ding@.neu.edu> wrote in message
> news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does
>> the job. They simply cleanup the actual backup files, or the
>> backup/restore history tables in msdb. I want something to clean up the
>> log files otherwise they keep accumulating...
>> I can write a homegrown process to handle this. But I'd be amazed that
>> there isn't anything out of the SSIS box that can do this.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>>I believe this is in one of the maint tasks.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message
>> news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
>> SS2005, SP2
>> Anyone has a quick way of deleting log files for db maint. plans? By
>> default they are text files created under the LOG directory. Tired of
>> googling for it 'cause there arn't many posts...
>>
>|||I'm a bit confused here. When I open the "Maintenance Cleanup Dialog", there's an option to delete
"Maintenance Plan text reports". Perhaps this was introduced with sp2? Or did you try it and it
didn't work (of so, you should file a bug on http://connect.microsoft.com/sql)?.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:eCfoO8ysHHA.4548@.TK2MSFTNGP04.phx.gbl...
> Yes, I tried but it didn't work. I also tried to fool the manit plan to purge regular text files
> that were renamed just like the backup files. It's smart enough to know what files are real backup
> files and what are not, and only delete REAL backup files. interesting! Fortunately those txt log
> files are tiny (1 or 2 kbs each) so leaving them uncleaned really isn't a big deal.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:078461FC-C310-454D-BEE9-721958C7E312@.microsoft.com...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the job.
>> I see, I though this was part of the "standard process". But Maint Cleanup Task isn't limited to
>> deletion of backup files. Did you try to add one more such task for deletion of the .txt files?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the job. They simply
>> cleanup the actual backup files, or the backup/restore history tables in msdb. I want something
>> to clean up the log files otherwise they keep accumulating...
>> I can write a homegrown process to handle this. But I'd be amazed that there isn't anything out
>> of the SSIS box that can do this.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>>I believe this is in one of the maint tasks.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
>> SS2005, SP2
>> Anyone has a quick way of deleting log files for db maint. plans? By default they are text
>> files created under the LOG directory. Tired of googling for it 'cause there arn't many
>> posts...
>>
>|||Tibor, that's a good catch. I overlooked it.
However, i still was unable to get it to work. I have tried it on one
default instance and two clustered instances, with a separate cleanup task
and proper length of days /weeks to purge - log files are not deleted.
A similar bug was logged in the Feedback list earlier this month and MS
marked it as resolved. The ticket wished to build both purging backups and
log files into one interface. So from the wording, it seems someone has
successfully gotten it worked.
I'll try more instances in case it's just a permission issue. Since I've
already had my purge routine in place, it won't be an issue any more even if
it doesn't work. but I'll try to send them a comment on this.
Thanks for your time on helping this.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:EB5BC91A-5A5A-4204-99EA-E6743554D034@.microsoft.com...
> I'm a bit confused here. When I open the "Maintenance Cleanup Dialog",
> there's an option to delete "Maintenance Plan text reports". Perhaps this
> was introduced with sp2? Or did you try it and it didn't work (of so, you
> should file a bug on http://connect.microsoft.com/sql)?.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "YPD" <y.ding@.neu.edu> wrote in message
> news:eCfoO8ysHHA.4548@.TK2MSFTNGP04.phx.gbl...
>> Yes, I tried but it didn't work. I also tried to fool the manit plan to
>> purge regular text files that were renamed just like the backup files.
>> It's smart enough to know what files are real backup files and what are
>> not, and only delete REAL backup files. interesting! Fortunately those
>> txt log files are tiny (1 or 2 kbs each) so leaving them uncleaned really
>> isn't a big deal.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:078461FC-C310-454D-BEE9-721958C7E312@.microsoft.com...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither
>> does the job.
>> I see, I though this was part of the "standard process". But Maint
>> Cleanup Task isn't limited to deletion of backup files. Did you try to
>> add one more such task for deletion of the .txt files?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message
>> news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither
>> does the job. They simply cleanup the actual backup files, or the
>> backup/restore history tables in msdb. I want something to clean up the
>> log files otherwise they keep accumulating...
>> I can write a homegrown process to handle this. But I'd be amazed that
>> there isn't anything out of the SSIS box that can do this.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message
>> news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>>I believe this is in one of the maint tasks.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message
>> news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
>> SS2005, SP2
>> Anyone has a quick way of deleting log files for db maint. plans? By
>> default they are text files created under the LOG directory. Tired of
>> googling for it 'cause there arn't many posts...
>>
>>
>|||> I'll try more instances in case it's just a permission issue. Since I've
> already had my purge routine in place, it won't be an issue any more even if
> it doesn't work. but I'll try to send them a comment on this.
This is what I also tend to do. When Maint plans don't do what you want, do it yourself... :-)
Let us know if you find out anything more about this... :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:eOtl7aDuHHA.1204@.TK2MSFTNGP03.phx.gbl...
> Tibor, that's a good catch. I overlooked it.
> However, i still was unable to get it to work. I have tried it on one
> default instance and two clustered instances, with a separate cleanup task
> and proper length of days /weeks to purge - log files are not deleted.
> A similar bug was logged in the Feedback list earlier this month and MS
> marked it as resolved. The ticket wished to build both purging backups and
> log files into one interface. So from the wording, it seems someone has
> successfully gotten it worked.
> I'll try more instances in case it's just a permission issue. Since I've
> already had my purge routine in place, it won't be an issue any more even if
> it doesn't work. but I'll try to send them a comment on this.
> Thanks for your time on helping this.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:EB5BC91A-5A5A-4204-99EA-E6743554D034@.microsoft.com...
>> I'm a bit confused here. When I open the "Maintenance Cleanup Dialog",
>> there's an option to delete "Maintenance Plan text reports". Perhaps this
>> was introduced with sp2? Or did you try it and it didn't work (of so, you
>> should file a bug on http://connect.microsoft.com/sql)?.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message
>> news:eCfoO8ysHHA.4548@.TK2MSFTNGP04.phx.gbl...
>> Yes, I tried but it didn't work. I also tried to fool the manit plan to
>> purge regular text files that were renamed just like the backup files.
>> It's smart enough to know what files are real backup files and what are
>> not, and only delete REAL backup files. interesting! Fortunately those
>> txt log files are tiny (1 or 2 kbs each) so leaving them uncleaned really
>> isn't a big deal.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:078461FC-C310-454D-BEE9-721958C7E312@.microsoft.com...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither
>> does the job.
>> I see, I though this was part of the "standard process". But Maint
>> Cleanup Task isn't limited to deletion of backup files. Did you try to
>> add one more such task for deletion of the .txt files?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message
>> news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...
>> Have tried the History Cleanup Task and Maint Cleanup Task. Neither
>> does the job. They simply cleanup the actual backup files, or the
>> backup/restore history tables in msdb. I want something to clean up the
>> log files otherwise they keep accumulating...
>> I can write a homegrown process to handle this. But I'd be amazed that
>> there isn't anything out of the SSIS box that can do this.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message
>> news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>>I believe this is in one of the maint tasks.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "YPD" <y.ding@.neu.edu> wrote in message
>> news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
>>> SS2005, SP2
>>>
>>> Anyone has a quick way of deleting log files for db maint. plans? By
>>> default they are text files created under the LOG directory. Tired of
>>> googling for it 'cause there arn't many posts...
>>
>>
>>
>

purge .txt log files

SS2005, SP2
Anyone has a quick way of deleting log files for db maint. plans? By default
they are text files created under the LOG directory. Tired of googling for
it 'cause there arn't many posts...I believe this is in one of the maint tasks.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...seagreen">
> SS2005, SP2
> Anyone has a quick way of deleting log files for db maint. plans? By defau
lt
> they are text files created under the LOG directory. Tired of googling for
> it 'cause there arn't many posts...
>|||Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the
job. They simply cleanup the actual backup files, or the backup/restore
history tables in msdb. I want something to clean up the log files otherwise
they keep accumulating...
I can write a homegrown process to handle this. But I'd be amazed that
there isn't anything out of the SSIS box that can do this.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...[vbcol=seagreen]
>I believe this is in one of the maint tasks.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "YPD" <y.ding@.neu.edu> wrote in message
> news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...|||> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does t
he job.
I see, I though this was part of the "standard process". But Maint Cleanup T
ask isn't limited to
deletion of backup files. Did you try to add one more such task for deletion
of the .txt files?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...[vbco
l=seagreen]
> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does t
he job. They simply
> cleanup the actual backup files, or the backup/restore history tables in m
sdb. I want something to
> clean up the log files otherwise they keep accumulating...
> I can write a homegrown process to handle this. But I'd be amazed that th
ere isn't anything out
> of the SSIS box that can do this.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n message
> news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>[/vbcol]|||Yes, I tried but it didn't work. I also tried to fool the manit plan to
purge regular text files that were renamed just like the backup files. It's
smart enough to know what files are real backup files and what are not, and
only delete REAL backup files. interesting! Fortunately those txt log files
are tiny (1 or 2 kbs each) so leaving them uncleaned really isn't a big
deal.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:078461FC-C310-454D-BEE9-721958C7E312@.microsoft.com...
> I see, I though this was part of the "standard process". But Maint Cleanup
> Task isn't limited to deletion of backup files. Did you try to add one
> more such task for deletion of the .txt files?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "YPD" <y.ding@.neu.edu> wrote in message
> news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...
>|||I'm a bit confused here. When I open the "Maintenance Cleanup Dialog", there
's an option to delete
"Maintenance Plan text reports". Perhaps this was introduced with sp2? Or di
d you try it and it
didn't work (of so, you should file a bug on http://connect.microsoft.com/sql[/u...ver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:eCfoO8ysHHA.4548@.TK2MSFTNGP04.phx.gbl...seagreen">
> Yes, I tried but it didn't work. I also tried to fool the manit plan to pu
rge regular text files
> that were renamed just like the backup files. It's smart enough to know wh
at files are real backup
> files and what are not, and only delete REAL backup files. interesting! Fo
rtunately those txt log
> files are tiny (1 or 2 kbs each) so leaving them uncleaned really isn't a
big deal.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n message
> news:078461FC-C310-454D-BEE9-721958C7E312@.microsoft.com...
>|||Tibor, that's a good catch. I overlooked it.
However, i still was unable to get it to work. I have tried it on one
default instance and two clustered instances, with a separate cleanup task
and proper length of days /weeks to purge - log files are not deleted.
A similar bug was logged in the Feedback list earlier this month and MS
marked it as resolved. The ticket wished to build both purging backups and
log files into one interface. So from the wording, it seems someone has
successfully gotten it worked.
I'll try more instances in case it's just a permission issue. Since I've
already had my purge routine in place, it won't be an issue any more even if
it doesn't work. but I'll try to send them a comment on this.
Thanks for your time on helping this.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:EB5BC91A-5A5A-4204-99EA-E6743554D034@.microsoft.com...
> I'm a bit confused here. When I open the "Maintenance Cleanup Dialog",
> there's an option to delete "Maintenance Plan text reports". Perhaps this
> was introduced with sp2? Or did you try it and it didn't work (of so, you
> should file a bug on http://connect.microsoft.com/sql)?.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "YPD" <y.ding@.neu.edu> wrote in message
> news:eCfoO8ysHHA.4548@.TK2MSFTNGP04.phx.gbl...
>|||> I'll try more instances in case it's just a permission issue. Since I've
> already had my purge routine in place, it won't be an issue any more even
if
> it doesn't work. but I'll try to send them a comment on this.
This is what I also tend to do. When Maint plans don't do what you want, do
it yourself... :-)
Let us know if you find out anything more about this... :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:eOtl7aDuHHA.1204@.TK2MSFTNGP03.phx.gbl...seagreen">
> Tibor, that's a good catch. I overlooked it.
> However, i still was unable to get it to work. I have tried it on one
> default instance and two clustered instances, with a separate cleanup task
> and proper length of days /weeks to purge - log files are not deleted.
> A similar bug was logged in the Feedback list earlier this month and MS
> marked it as resolved. The ticket wished to build both purging backups and
> log files into one interface. So from the wording, it seems someone has
> successfully gotten it worked.
> I'll try more instances in case it's just a permission issue. Since I've
> already had my purge routine in place, it won't be an issue any more even
if
> it doesn't work. but I'll try to send them a comment on this.
> Thanks for your time on helping this.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n
> message news:EB5BC91A-5A5A-4204-99EA-E6743554D034@.microsoft.com...
>sql

purge .txt log files

SS2005, SP2
Anyone has a quick way of deleting log files for db maint. plans? By default
they are text files created under the LOG directory. Tired of googling for
it 'cause there arn't many posts...
I believe this is in one of the maint tasks.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
> SS2005, SP2
> Anyone has a quick way of deleting log files for db maint. plans? By default
> they are text files created under the LOG directory. Tired of googling for
> it 'cause there arn't many posts...
>
|||Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the
job. They simply cleanup the actual backup files, or the backup/restore
history tables in msdb. I want something to clean up the log files otherwise
they keep accumulating...
I can write a homegrown process to handle this. But I'd be amazed that
there isn't anything out of the SSIS box that can do this.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...[vbcol=seagreen]
>I believe this is in one of the maint tasks.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "YPD" <y.ding@.neu.edu> wrote in message
> news:eA$PGNqsHHA.4968@.TK2MSFTNGP06.phx.gbl...
|||> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the job.
I see, I though this was part of the "standard process". But Maint Cleanup Task isn't limited to
deletion of backup files. Did you try to add one more such task for deletion of the .txt files?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...
> Have tried the History Cleanup Task and Maint Cleanup Task. Neither does the job. They simply
> cleanup the actual backup files, or the backup/restore history tables in msdb. I want something to
> clean up the log files otherwise they keep accumulating...
> I can write a homegrown process to handle this. But I'd be amazed that there isn't anything out
> of the SSIS box that can do this.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:8F12D2C7-FA8E-4CFD-A9A4-B273084C46C9@.microsoft.com...
>
|||Yes, I tried but it didn't work. I also tried to fool the manit plan to
purge regular text files that were renamed just like the backup files. It's
smart enough to know what files are real backup files and what are not, and
only delete REAL backup files. interesting! Fortunately those txt log files
are tiny (1 or 2 kbs each) so leaving them uncleaned really isn't a big
deal.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:078461FC-C310-454D-BEE9-721958C7E312@.microsoft.com...
> I see, I though this was part of the "standard process". But Maint Cleanup
> Task isn't limited to deletion of backup files. Did you try to add one
> more such task for deletion of the .txt files?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "YPD" <y.ding@.neu.edu> wrote in message
> news:%23dWriGrsHHA.1728@.TK2MSFTNGP06.phx.gbl...
>
|||I'm a bit confused here. When I open the "Maintenance Cleanup Dialog", there's an option to delete
"Maintenance Plan text reports". Perhaps this was introduced with sp2? Or did you try it and it
didn't work (of so, you should file a bug on http://connect.microsoft.com/sql)?.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:eCfoO8ysHHA.4548@.TK2MSFTNGP04.phx.gbl...
> Yes, I tried but it didn't work. I also tried to fool the manit plan to purge regular text files
> that were renamed just like the backup files. It's smart enough to know what files are real backup
> files and what are not, and only delete REAL backup files. interesting! Fortunately those txt log
> files are tiny (1 or 2 kbs each) so leaving them uncleaned really isn't a big deal.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:078461FC-C310-454D-BEE9-721958C7E312@.microsoft.com...
>
|||Tibor, that's a good catch. I overlooked it.
However, i still was unable to get it to work. I have tried it on one
default instance and two clustered instances, with a separate cleanup task
and proper length of days /weeks to purge - log files are not deleted.
A similar bug was logged in the Feedback list earlier this month and MS
marked it as resolved. The ticket wished to build both purging backups and
log files into one interface. So from the wording, it seems someone has
successfully gotten it worked.
I'll try more instances in case it's just a permission issue. Since I've
already had my purge routine in place, it won't be an issue any more even if
it doesn't work. but I'll try to send them a comment on this.
Thanks for your time on helping this.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:EB5BC91A-5A5A-4204-99EA-E6743554D034@.microsoft.com...
> I'm a bit confused here. When I open the "Maintenance Cleanup Dialog",
> there's an option to delete "Maintenance Plan text reports". Perhaps this
> was introduced with sp2? Or did you try it and it didn't work (of so, you
> should file a bug on http://connect.microsoft.com/sql)?.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "YPD" <y.ding@.neu.edu> wrote in message
> news:eCfoO8ysHHA.4548@.TK2MSFTNGP04.phx.gbl...
>
|||> I'll try more instances in case it's just a permission issue. Since I've
> already had my purge routine in place, it won't be an issue any more even if
> it doesn't work. but I'll try to send them a comment on this.
This is what I also tend to do. When Maint plans don't do what you want, do it yourself... :-)
Let us know if you find out anything more about this... :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"YPD" <y.ding@.neu.edu> wrote in message news:eOtl7aDuHHA.1204@.TK2MSFTNGP03.phx.gbl...
> Tibor, that's a good catch. I overlooked it.
> However, i still was unable to get it to work. I have tried it on one
> default instance and two clustered instances, with a separate cleanup task
> and proper length of days /weeks to purge - log files are not deleted.
> A similar bug was logged in the Feedback list earlier this month and MS
> marked it as resolved. The ticket wished to build both purging backups and
> log files into one interface. So from the wording, it seems someone has
> successfully gotten it worked.
> I'll try more instances in case it's just a permission issue. Since I've
> already had my purge routine in place, it won't be an issue any more even if
> it doesn't work. but I'll try to send them a comment on this.
> Thanks for your time on helping this.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:EB5BC91A-5A5A-4204-99EA-E6743554D034@.microsoft.com...
>

Pull subscription and ISA server

Hi
Can anyone point me in the right direction, I am trying to do an anonymous
pull subscription across the internet. I have created a publisher and created
the snapshot ok. On the subscriber server I can FTP by IP ( the ISA servers
external IP address ) or by the servers name and can see the folders created
in the repldata\ftp directory. I can create a new SQL server registration on
the subscription server and get a connection into the publisher, I can run
sql queries against the publisher ok.
When I try and create a pull subscription, I get to the last page on the
wizard and get
SQL Server enterprise Edition could not create a pull subscription to
publication 'MyDB'
Error 21776: [SQL-DMO] The name 'MyDB' was not found in the TransPublications
collection
Any help greatly appreciated
Having reinstalled and rebooted several times yesterday I was getting nowhere
hence my post in this NG
Come back to it today and the pull subscription worked first time without
any errors on yesterdays configuration. Wierd ?
Anyway, if any one can shed any light on what was going on when it was
failing, please let me know.
thanks

pull subscription

I cannot get a pull subscription to work. I have created my publication
to allow anynonomous. The client is a registered subscriber. On the
subscriber I created the pull subscription always specifying the SQL
server authentication and entering the login/password.
I have enabled loggin, but I can't find where it says this is the
problem.
The error is:
The process could not deliver the snapshot to the subscriber. The step
failed.
I sure would like more information. I am leaning towards a security
issue, but the SQL authentication login and password are also setup on
the server as a user name/password with admin rights.
THe server is Win2000 running SQL 2000. Client is XP Pro running MSDE.
THanks.
Darin
*** Sent via Developersdex http://www.codecomments.com ***
On your publisher connect to your publisher in EM, then go to tools,
replication, configure distributor, publishers, subscribers, click on the
subscriber tab, locate your subscriber, click on the browse button the right
of your subscriber, and in the SQL login enter the sa account and password
of the Publisher. Restart your pull agent.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Darin" <darin_nospam@.nospamever> wrote in message
news:uA7gFbUtFHA.2912@.TK2MSFTNGP09.phx.gbl...
> I cannot get a pull subscription to work. I have created my publication
> to allow anynonomous. The client is a registered subscriber. On the
> subscriber I created the pull subscription always specifying the SQL
> server authentication and entering the login/password.
> I have enabled loggin, but I can't find where it says this is the
> problem.
> The error is:
> The process could not deliver the snapshot to the subscriber. The step
> failed.
> I sure would like more information. I am leaning towards a security
> issue, but the SQL authentication login and password are also setup on
> the server as a user name/password with admin rights.
> THe server is Win2000 running SQL 2000. Client is XP Pro running MSDE.
> THanks.
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***

Pull subscription

Hi,
I created a transactionnal publication with one pull subscription. All
work fine, the transactions are replicated on subscriber. But on the
subscriber, I have two subscriptions under the "Local subscription" in
SQL Server Management Studio with one that don't have a publication
name. I cannot see properties, I get this message :
- SQL Server is unable to complete the operation.
-
- You must manage this subscription from the Publisher because it
shares a Distribution Agent with subscriptions - to other
publications from the same publication database. (Subscription
Properties)
This subscriptions appears after I call
sp_addpullsubscription_agent...
It's normal?I suggest you to post this message to
"microsoft.public.sqlserver.replication"
You'll probably get more answers about this issue there.
--
Ekrem Önsoy
"PPaquin" <patrick.paquin@.gmail.com> wrote in message
news:1189199171.692355.60980@.19g2000hsx.googlegroups.com...
> Hi,
> I created a transactionnal publication with one pull subscription. All
> work fine, the transactions are replicated on subscriber. But on the
> subscriber, I have two subscriptions under the "Local subscription" in
> SQL Server Management Studio with one that don't have a publication
> name. I cannot see properties, I get this message :
> - SQL Server is unable to complete the operation.
> -
> - You must manage this subscription from the Publisher because it
> shares a Distribution Agent with subscriptions - to other
> publications from the same publication database. (Subscription
> Properties)
> This subscriptions appears after I call
> sp_addpullsubscription_agent...
> It's normal?
>|||Thanks, I do...
On 7 sep, 17:20, Ekrem =D6nsoy <ek...@.btegitim.com> wrote:
> I suggest you to post this message to
> "microsoft.public.sqlserver.replication"
> You'll probably get more answers about this issue there.
> --
> Ekrem =D6nsoy
> "PPaquin" <patrick.paq...@.gmail.com> wrote in message
> news:1189199171.692355.60980@.19g2000hsx.googlegroups.com...
>
> > Hi,
> > I created a transactionnal publication with one pull subscription. All
> > work fine, the transactions are replicated on subscriber. But on the
> > subscriber, I have two subscriptions under the "Local subscription" in
> > SQL Server Management Studio with one that don't have a publication
> > name. I cannot see properties, I get this message :
> > - SQL Server is unable to complete the operation.
> > -
> > - You must manage this subscription from the Publisher because it
> > shares a Distribution Agent with subscriptions - to other
> > publications from the same publication database. (Subscription
> > Properties)
> > This subscriptions appears after I call
> > sp_addpullsubscription_agent...
> > It's normal... Masquer le texte des messages pr=E9c=E9dents -
> - Afficher le texte des messages pr=E9c=E9dents -

Pull replication vs. DTS package

What will be better approach (pull replication or DTS package) in
following case?
Case:
Sql Server 2005 database (1) will have data created by small
application (all data will go only to one table),
This data has to be used by legacy application that uses Sql Server
2000 (2) database.
Transactional push replication will be set from server (2) to server
(1) to update some tables that small application will use for lookup
data.
We can't set push replication from server (1) to server (2) because of
location of these servers, server (1) can't "see" server (2), but
server (2) can "see" server (1).
Will appreciate any help in selecting better approach.
Gail
Not too sure I can follow your topology, but if the choice is between
transactional replication and DTS for a single table and single subscriber,
then I'd probably go for transactional replication. This'll allow just
application of data changes so you won't have to drop all the data each
time. The table will remain available (online) during synchronization. There
will be lower latency. Also, you can easily see what changes are waiting to
be delivered.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Pull Agent: Process Could Not Connect To Subscriber

OK, with a tip from ChrisR I got the first problem fixed (I hope). Now, I have
another problem. I have created a pull subscription on a second server, say
SERVERB, to get the data from the first server, say SERVERA. Every time I try to
run this pull subscription I get the following message:
The process could not connect to Subscriber 'NEWSERVERB'.
Then it fails every time. Funny thing to me is that then name of the subscriber
in this message is my subscriber server with 'NEW' on the front. Questions:
Where does that name come from? Why is it trying to connect to my subscriber?
What the heck is going on?
Thanks!
Hi Darrell,
It looks like '-Subscriber NEWSERVERB' might have been accidentally added to
the command line for starting the replication agent. You can find out the
replication agent command line by doing a select from msdb..sysjobsteps.
Merge agent job steps will have a subsystem value of 'REPL-MERGE' whereas
distribution agent job steps will have a subsystem value of
'REPL-DISTRIBUTION'.
-Raymond
"Darrell" wrote:

> OK, with a tip from ChrisR I got the first problem fixed (I hope). Now, I have
> another problem. I have created a pull subscription on a second server, say
> SERVERB, to get the data from the first server, say SERVERA. Every time I try to
> run this pull subscription I get the following message:
> The process could not connect to Subscriber 'NEWSERVERB'.
> Then it fails every time. Funny thing to me is that then name of the subscriber
> in this message is my subscriber server with 'NEW' on the front. Questions:
> Where does that name come from? Why is it trying to connect to my subscriber?
> What the heck is going on?
> Thanks!
>
|||Dude, thanks! I thought I had changed that in the steps of all jobs. I must have
missed one or more of the steps. Thanks again.
Raymond Mak [MSFT] wrote:[vbcol=seagreen]
> Hi Darrell,
> It looks like '-Subscriber NEWSERVERB' might have been accidentally added to
> the command line for starting the replication agent. You can find out the
> replication agent command line by doing a select from msdb..sysjobsteps.
> Merge agent job steps will have a subsystem value of 'REPL-MERGE' whereas
> distribution agent job steps will have a subsystem value of
> 'REPL-DISTRIBUTION'.
> -Raymond
> "Darrell" wrote:
>

publishing a ssrs2005 reprot on a 2000 system

Hello everyone!
Does anyone know if you can depoly a report created in SSRS2005 environment
on a SQL Server 2000 report server?
Thanks!
AmedeoHi
No, the RDL is different between the 2 versions.
Regards
--
Mike
This posting is provided "AS IS" with no warranties, and confers no rights.
"Amedeo Feroce" <aferoce@.akdhc.com> wrote in message
news:O8Obr1klGHA.5044@.TK2MSFTNGP02.phx.gbl...
> Hello everyone!
> Does anyone know if you can depoly a report created in SSRS2005
> environment on a SQL Server 2000 report server?
> Thanks!
> Amedeo
>

Publication takes record off subscriber

When I synch my subscriber back to my maste. A record I created on the
subscriber is now on the master but it is not also on the subscriber
like it should be. Any ideas? Everything seems to be in order.
Never mind. Those above me decided to add filters without telling me.
Thanks for taking the time to read this.
On Thu, 28 Apr 2005 16:09:14 -0600, Shane Lim <gslim@.blizzardice.com>
wrote:

>When I synch my subscriber back to my maste. A record I created on the
>subscriber is now on the master but it is not also on the subscriber
>like it should be. Any ideas? Everything seems to be in order.

Publication script error

Hello,
I am creating Publication through sql script. I have created Publication on
my machine using wizard and after that I created the script for the
publication. When I am running this script on another sql server it is giving
me an error saying Distributor not configured properly. What I need to do to
remove this error? Can this problem be solved by running some sql script?
Becoz I am creating all this through Installshield. So I need the script of
this. Please Help...
Sounds like replication is not installed on this server. Go to tools,
replication, enable replication and follow the prompts accepting the
defaults.
"Subin" <Subin@.discussions.microsoft.com> wrote in message
news:567DC900-D413-4769-916C-E24FF90B9A0E@.microsoft.com...
> Hello,
> I am creating Publication through sql script. I have created Publication
> on
> my machine using wizard and after that I created the script for the
> publication. When I am running this script on another sql server it is
> giving
> me an error saying Distributor not configured properly. What I need to do
> to
> remove this error? Can this problem be solved by running some sql script?
> Becoz I am creating all this through Installshield. So I need the script
> of
> this. Please Help...

Publication not enabled to use an independent agent

I've created a snapshot replication between 2 databases on 2 different
servers to run once a day. The snapshot has worked but when the
distribution job runs it fails within a few seconds. I've looked at the
job history and the following error message is recorded:
Publication 'EmailDB' is not enabled to use an independent agent. The
step failed.
I think this may be because I've defined the publication so that
anonymous pull subscriptions are not allowed. If not does anyone know
what the problem could be. If it is how do I alter the publication so
that they are allowed - the option doesn't appear to be changeable with
the publication properties window in EM.
TIA
Laurence Breeze
drop your subscriptions and try this
sp_changepublication 'pubs4','independent_agent','true'
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Laurence Breeze" <laurence_breeze@.yahoo.co.uk> wrote in message
news:4289AD77.5070305@.yahoo.co.uk...
> I've created a snapshot replication between 2 databases on 2 different
> servers to run once a day. The snapshot has worked but when the
> distribution job runs it fails within a few seconds. I've looked at the
> job history and the following error message is recorded:
> Publication 'EmailDB' is not enabled to use an independent agent. The
> step failed.
> I think this may be because I've defined the publication so that
> anonymous pull subscriptions are not allowed. If not does anyone know
> what the problem could be. If it is how do I alter the publication so
> that they are allowed - the option doesn't appear to be changeable with
> the publication properties window in EM.
> TIA
> Laurence Breeze
>

publication include new tables created automatically?

Hi All,
I have a merge replication on a SQL 2000 database to a remote site.
I have selected "publish all" in publication properties. Now if I a new
table is created, does it automatically runs the snapshot agent and include
that table in to the table schema?
Thanks in advance for the answer... :-)
Maani...
Using sp_addmergearticle followed by running the snapshot agent and merge
agents should be enough.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Public Synonym?

Hi,

I am an Oracle Developer and just started working on a SQL Server database. I created a view and gave ALL rights to PUBLIC and my supervisor. However, when my supervisor logs on as herself she can see the query (in Query Analyzer) but she can't select data from it.

In Oracle I typically have to create a public synonym so users can use an object without specifying the owner of that object. Does the same apply in SQL Server and if so, how do I create a public synonym?

Thanks,
KDoes that login have access to the database - and within that database does public have "select" rights ? When you manage the permissions for the view do you see that login and if so click on "select" rights.|||Did you create your view in your own schema? (as in user.viewname)

Basically, MS goes through a routine for each table on each query. Suppose you issue:

select * from table

SQL Server first looks for username.table where username is your username. If that fails, SQL Server than looks for dbo.table. If that fails, then an error is returned. Because of that first lookup, it is suggested that you supply the owner of the table for queries that are run many many times per hour. The first lookup is not too work intensie, but if you do it a million times an hour...

As for a public synonym, you have to create a view as dbo.view. Then anyone can query it as just select * from view (provided they have no view or table of trhe same name in their own schema).