I realize that a raw web request may be like using a sledgehammer to
crack an egg, but in my case, I am using this as a small test platform
to exercise the Raven-SQL Index replication to get a sense of timing
for the latency between the last insert of a batch and the time it
takes for the index to return from stale status and in the process
complete the replication to SQL Server. This is just so that for
reporting services I can set the expectation that the reporting
solution will be asynchronous and that best/worst case, my reports
will be x hours or minutes behind the Raven Transactional DB.
I use a SQL Server stored procedure to basically build a string that
represents the document format I want to work with, then I fill in the
relevant values in the document from a SQL Server table and store the
final result in one final table. In this way I can precreate a batch
of documents of whatever size I need and then my command line app
reads these documents from SQL and inserts them into Raven via the web
request.
Thanks again for your assistance here and hopefully this may help
others coming from more of a traditional RDBMS DBA background.
Colm
On May 2, 1:07 am, "Oren Eini (Ayende Rahien)" <
aye...@ayende.com>
wrote:
>
http://localhost:8080/databases/TENANT_NAMEis the root that you want to
> work with.
>
> GEThttp://localhost:8080/databases/Northwind/docs/
> people/6CFCE938-8ABE-4927-8F6F-C46ACFCDC8F4
>
> Etc.
>
> why are you working with raw web request, though?
>
> On Wed, May 2, 2012 at 2:06 AM, SQLServerDBARavenNewbie <
>
>
>
>
>
>
>
>
colm.ho...@gmail.com> wrote:
> > Values for variables used below,
> > -- docId - docs/people/6CFCE938-8ABE-4927-8F6F-C46ACFCDC8F4
> > -- ravenUrlhttp://localhost:8080