Exactly. I was using it for an audit log but querying was basically
impossible. I migrated it all to a Basic SQL Azure database and it now is
works perfectly.
On Tue, Jun 7, 2016 at 11:00 AM, David Connors wrote:
> On Tue, 7 Jun 2016 at 10:09 Craig van Nieuwkerk wrote:
>
>> I agree with these
On Tue, 7 Jun 2016 at 10:09 Craig van Nieuwkerk wrote:
> I agree with these points. It is slow enough to be unusable unless you are
> *very
> *careful when designing the initial tables.
>
I am not sure what design is possible when you have one key and can select
by that key.
It is a hang over
>
> And here is a list of caveats for table storage:
>
Depending which side of the mirror you're looking through, many of your
caveats may be considered blessings, especially the "no enforced schema".
The absence of the features you listed is what makes the ATS API so
mercifully simple and useful i
I agree with these points. It is slow enough to be unusable unless you
are *very
*careful when designing the initial tables.
On Tue, Jun 7, 2016 at 9:46 AM, David Connors wrote:
> On Mon, 6 Jun 2016 at 23:00 Greg Keogh wrote:
>
>> I forgot to mention ... don't forget Azure Table Storage! I've b
Perfect for the government then lol
On Tue, Jun 7, 2016 at 9:46 AM, David Connors wrote:
> On Mon, 6 Jun 2016 at 23:00 Greg Keogh wrote:
>
>> I forgot to mention ... don't forget Azure Table Storage! I've been
>> really loving it recently and using it where a SQL Db would be overkill.
>> The AP
On Mon, 6 Jun 2016 at 23:00 Greg Keogh wrote:
> I forgot to mention ... don't forget Azure Table Storage! I've been really
> loving it recently and using it where a SQL Db would be overkill. The API
> is dead simple, vast capacity, cheap, and build and runtime dependencies
> are trivial -- *GregK
>
> Greg, am I correct in thinking azure table storage is only a cheaper
> option when the number of reads is light? Preet mentions he will need
> reporting and depending on how heavy those are hit azure table storage
> could get expensive.
>
Hmmm! I'm not sure as my demands have only reached the
Greg, am I correct in thinking azure table storage is only a cheaper option
when the number of reads is light? Preet mentions he will need reporting
and depending on how heavy those are hit azure table storage could get
expensive.
On Mon, Jun 6, 2016 at 10:59 PM, Greg Keogh wrote:
> For the DB I
>
> For the DB I suspect the latest entity framework will be sufficient but am
>>> open to ideas about other technologies that might not have been present
>>> when I last worked with it 5 years ago.
>>>
>>> This service will only be used in house, but might be housed in the
>>> cloud and security i
>
> It's seems to me that a restful one would be the simplest in terms of
> usage for all the clients (various tools and programs within the
> organisation).
>
> Personally I find them easier to work with when coding to them as clients,
> and I'll be writing the first client for this service too.
>
Thank you. I'll be managing the DB and it's a simple time recording store
that will be reported on using BI/Excel tools so practically trivial.
In terms of data a simple SQL Server Express/Local DB will be more that
enough - so I think a hosted SQL instance will be sufficient. Having spent
4 years
AFAIK not much has changed. I've been out of the area for a while too.
Start with web api and only go to wcf if web api is insufficient which I
doubt it will be.
DB side can depend on many things as you know like if you have an existing
db you need to use, who manages the db (dba?), amount of dat
It's seems to me that a restful one would be the simplest in terms of usage
for all the clients (various tools and programs within the organisation).
Personally I find them easier to work with when coding to them as clients,
and I'll be writing the first client for this service too.
regards,
Pre
Have you decided on the style you need: SOAP and XML, or RESTful? -- *GK*
On 6 June 2016 at 21:20, Preet Sangha wrote:
> I've been out of .net Web stuff for many years and now need to build a
> webservice with a sql backend. I've seen many posts on here from you guys
> going web stuff and wonder
I've been out of .net Web stuff for many years and now need to build a
webservice with a sql backend. I've seen many posts on here from you guys
going web stuff and wondered if you could point me in the right direction
please?
If I wanted to build .net based web cased service, would I need to use
15 matches
Mail list logo
