do process

how can I do
perform a stored procedure with paramert from my client application but my q
uestion is sent call but transfer process to sqlserver a for example i can c
lose my application but process continue running in a sqlserver until finiss
hed, similar a job but with
out job.
Thank You
AlfSome environments and providers (e.g. .NET) will allow you to make a stored
procedure call asynchronous, meaning it does not have to wait for the
result.
So, it is hard to say if your client application can do that, because you
forgot to tell us anything about your client application.
A
<ag> wrote in message news:%23iXkfN6QGHA.4740@.TK2MSFTNGP14.phx.gbl...
> how can I do
>
> perform a stored procedure with paramert from my client application but my
> question is sent call but transfer process to sqlserver a for example i
> can close my application but process continue running in a sqlserver until
> finisshed, similar a job but without job.
> Thank You
> Alf
>

Do locks slow other processes?

Hi,
Lets say I have a process running on the server (e.g a stored proc) -
Process A
Then another scheduled process starts to run but is locked up by process A.
Will process A run any slower as it's holding up the second process, or,
does it not affect the performance at all?
Basically, I'm quite happy for the second process to have to wait - but - I
don't want the performance to be radically slowed.
ThanksLondon
http://www.sql-server-performance.com/reducing_locks.asp
"London Developer" <dev@.nowhere.com> wrote in message
news:OSO5ge8lDHA.744@.tk2msftngp13.phx.gbl...
> Hi,
> Lets say I have a process running on the server (e.g a stored proc) -
> Process A
> Then another scheduled process starts to run but is locked up by process
A.
> Will process A run any slower as it's holding up the second process, or,
> does it not affect the performance at all?
> Basically, I'm quite happy for the second process to have to wait - but -
I
> don't want the performance to be radically slowed.
> Thanks
>|||Process A should not be slowed by processes which are waiting on A.
Offcourse if there are more processes which are running or claiming memory,
process A can get slowed. A waiting process should consume very little (or
no) cpu. It is offcourse in a list of processes so the OS uses a very very
VERY small amount of CPU to check or pass over this process when
rescheduling, SQL-server has to set a wait on a lock this consumes very VERY
VERY small amount of cpu.
Offcourse if the process which is blocked by A holds locks and process A
needs those resources you wil have a deadlock. This holds both processes
till a deadlock is detected, one process is 'aborted' the other can
continue.
ben brugman
"London Developer" <dev@.nowhere.com> wrote in message
news:OSO5ge8lDHA.744@.tk2msftngp13.phx.gbl...
> Hi,
> Lets say I have a process running on the server (e.g a stored proc) -
> Process A
> Then another scheduled process starts to run but is locked up by process
A.
> Will process A run any slower as it's holding up the second process, or,
> does it not affect the performance at all?
> Basically, I'm quite happy for the second process to have to wait - but -
I
> don't want the performance to be radically slowed.
> Thanks
>sql

Do i need to Fully process the CUBE, if Structural change to fact table happens

I have a requirement.
I have a CUBE in SQL 2000. I need to change the structure of Fact Table and i need to add one more dimension to my CUBE.
What are the problems will arise if i do this. i need to Fully process the CUBE?
PLS help meSQl 2000 - OLAP CUBE

Do I need SSIS to process cube?

There is a function called "proactive caching" in Analysis services. It can:
-Automatic synchronization with the relational database
-No more explicit "cube processing

But I cannot have the latest data in the cube even I set the proactive mode as "real time"

Do I need SSIS to process cube in this case?

Following is the procedures I have done:
1. test the data
1.1 use the bi dev studio to browser the cube, ensure no new data are there
1.2 process the the cube and browser the data, ensure new data are there
1.3 delete new data from source database and reprocess the cube, ensure no new data are there
1.4 add new data again

2. configure the proactive setting of cube
2.1 use sql server management studio to open the cube and open the properties window
2.2 in the option of "proactive caching" select "low-latency MOLAP" (even real-time ROLAP later), then click ok

3. configure the proactive setting of cube
3.1 open the patitions view properties window

3.2 in the option of "proactive caching" select "low-latency MOLAP" (even real-time ROLAP later), then click ok

3.3 in the notification tab, select "sql server " and specifiy tracking tables to the "fact table", which is a view to get data from real fact table.

4. wait a period of time...

5. test the data again
5.1 use the bi dev studio to browser the cube, but no new data are there (even I selected real-time ROLAP later). I even tried the reconnect and refresh options in the tool bar

So my questions are :
1. Did I do the right thing to achieve the target "Automatic synchronization with the relational database "

2. Can I monitor the procedure of synchronization, such as monitoring the log of processing, viewing the schedule setting and status of the process?



Thanks a lot!

You'd be better putting this on the SSAS forum.

-Jamie

|||

Sorry to post to the wrong place. But I did post it to the SSAS yesterday but nobody answered. Since it is urgent for me to solve the problem, I tried to post here.

I just wanted to know whether I should use "proactive caching" or use SSIS to solve the problem. Even a simple answer yes or no will be mostly appreciated.

Thanks!

|||

Well it depends on your requirements.

Using ProActive caching means there is an unknown latency between putting data into the warehouse and it appearing in the cube. But the good thing is you don't have to build extra functionality to do it.

The opposite is true of using SSIS. You process the cube when you need it to but you have to build, maintain and control that extra fucntionality.

Its your choice.

-Jamie

|||

Thanks Jamie.

That means I can use proactive caching to synchronize the data from database? Now the problem is how to make it work. At least I think I am in the right track.So I will put more time on it.

Thanks again.

|||

Sorry, I still cannot work it out. Can anybody help?

Thanks in advance!

DLL issues

Can anybody recall having simmilar messages while running sprocs with trace
turned on:
DBCC TRACEON 260, server process ID (SPID) 52.
2007-10-19 08:41:18.72 spid52 Extended stored procedure DLL
'aegxprocs.dll' does not export __GetXpVersion(). Refer to the topic
"Backward Compatibility Details (Level 1) - Open Data Services" in the
documentation for more information.
2007-10-19 08:41:23.87 spid52 Extended stored procedure DLL
'aegxprocs.dll' does not export __GetXpVersion(). Refer to the topic
"Backward Compatibility Details (Level 1) - Open Data Services" in the
documentation for more information.
2007-10-19 08:41:33.75 spid52 DBCC TRACEOFF 260, server process ID (SPID)
52.
ThanksHi
From: http://msdn2.microsoft.com/en-us/library/ms164627.aspx
When SQL Server is started with the trace flag -T260 or if a user with
system administrator privileges runs DBCC TRACEON (260), and if the extended
stored procedure DLL does not support __GetXpVersion(), a warning message
(Error 8131: Extended stored procedure DLL '%' does not export
__GetXpVersion().) is printed to the error log. (Note that __GetXpVersion()
begins with two underscores.)
As I don't seem to have this DLL I would assume it is a third party product
which may need updating?
John
"dk" wrote:
> Can anybody recall having simmilar messages while running sprocs with trace
> turned on:
> DBCC TRACEON 260, server process ID (SPID) 52.
> 2007-10-19 08:41:18.72 spid52 Extended stored procedure DLL
> 'aegxprocs.dll' does not export __GetXpVersion(). Refer to the topic
> "Backward Compatibility Details (Level 1) - Open Data Services" in the
> documentation for more information.
> 2007-10-19 08:41:23.87 spid52 Extended stored procedure DLL
> 'aegxprocs.dll' does not export __GetXpVersion(). Refer to the topic
> "Backward Compatibility Details (Level 1) - Open Data Services" in the
> documentation for more information.
> 2007-10-19 08:41:33.75 spid52 DBCC TRACEOFF 260, server process ID (SPID)
> 52.
> Thanks
>|||Hi John,
Thanks for your reply. Yes, it's third party dll (epicor financials).
THanks again
Dk
"John Bell" wrote:
> Hi
> From: http://msdn2.microsoft.com/en-us/library/ms164627.aspx
> When SQL Server is started with the trace flag -T260 or if a user with
> system administrator privileges runs DBCC TRACEON (260), and if the extended
> stored procedure DLL does not support __GetXpVersion(), a warning message
> (Error 8131: Extended stored procedure DLL '%' does not export
> __GetXpVersion().) is printed to the error log. (Note that __GetXpVersion()
> begins with two underscores.)
> As I don't seem to have this DLL I would assume it is a third party product
> which may need updating?
> John
>
> "dk" wrote:
> > Can anybody recall having simmilar messages while running sprocs with trace
> > turned on:
> > DBCC TRACEON 260, server process ID (SPID) 52.
> > 2007-10-19 08:41:18.72 spid52 Extended stored procedure DLL
> > 'aegxprocs.dll' does not export __GetXpVersion(). Refer to the topic
> > "Backward Compatibility Details (Level 1) - Open Data Services" in the
> > documentation for more information.
> > 2007-10-19 08:41:23.87 spid52 Extended stored procedure DLL
> > 'aegxprocs.dll' does not export __GetXpVersion(). Refer to the topic
> > "Backward Compatibility Details (Level 1) - Open Data Services" in the
> > documentation for more information.
> > 2007-10-19 08:41:33.75 spid52 DBCC TRACEOFF 260, server process ID (SPID)
> > 52.
> > Thanks
> >
> >

Dividing the sale amount by month

Hello,

I want to process a row from a source table by dividing the sales amount in that row over the period of the sale by month.

For instance if an item is sold for 500$ and it's duration is 5 months from 1/15/2004 till 6/15/2004, I want to divide the sale amount by month as follows:

Month 1: 50$

Month 2: 100$

Month 3: 100$

Month 4: 100$

Month 5: 100$

Month 6: 50$

I know I can create a script component and do the calculation for each month and insert 6 records in the fact table for each row in the source table, where each record holds the amount for the corresponding month. However I was wondering if there is another technique that utilizes the components of SSIS to do it more efficiently.

Thanks,

Grace

Its definately possible but I would say if you've already figured out how to do it in script component why bother trying to do it elsewhere? I doubt you'd be able to do it more efficiently either!

-Jamie

|||

Thanks Jamie,

I just wanted to confirm my method. I always tend to think that script component is not much efficient especially when i'm using it to open connection to the database and insert multiple rows. It is faster when SQL Destination is used. But in my case i can't use the destination component.

Grace

|||

There's no problem with perf of the script component. It is compiled code (different from DTS) so it is very quick!

-Jamie

Distribution of SQLServer Database

Hi,
We're in the process of developing a .NET application which will use a
SQLServer database. When installed/deployed the application will query this
database. I assume each time the application is installed the SQL Server
database will need to be installed. Is this the case - sorry I know it's a
dumb question but I am a complete SQL Server novice. If this is the case then
which licensing option should we go for?
Any help would be greatly appreciated.
-Kim
Hi Kim
There is a version of SQL Server which is designed to be deployed with user
programs. It's called MSDE & you can read more about it here:
http://msdn.microsoft.com/library/de...ar_ts_67ax.asp
There are limits on it's growth (2Gb per db, max 2 CPUs etc) & if you exceed
these, you'd probably be looking at SQL Server Standard Edition.
Regards,
Greg Linwood
SQL Server MVP
"kim d" <kimd@.discussions.microsoft.com> wrote in message
news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> Hi,
> We're in the process of developing a .NET application which will use a
> SQLServer database. When installed/deployed the application will query
> this
> database. I assume each time the application is installed the SQL Server
> database will need to be installed. Is this the case - sorry I know it's a
> dumb question but I am a complete SQL Server novice. If this is the case
> then
> which licensing option should we go for?
> Any help would be greatly appreciated.
> -Kim
|||It also depends on what you mean about deplying SQL... YOu might wish all of
the clients to share data from a single database, or you might wish to
install the MSDE version on each client, so there is no data sharing...
In either case, at least you will have to the the SQL Connectivity piece on
the client.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"kim d" <kimd@.discussions.microsoft.com> wrote in message
news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> Hi,
> We're in the process of developing a .NET application which will use a
> SQLServer database. When installed/deployed the application will query
this
> database. I assume each time the application is installed the SQL Server
> database will need to be installed. Is this the case - sorry I know it's a
> dumb question but I am a complete SQL Server novice. If this is the case
then
> which licensing option should we go for?
> Any help would be greatly appreciated.
> -Kim
|||Ideally clients would share data from a single database but there would be
the capability to work 'off-line' - in other words users could access the
database even while not explicitly connected to the server. I presume in this
case it would require a separate MSDE installation on each client as well as
on the server database. Does MSDE support this type of behaviour?
"Wayne Snyder" wrote:

> It also depends on what you mean about deplying SQL... YOu might wish all of
> the clients to share data from a single database, or you might wish to
> install the MSDE version on each client, so there is no data sharing...
> In either case, at least you will have to the the SQL Connectivity piece on
> the client.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "kim d" <kimd@.discussions.microsoft.com> wrote in message
> news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> this
> then
>
>
|||Great, so does this mean that we would only need to purchase a SQLServer
developers license?
"Greg Linwood" wrote:

> Hi Kim
> There is a version of SQL Server which is designed to be deployed with user
> programs. It's called MSDE & you can read more about it here:
> http://msdn.microsoft.com/library/de...ar_ts_67ax.asp
> There are limits on it's growth (2Gb per db, max 2 CPUs etc) & if you exceed
> these, you'd probably be looking at SQL Server Standard Edition.
> Regards,
> Greg Linwood
> SQL Server MVP
> "kim d" <kimd@.discussions.microsoft.com> wrote in message
> news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
>
>
|||In this case, you'd be looking at Personal Edition, which is on the SS
media. Then you replicate the Central Database to your clients, which can
then go "offline."
That's what this edition was created for. It has restrictions, but
different than those of MSDE, which is more an Access database replacement.
SS Personal Edition is more for business, semi-connected users, like sales
staff.
Sincerely,
Anthony Thomas

"kim d" <kimd@.discussions.microsoft.com> wrote in message
news:7E0720DF-6224-4B91-A92E-5D4C542D7FC3@.microsoft.com...
Ideally clients would share data from a single database but there would be
the capability to work 'off-line' - in other words users could access the
database even while not explicitly connected to the server. I presume in
this
case it would require a separate MSDE installation on each client as well as
on the server database. Does MSDE support this type of behaviour?
"Wayne Snyder" wrote:

> It also depends on what you mean about deplying SQL... YOu might wish all
of
> the clients to share data from a single database, or you might wish to
> install the MSDE version on each client, so there is no data sharing...
> In either case, at least you will have to the the SQL Connectivity piece
on[vbcol=seagreen]
> the client.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "kim d" <kimd@.discussions.microsoft.com> wrote in message
> news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> this
a
> then
>
>

Distribution of SQLServer Database

Hi,
We're in the process of developing a .NET application which will use a
SQLServer database. When installed/deployed the application will query this
database. I assume each time the application is installed the SQL Server
database will need to be installed. Is this the case - sorry I know it's a
dumb question but I am a complete SQL Server novice. If this is the case then
which licensing option should we go for?
Any help would be greatly appreciated.
-KimHi Kim
There is a version of SQL Server which is designed to be deployed with user
programs. It's called MSDE & you can read more about it here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_67ax.asp
There are limits on it's growth (2Gb per db, max 2 CPUs etc) & if you exceed
these, you'd probably be looking at SQL Server Standard Edition.
Regards,
Greg Linwood
SQL Server MVP
"kim d" <kimd@.discussions.microsoft.com> wrote in message
news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> Hi,
> We're in the process of developing a .NET application which will use a
> SQLServer database. When installed/deployed the application will query
> this
> database. I assume each time the application is installed the SQL Server
> database will need to be installed. Is this the case - sorry I know it's a
> dumb question but I am a complete SQL Server novice. If this is the case
> then
> which licensing option should we go for?
> Any help would be greatly appreciated.
> -Kim|||It also depends on what you mean about deplying SQL... YOu might wish all of
the clients to share data from a single database, or you might wish to
install the MSDE version on each client, so there is no data sharing...
In either case, at least you will have to the the SQL Connectivity piece on
the client.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"kim d" <kimd@.discussions.microsoft.com> wrote in message
news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> Hi,
> We're in the process of developing a .NET application which will use a
> SQLServer database. When installed/deployed the application will query
this
> database. I assume each time the application is installed the SQL Server
> database will need to be installed. Is this the case - sorry I know it's a
> dumb question but I am a complete SQL Server novice. If this is the case
then
> which licensing option should we go for?
> Any help would be greatly appreciated.
> -Kim|||Ideally clients would share data from a single database but there would be
the capability to work 'off-line' - in other words users could access the
database even while not explicitly connected to the server. I presume in this
case it would require a separate MSDE installation on each client as well as
on the server database. Does MSDE support this type of behaviour?
"Wayne Snyder" wrote:
> It also depends on what you mean about deplying SQL... YOu might wish all of
> the clients to share data from a single database, or you might wish to
> install the MSDE version on each client, so there is no data sharing...
> In either case, at least you will have to the the SQL Connectivity piece on
> the client.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "kim d" <kimd@.discussions.microsoft.com> wrote in message
> news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> > Hi,
> > We're in the process of developing a .NET application which will use a
> > SQLServer database. When installed/deployed the application will query
> this
> > database. I assume each time the application is installed the SQL Server
> > database will need to be installed. Is this the case - sorry I know it's a
> > dumb question but I am a complete SQL Server novice. If this is the case
> then
> > which licensing option should we go for?
> > Any help would be greatly appreciated.
> > -Kim
>
>|||Great, so does this mean that we would only need to purchase a SQLServer
developers license?
"Greg Linwood" wrote:
> Hi Kim
> There is a version of SQL Server which is designed to be deployed with user
> programs. It's called MSDE & you can read more about it here:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_67ax.asp
> There are limits on it's growth (2Gb per db, max 2 CPUs etc) & if you exceed
> these, you'd probably be looking at SQL Server Standard Edition.
> Regards,
> Greg Linwood
> SQL Server MVP
> "kim d" <kimd@.discussions.microsoft.com> wrote in message
> news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> > Hi,
> > We're in the process of developing a .NET application which will use a
> > SQLServer database. When installed/deployed the application will query
> > this
> > database. I assume each time the application is installed the SQL Server
> > database will need to be installed. Is this the case - sorry I know it's a
> > dumb question but I am a complete SQL Server novice. If this is the case
> > then
> > which licensing option should we go for?
> > Any help would be greatly appreciated.
> > -Kim
>
>|||In this case, you'd be looking at Personal Edition, which is on the SS
media. Then you replicate the Central Database to your clients, which can
then go "offline."
That's what this edition was created for. It has restrictions, but
different than those of MSDE, which is more an Access database replacement.
SS Personal Edition is more for business, semi-connected users, like sales
staff.
Sincerely,
Anthony Thomas
"kim d" <kimd@.discussions.microsoft.com> wrote in message
news:7E0720DF-6224-4B91-A92E-5D4C542D7FC3@.microsoft.com...
Ideally clients would share data from a single database but there would be
the capability to work 'off-line' - in other words users could access the
database even while not explicitly connected to the server. I presume in
this
case it would require a separate MSDE installation on each client as well as
on the server database. Does MSDE support this type of behaviour?
"Wayne Snyder" wrote:
> It also depends on what you mean about deplying SQL... YOu might wish all
of
> the clients to share data from a single database, or you might wish to
> install the MSDE version on each client, so there is no data sharing...
> In either case, at least you will have to the the SQL Connectivity piece
on
> the client.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "kim d" <kimd@.discussions.microsoft.com> wrote in message
> news:6DFA23FC-DADB-48A1-BF7B-03EF46AEE5D8@.microsoft.com...
> > Hi,
> > We're in the process of developing a .NET application which will use a
> > SQLServer database. When installed/deployed the application will query
> this
> > database. I assume each time the application is installed the SQL Server
> > database will need to be installed. Is this the case - sorry I know it's
a
> > dumb question but I am a complete SQL Server novice. If this is the case
> then
> > which licensing option should we go for?
> > Any help would be greatly appreciated.
> > -Kim
>
>

Distribution executable running at 100% cpu but doesn't process any transactions

MSSQL Server 2000 SP3a -> MSSQL Server 2000 SP3a
Transactional Replication
Push subscriptions
Transactional replication has been performing well for years between
two servers. I added a new publication to handle some other tables.
Both publications had push subscriptions to our Production and
Development SQL servers. I added an article for a relatively large
table (2,000,000 rows or so) to the second publication and a few days
later the distribution agent seemed to get "stuck" after this new
article was added.
The distribution agent maxes out the CPU, but I don't see any
transactions going through. Nothing appears to be happening in
profiler, and neither the sqlserver nor the distrib.exe processes seem
to be performing any I/O related to replication with the exception of
a very slow incrementing I/O other for distrib.exe.
I killed the push subscription for the second publication and this
fixed the problem for a day or so. However this morning the
publication that has been working fine for months is now creating the
same problem. As a result no transactions are getting through to the
production server.
I've tried running the distrib.exe through the command prompt but it
causes the same issue.
Any advice or guidance?
Thanks!
- Mike
You can bet it will get "stuck" - 2,000,000 rows is a lot of data to push.
I suggest you do DTS it over (create a package for this and use the fast
insert option), and then do a nosync subscription. Ensure you build the
replication stored procedures using sp_scriptcustomprocs.
"Mike" <ngposterMikeBain@.gmail.com> wrote in message
news:ea5d5311.0410210729.264b3427@.posting.google.c om...
> MSSQL Server 2000 SP3a -> MSSQL Server 2000 SP3a
> Transactional Replication
> Push subscriptions
> Transactional replication has been performing well for years between
> two servers. I added a new publication to handle some other tables.
> Both publications had push subscriptions to our Production and
> Development SQL servers. I added an article for a relatively large
> table (2,000,000 rows or so) to the second publication and a few days
> later the distribution agent seemed to get "stuck" after this new
> article was added.
> The distribution agent maxes out the CPU, but I don't see any
> transactions going through. Nothing appears to be happening in
> profiler, and neither the sqlserver nor the distrib.exe processes seem
> to be performing any I/O related to replication with the exception of
> a very slow incrementing I/O other for distrib.exe.
> I killed the push subscription for the second publication and this
> fixed the problem for a day or so. However this morning the
> publication that has been working fine for months is now creating the
> same problem. As a result no transactions are getting through to the
> production server.
> I've tried running the distrib.exe through the command prompt but it
> causes the same issue.
> Any advice or guidance?
> Thanks!
> - Mike

Distribution Agent Process

Hi,
Our replication topology (currently in design) will use transactional
replication to replicate from a OLTP server (publisher) to a Reporting server
(subscriber) in hope of near realtime results. Not all of the tables require
this though and the plan would be to use snapshot replication once a day for
these less updated tables. We’re then going to use log shipping to ship
tranaction log files out to remote servers with the databases originating
from the Reporting server.
My question is what does the distribution agent do to the existing
subscriber tables when it applies the new snapshot files? I guess I’m
looking for information as to whether it TRUNCATES the table, DELETES the
data, or DROPS the table prior to importing the BCP files from the new
snapshot.
SQL 2005 SP1 exclusively will be used in this environment.
Any information would be appreciated.
It depends on what option you set in the article property.
The property you should look for is in the article property under the
destination objects and Action if name is in use
The options, are keep data, drop table, truncate and delete filter data.
"dgcull" <dgcull@.discussions.microsoft.com> wrote in message
news:4A2EAA92-0353-4E83-AAC0-546BD5E0C5B1@.microsoft.com...
> Hi,
> Our replication topology (currently in design) will use transactional
> replication to replicate from a OLTP server (publisher) to a Reporting
> server
> (subscriber) in hope of near realtime results. Not all of the tables
> require
> this though and the plan would be to use snapshot replication once a day
> for
> these less updated tables. We're then going to use log shipping to ship
> tranaction log files out to remote servers with the databases originating
> from the Reporting server.
> My question is what does the distribution agent do to the existing
> subscriber tables when it applies the new snapshot files? I guess I'm
> looking for information as to whether it TRUNCATES the table, DELETES the
> data, or DROPS the table prior to importing the BCP files from the new
> snapshot.
> SQL 2005 SP1 exclusively will be used in this environment.
> Any information would be appreciated.
>
|||Gopal is right, but just to add - the default is to drop the existing table
on the subscriber.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

distribution agent error

Hi all,
I got this error in my distribution agent today it was
The process could not execute '{call sp_MSget_subscription_guid(25)}'
Can anebody tell me what caused the error and also what does the procedure
sp_MSget_subscription_guid actually do.
How can i avoid such errors in future.
Thanks in advance
Jacx
Can you run sp_lock on the subscriber database? See how many locks there
are.
Also enable logging as per this article and post the results back here.
http://support.microsoft.com/kb/312292
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
"Jacx" <Jacx@.discussions.microsoft.com> wrote in message
news:CEC339D5-E3A9-4369-B5D7-1B60854357CB@.microsoft.com...
> Hi all,
> I got this error in my distribution agent today it was
> The process could not execute '{call sp_MSget_subscription_guid(25)}'
> Can anebody tell me what caused the error and also what does the procedure
> sp_MSget_subscription_guid actually do.
> How can i avoid such errors in future.
> Thanks in advance
> Jacx

Distribution Agent - Stored Procedure Error Logging

I know how I can set-up my distribution agent jobs to log them
to a file and up the verbosity of the procedure.
I am in the process of creating snap-shot's of my stored procedures
for replication. The Snapshot agent works just fine, it is
when I use the distribution agent to send it to the subscriber
that it will stop on the first error it finds.
Is there a way to have it run through all the Stored Procedures
so that I don't have to constantly re-create the publication
by removing the first problem sp?
It helps me give the sp's to our developers in one shot
rather than one at a time.
Dave
I think your best bet is to create a separate publication for each stored
procedure. This way the only procs which fail to be replicated are the
problem ones - the remainder will be replicated.
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
"David Gresham" <gresham@.panix.com> wrote in message
news:d62hq1$mar$1@.reader1.panix.com...
> I know how I can set-up my distribution agent jobs to log them
> to a file and up the verbosity of the procedure.
> I am in the process of creating snap-shot's of my stored procedures
> for replication. The Snapshot agent works just fine, it is
> when I use the distribution agent to send it to the subscriber
> that it will stop on the first error it finds.
>
> Is there a way to have it run through all the Stored Procedures
> so that I don't have to constantly re-create the publication
> by removing the first problem sp?
> It helps me give the sp's to our developers in one shot
> rather than one at a time.
>
> Dave
>