>Greetings -
>
>Several of you were helpful in disuading me from using Jet in a prior post.
>
>I'm developing an application that needs a "person manager" attached to it,
>with typical interfaces like "add person" "edit person" "get list of people"
>plus some custom items.
>
>A few questions. 
>
>I'm experienced in relational database design, access and .net, but not at
>all in sql server:
>
>1. How steep is the learning curve on SQL Server?
>
>2. Any suggestions for good materials on getting started (most of the
>documentation looks geared to those who are proficient with prior versions)
>
>3. Any suggestions for how I can find a third party to get me started on
>this -- most of the solution providers listed online seem to be looking to do
>large turnkey packages.  I'd be looking more for some part time development
>and mentoring consulting to get this launched and then back in my hands.  Any
>ideas where I can find this (I'm just outside of NYC, fwiw).

"kcamhi" <kca***@discussions.microsoft.com> wrote in message
news:63302227-CA64-4B4F-B53B-0EF38D47D59F@microsoft.com...
> Greetings -
>
> Several of you were helpful in disuading me from using Jet in a prior
> post.
>
> I'm developing an application that needs a "person manager" attached to
> it,
> with typical interfaces like "add person" "edit person" "get list of
> people"
> plus some custom items.
>
> A few questions.
>
> I'm experienced in relational database design, access and .net, but not at
> all in sql server:
>
> 1. How steep is the learning curve on SQL Server?
>>>> SQL Server (especially SQL Express) is simple to install--far easier
>>>> than ever. However, consider that it (like many serious tools) has lots
>>>> of features that you might never need. I councel my readers to stick to
>>>> simple designs. Visual Studio is closely integrated with SQL Server and
>>>> the Express edition so many of the basic operations are built into the
>>>> UI.
>
> 2. Any suggestions for good materials on getting started (most of the
> documentation looks geared to those who are proficient with prior
> versions)

>>>>> I would suggest my new book but it won't be ready until Summer. I
>>>>> agree, many of the help topics and books assume quite a bit. I'm
>>>>> writing as fast as I can but it's a big job. The new book is designed
>>>>> for those just getting started so I have to fill in a lot of cracks
>>>>> before it's right.
>
> 3. Any suggestions for how I can find a third party to get me started on
> this -- most of the solution providers listed online seem to be looking to
> do
> large turnkey packages.  I'd be looking more for some part time
> development
> and mentoring consulting to get this launched and then back in my hands.
> Any
> ideas where I can find this (I'm just outside of NYC, fwiw).

>>> I would try to attend one of the conferences like VSLive (Boston is
>>> nearby). I'll be speaking there and hopefully they'll offer one of my
>>> ADO.NET workshops that should get you started. I don't plan to do much
>>> mentoring until I get done with the book. I also suggest you lookup your
>>> local .NET User Group. There will be pleanty of people there that can
>>> help or point you in the right direction. I'm an INETA speaker so
>>> perhaps your UG can invite me out there to talk.

>
> Thanks for any pointers/suggestions!
>
> kc
>
>

"Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> wrote in message
news:emaWSiEEGHA.3200@tk2msftngp13.phx.gbl...
> Kcamhi,
>
> Just start, MSDN is full of samples, in fact it is SQLSever easier to use
> in Net than OleDB because it has less exceptions.
>
> A problem that exist with SQL Express is at the moment no maintenance
> tool, which makes it for newbies more trouble full. However that the tool
> not yet exist does not make it more helpful for you if you have a book
> which describes the SQL maintenance tool.
>
> With Full SQL sever 2005 it is just intall and start and use the SQL
> Server management Studio, that is less complex (because of the way it was
> done, although 6.5 was the worst and it became better and better) than all
> previous versions were for that.
>
> Just my thought,
>
> Cor
>
>
>

"Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> wrote in message
news:uQCMuLTEGHA.1816@TK2MSFTNGP11.phx.gbl...
> Bill,
>
> I had seen it, however did not know if it was working so thanks for your
> information (I had mentioned all in an other message, however because that
> I did not know the status I did skip it here).
>
> Are you going to cover it in one of your books? In my opinion can that be
> a great addition especial for all those going from Access to SQL.
>
> Cor
>
>

"kcamhi" wrote:

> Greetings -
>
> Several of you were helpful in disuading me from using Jet in a prior post.
>
> I'm developing an application that needs a "person manager" attached to it,
> with typical interfaces like "add person" "edit person" "get list of people"
> plus some custom items.
>
> A few questions. 
>
> I'm experienced in relational database design, access and .net, but not at
> all in sql server:
>
> 1. How steep is the learning curve on SQL Server?
>
> 2. Any suggestions for good materials on getting started (most of the
> documentation looks geared to those who are proficient with prior versions)
>
> 3. Any suggestions for how I can find a third party to get me started on
> this -- most of the solution providers listed online seem to be looking to do
> large turnkey packages.  I'd be looking more for some part time development
> and mentoring consulting to get this launched and then back in my hands.  Any
> ideas where I can find this (I'm just outside of NYC, fwiw).
>
> Thanks for any pointers/suggestions!
>
> kc
>
>