"gregory_may" <None> wrote in message
news:OAFynzJGGHA.2064@TK2MSFTNGP09.phx.gbl...
>I am developing a small application that needs quick access to about 12
>Megs of data.  This 12 Megs of data is mastered in another application.
>So, my app needs to refresh from the source every 1/2 hour or so.  But,
>there is really no risk of data loss if the DB dies ... just functionally
>loss.
>
> So, I was thinking about using SQL Express edition for this project.
> Since the data doesn't need to be backed up and the user queries are a
> simple select off a key'd table.
>
> Does anyone have any feedback on Express edition in a production
> environment?
>

"Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message
news:%23RbpcNKGGHA.1088@tk2msftngp13.phx.gbl...
> Sounds perfect for Express.  By the way just because Express does not have
> a job scheduler does not mean you can't back it up. It still has most of
> the functionality of the other editions, especially when it comes to
> things like that.
>
> --
> Andrew J. Kelly  SQL MVP
>
>
> "gregory_may" <None> wrote in message
> news:OAFynzJGGHA.2064@TK2MSFTNGP09.phx.gbl...
>>I am developing a small application that needs quick access to about 12
>>Megs of data.  This 12 Megs of data is mastered in another application.
>>So, my app needs to refresh from the source every 1/2 hour or so.  But,
>>there is really no risk of data loss if the DB dies ... just functionally
>>loss.
>>
>> So, I was thinking about using SQL Express edition for this project.
>> Since the data doesn't need to be backed up and the user queries are a
>> simple select off a key'd table.
>>
>> Does anyone have any feedback on Express edition in a production
>> environment?
>>
>
>