Showing posts with label pulled. Show all posts
Showing posts with label pulled. Show all posts

Monday, March 26, 2012

push table only on handheld database

I'm able to pull down all my tables needed, but I need to push a table from my handheld database that was not pulled. Is this possible?

The table is used to save data on some input screen on my handheld application and I need to push it to a 'staging' table on my main sql server before it is inserted into the correct tables.

Is there a way to do this?

Why not use RDA.SubmitSQL("INSERT INTO xxx ....) ?|||

SubmitSQL("insert xxx") will work?

So the insert statement will be the insertion of the table on my main SQL Server? I've been under the impression that you can't push a table unless you pull it first? Is that not true?

So here is what I have.

on my handeld database

table1 - pulled

table2 - not pulled

main SQL Server database

table1

table2 - 'staged table'

since table2 wasn't not pulled and is used as a data collection table on the handheld, I can do SubmitSQL("insert into table2 (xxx)") and that will work?

|||Yes, SubmitSQL simply executes SQL statements on the database server, any you can code whatever SQL statements you like.

push table only on handheld database

I'm able to pull down all my tables needed, but I need to push a table from my handheld database that was not pulled. Is this possible?

The table is used to save data on some input screen on my handheld application and I need to push it to a 'staging' table on my main sql server before it is inserted into the correct tables.

Is there a way to do this?

Why not use RDA.SubmitSQL("INSERT INTO xxx ....) ?|||

SubmitSQL("insert xxx") will work?

So the insert statement will be the insertion of the table on my main SQL Server? I've been under the impression that you can't push a table unless you pull it first? Is that not true?

So here is what I have.

on my handeld database

table1 - pulled

table2 - not pulled

main SQL Server database

table1

table2 - 'staged table'

since table2 wasn't not pulled and is used as a data collection table on the handheld, I can do SubmitSQL("insert into table2 (xxx)") and that will work?

|||Yes, SubmitSQL simply executes SQL statements on the database server, any you can code whatever SQL statements you like.sql

Tuesday, March 20, 2012

pulling single lines from a DB

hi im making a page where i want a single line at a time to be pulled from my MS Database, basically at the moment i have a list of questions, but the page is displaying all the questions from my database, i only want it to pull out 1 and then if the user clicks the true button then it goes to another page and displays another question?

Any ideas

Regards,

JoeHi Joe,

Are you want to retrieve any 1 question from DB randomly?
FYI:http://www.datawebcontrols.com/faqs/Data/ReturningDataInRandomOrder.shtml

Regards,

Monday, March 12, 2012

Pull Subscription Continues to Run Indefinitely

I have a publication that is being pulled and when I execute a UPDATE command
example: UPDATE Oils SET Description = 'This is a description'
The SQL Query Analyzer completes the command successfully.
I am receiving confirmation that more than 30,0000 rows have been updated
when I run this command.
When I go to the Replication Manager and view the Subscription it continues
to run indefinitely.
In some cases more than 8 hrs.
Are there some parameters that might need to be set when running this
process?
Any feedback is appreciated.
Thank you
open up profiler on the subscriber and see if there is any activity from the
replication process.
"BSandia" <BSandia@.discussions.microsoft.com> wrote in message
news:2B137D55-AD5A-4E61-9D77-9CB0DDF5C1B9@.microsoft.com...
>I have a publication that is being pulled and when I execute a UPDATE
>command
> example: UPDATE Oils SET Description = 'This is a description'
> The SQL Query Analyzer completes the command successfully.
> I am receiving confirmation that more than 30,0000 rows have been updated
> when I run this command.
> When I go to the Replication Manager and view the Subscription it
> continues
> to run indefinitely.
> In some cases more than 8 hrs.
> Are there some parameters that might need to be set when running this
> process?
> Any feedback is appreciated.
> Thank you
>
>
>
|||There are several optimization techniques for transactional replication one
half is to create a new distribution agent profile with a lower amount of
transactions set per commit, and the second half is to add [-MaxCmdsInTran
10000] to the log reader agent where 10000 is the maximum number of commands
per transaction. With this switch added to the execution command in the
actual log reader agent you will only send 10000 commands down the
replication pipe per transaction. The combination of these two performance
enhancements will reduce that 8 hour run to quite a bit smaller.
"BSandia" wrote:

> I have a publication that is being pulled and when I execute a UPDATE command
> example: UPDATE Oils SET Description = 'This is a description'
> The SQL Query Analyzer completes the command successfully.
> I am receiving confirmation that more than 30,0000 rows have been updated
> when I run this command.
> When I go to the Replication Manager and view the Subscription it continues
> to run indefinitely.
> In some cases more than 8 hrs.
> Are there some parameters that might need to be set when running this
> process?
> Any feedback is appreciated.
> Thank you
>
>
>
|||Thank you for your responsive posts I will give them a try.
Brett
"Richard S. Hale" wrote:
[vbcol=seagreen]
> There are several optimization techniques for transactional replication one
> half is to create a new distribution agent profile with a lower amount of
> transactions set per commit, and the second half is to add [-MaxCmdsInTran
> 10000] to the log reader agent where 10000 is the maximum number of commands
> per transaction. With this switch added to the execution command in the
> actual log reader agent you will only send 10000 commands down the
> replication pipe per transaction. The combination of these two performance
> enhancements will reduce that 8 hour run to quite a bit smaller.
> "BSandia" wrote:

Pull replication errors...

Hi,
the idea is to setup an offsite backup of our single sql server, have
created a publication on the MASTER server, and pulled it to the offsite
server using FTP, downloaded snapshot, replicated transactions, all appeared
to work, generated schema, but the frontend database app didnt run, loads of
various errors showing up.
decided to restore the database from disk to the backup server, to check the
app is working fine, which it now is, so all i need to do is replicated the
changes in the tables on the master server to the offsite server, only needs
to be one-way, the offsite is only for backup read only...changed the
publication to tables only, re-created snapshot and now get errors saying...
Cannot update identity column. The step failed
help please on solution or other ways to achive this.
comment the identity column update in the update proc.
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
"Matt" <mattnj@.hotmail.com> wrote in message
news:d9tqpf$gkn$1@.news.freedom2surf.net...
> Hi,
> the idea is to setup an offsite backup of our single sql server, have
> created a publication on the MASTER server, and pulled it to the offsite
> server using FTP, downloaded snapshot, replicated transactions, all
> appeared to work, generated schema, but the frontend database app didnt
> run, loads of various errors showing up.
> decided to restore the database from disk to the backup server, to check
> the app is working fine, which it now is, so all i need to do is
> replicated the changes in the tables on the master server to the offsite
> server, only needs to be one-way, the offsite is only for backup read
> only...changed the publication to tables only, re-created snapshot and
> now get errors saying...
> Cannot update identity column. The step failed
> help please on solution or other ways to achive this.
>