Showing posts with label app. Show all posts
Showing posts with label app. Show all posts

Wednesday, March 28, 2012

No Factory?

I've tried all the things needed to load a provider. It does create an entry by putting this into App.config:

<system.data>
<DbProviderFactories>
<add name="Sql Everywhere Data Provider"
invariant="System.Data.SqlServerCe"
description=".NET Framework Data Provider for Microsoft SQL
Everywhere CTP Edition 3.1"
type="System.Data.SqlServerCe.SqlServerCeFactory,
System.Data.SqlServerCe, Version=9.0.242.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91"/>
</DbProviderFactories>
</system.data>

However, it fails to load when I call DbProviderFactories.GetFactory("System.Data.SqlServerCe");

The root cause: In the SQL Everywhere dll, System.Data.SqlServerCe.dll,
there appears to be no class such as SqlServerCeFactory. Nor anything
like unto it was found in the object browser.

Is this true? If so, it really sucks. What happened to SQL Everywhere
being compatible with the full .Net 2.0 framework?


Nathan

The type in the above Machine.Config entry is wrong. Please have a look at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=674426&SiteID=17

Thanks,

Laxmi

Tuesday, March 20, 2012

NLB Web App accessing Cluster SQL 2005

Hello Friends
I have a project that will use Failover Cluster for SQL 2005 and NLB for the
web server front-end (using IIS).
That web application will be developed in-house. there are any special
programming considerations that the programmers must embed in the application
in order to support the special features of Failover and NLB clusters?
Does the web App Server must be Cluster-Aware to interact to SQL 2005
Failover Cluster?
Can you please give me any links to some documents that reflect these
situations?
Thanks for Help
Bruno
No. If it can connect to the SQL Server, you are set for the application.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
> the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
> application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno
|||Any SQL client application can connect to a SQL Cluster with no changes. I
recommend using non-persistent connections so the web app can recover in
case of a cluster failover, but that has been general programming practice
for a while now. Your NLB session model and the application session model
will need to work together. I.E. if you only support local sessions in IIS,
you will need to make sure your NLB sessions are "sticky". Your Network
Engineer can help with this.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
> the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
> application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno
|||You need to have reconnect logic built into the application. Whenever a
failover occurs, you will loose connectivity. The advantage of this
solution, however, is that the failover happens automatically, and is
relatively brief.
On the NLB, you need to program "stateless" apps. That is, you can not
guarantee that recovered session are redirect to the same web server during
each pass. If only one server is aware of the state, you find the user
orphaned if redirected to one of the other servers.
Also, to keep your solution clean and to harden security, consider using
some sort of middleware, either through dedicated application hosts, or some
sort of messaging platform.
Sincerely,
Anthony Thomas

"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno

Monday, March 12, 2012

Next step after Access?

I've been an Access user for years designing and running desktop database
app's. My work, however, has taken the size of my Access databases to half a
million records and 1.5GB. Access completely crawls at this level.
Furthermore, I need to perform more statistical analysis that Access seems to
be designed for. I feel like I'm needing to take the next step in database
usage. Unfortunately, there don't seem to be any other "desktop" database
app's that are significantly more capable than Access. Thus, I'm guessing I
need to bite the bullet and begrudgingly buy and learn the server /
enterprise database software. What would be the best one to ease into for a
MS Access user like me? Would it be MS SQL Server Personal, for instance?
What's the learning curve like for an Access user? And finally, will it run
on a desktop computer running Windows XP?Bill_S wrote:
> I've been an Access user for years designing and running desktop
> database app's. My work, however, has taken the size of my Access
> databases to half a million records and 1.5GB. Access completely
> crawls at this level. Furthermore, I need to perform more statistical
> analysis that Access seems to be designed for. I feel like I'm
> needing to take the next step in database usage. Unfortunately,
> there don't seem to be any other "desktop" database app's that are
> significantly more capable than Access. Thus, I'm guessing I need to
> bite the bullet and begrudgingly buy and learn the server /
> enterprise database software. What would be the best one to ease
> into for a MS Access user like me? Would it be MS SQL Server
> Personal, for instance? What's the learning curve like for an Access
> user? And finally, will it run on a desktop computer running Windows
> XP?
Personal Edition only exists as an add-on for Standard/EE/and Developer.
You can download the MS Data Engine (MSDE) - which is essentially a
stripped down version of SQL Server 2000 without any client tools and a
2GB limit on database size. It may not take you very far, given you're
already at 1.5GB, but at least it's free. You can download the MS Web
Data Administrator to help manage the database.
If this is a development project, you can purchase Developer Edition
from MS for about $50. It's obviously not licensed for use in
production.
You'll need to read about SQL Server to get started. There are number of
good web sites (sqlserverperformance.com, SQLServerCentral.com, etc).
Get a book as well - I prefer Kalen Delaney's Inside SQL Server 2000 -
MS Press.
David Gugick
Imceda Software
www.imceda.com

Saturday, February 25, 2012

newbie: True and False 0 and 1?

Hi,
I have an MSDE 2000 SP3a running on Win2k3, problem I have is that I am
writing a little basic web app. One of the fields I have set to bit
which I assumed I would use for True or False (1 or 0) - Using
Dreamweaver it seems that when I check a field in order to set it to
"true" it seems to have a value of -1 in the table? Why is this? Can
anyone shed some light for me
cheers
Baronne
On 11 Mar 2005 07:56:29 -0800, Baronne wrote:

>I have an MSDE 2000 SP3a running on Win2k3, problem I have is that I am
>writing a little basic web app. One of the fields I have set to bit
>which I assumed I would use for True or False (1 or 0) - Using
>Dreamweaver it seems that when I check a field in order to set it to
>"true" it seems to have a value of -1 in the table? Why is this? Can
>anyone shed some light for me
Hi Baronne,
The BIT datatype is not boolean. It is numeric, with only the values 0
and 1 allowed. Some people use BIT to represent booleans, but you'll
have to convert true to 1 (or 0) and false to 0 (or 1), and back again,
when going to and from the database.
Since SQL Server has no boolean datatype, you can pick wahtever you
want. I usually use a CHAR(1) datatype, with a CHECK constraint to make
sure that only 'T' or 'F' are allowd (or 'Y' / 'N' - depending on the
specific case).
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)