Noob question(s)

I am used to using SQL Server 2000 and am just learning about MSDE 2000.
I'm on XP Pro, latest everything
Using VS .Net 2003 (latest framework, et cetera)
I've installed (correctly) the MSDE Toolkit Release Candidate
I've built a test deployment app (from the readme.htm) and it works just
fine
Now, I've got some (probably stupid) basic questions.
(1)With SQL Server 2000 (which is also installed on my dev machine) I have
had to configure the service to auto start via the service manager. How
does this happen with MSDE? I mean, treating my machine as a test
deployment machine, do I need to trigger its startup or configure it (post
installation) with osql.exe commands>
(2)My instance name given to the setup application was MSDETestInstall and I
wanted to know how can I check for the service being correctly configured
and/or available? (Question 1 may answer this.)
(3)If not answered by question 1, does my application need to startup the
MSDE instance each time it is run (and should also shut it down as the
license stipulates that only my application(s) can make use of this instance
of MSDE)?
(4)Is there a subsection of the 'Books Online' docs that deals specifically
with MSDE because I've been unable to locate it. Perhaps there is
supplementary documentation elsewhere?
Thanks everyone, hope those questions weren't astonishingly stupid (I'd
settle for just plain stupid)
WTH
For #1 and #2 and #3, to auto start SQL, just go into Control Panel |
Administrative Tools | Services and set MSSQLServer (and MSSQLSERVERAgent)
to Automatic. It will start when the computer does. You can also assign it
to a service account. Multiple instances of SQL will show up as
MSSQL$instance name, and you should be able to connect it to as
computer_name\instance_name.
Most of MSDE is SQL 2000 so it will be covered by the books online at
http://www.microsoft.com/sql/downloads/default.asp. The limitations of MSDE
can be found at
http://www.microsoft.com/sql/msde/pr...o/features.asp
and from there you can link around to find licensing information and such.
Good luck.
************************************************** *****************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
************************************************** *****************
"WTH" <spamsucks@.Ih8it.com> wrote in message
news:usOJ4VgMEHA.2244@.tk2msftngp13.phx.gbl...
> I am used to using SQL Server 2000 and am just learning about MSDE 2000.
> I'm on XP Pro, latest everything
> Using VS .Net 2003 (latest framework, et cetera)
> I've installed (correctly) the MSDE Toolkit Release Candidate
> I've built a test deployment app (from the readme.htm) and it works just
> fine
> Now, I've got some (probably stupid) basic questions.
> (1)With SQL Server 2000 (which is also installed on my dev machine) I have
> had to configure the service to auto start via the service manager. How
> does this happen with MSDE? I mean, treating my machine as a test
> deployment machine, do I need to trigger its startup or configure it (post
> installation) with osql.exe commands>
> (2)My instance name given to the setup application was MSDETestInstall and
I
> wanted to know how can I check for the service being correctly configured
> and/or available? (Question 1 may answer this.)
> (3)If not answered by question 1, does my application need to startup the
> MSDE instance each time it is run (and should also shut it down as the
> license stipulates that only my application(s) can make use of this
instance
> of MSDE)?
> (4)Is there a subsection of the 'Books Online' docs that deals
specifically
> with MSDE because I've been unable to locate it. Perhaps there is
> supplementary documentation elsewhere?
> Thanks everyone, hope those questions weren't astonishingly stupid
(I'd
> settle for just plain stupid)
> WTH
>
sql

Nonconvergence issue after upgrading MSDE to SQL 2005 Express

I'm experiencing an intermittent issue with merge replication after
upgrading one of the subscribers to SQL 2005 Express from MSDE 2000.
Here are a few details about the environment before I describe the
issue
1. Originally was SQL 2000 Standard Publisher with MSDE 2000
Subscribers all SP4
2. Upgraded (in place) Publisher to SQL 2005 Standard SP1 - no issues
3. Upgraded 1 of 3 subscribers to SQL 2005 Express SP1 encountered the
following issue only on the upgraded Express installation
4. Merge replication is running continuously as a pull subscription
with column-level tracking
5. Replication is running as a scheduled task on the subscriber (pull)
by executing replmerg.exe
Issue:
Background: A contacts table has addresses stored in a separate table
with the address_id in the contacts table referencing the address_id
in the addresses table
1. Contact created on subscriber without an address (null address_id)
2. Replication runs (contact uploaded to publisher)
3. Contact updated at subscriber to have an address (address_id
populated)
4. Replication uploads changes to publisher
4a. The address is uploaded to the publisher
4b. The address_id update to the contact record appears to be uploaded
to the publisher (confirmed by running SQL profiler)
4c. After the replication session is complete the address_id update to
the contact record appears to have not been made or is rolled back
5. Replication downloads changes to the subscriber and determines that
the address is not part of the partition for the subscriber (because
the address_id is not present in the contact record) and removes it
from the subscriber (the address is still present on publisher)
If I were to bet on a theory about why the address_id update to the
contact record is getting lost I would put my money on a deadlock (or
similar issue) and rollback but I would be interested to hear if
anyone has run into similar issues. I'd also be interested to know why
SQL 2005 Express would behave differently when replicating than MSDE
2000 (this setup has been running for almost 2 years on the MSDE with
no issues). If it is a deadlock/rollback then does the MSDE subscriber
handle the rollback differently than the Express subscriber? Is there
a re-try step that is not running in Express that does run in MSDE?
Have you logged to an output file or run profiler to determine exactly what
is happening?
If it is a deadlock the merge agent is transactional in nature and will put
the error in a retry loop at the end of each batch.
So this doesn't really explain what you are seeing.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Brian Fell" <brianfell@.gmail.com> wrote in message
news:1182807685.623799.115710@.u2g2000hsc.googlegro ups.com...
> I'm experiencing an intermittent issue with merge replication after
> upgrading one of the subscribers to SQL 2005 Express from MSDE 2000.
> Here are a few details about the environment before I describe the
> issue
> 1. Originally was SQL 2000 Standard Publisher with MSDE 2000
> Subscribers all SP4
> 2. Upgraded (in place) Publisher to SQL 2005 Standard SP1 - no issues
> 3. Upgraded 1 of 3 subscribers to SQL 2005 Express SP1 encountered the
> following issue only on the upgraded Express installation
> 4. Merge replication is running continuously as a pull subscription
> with column-level tracking
> 5. Replication is running as a scheduled task on the subscriber (pull)
> by executing replmerg.exe
>
> Issue:
> Background: A contacts table has addresses stored in a separate table
> with the address_id in the contacts table referencing the address_id
> in the addresses table
> 1. Contact created on subscriber without an address (null address_id)
> 2. Replication runs (contact uploaded to publisher)
> 3. Contact updated at subscriber to have an address (address_id
> populated)
> 4. Replication uploads changes to publisher
> 4a. The address is uploaded to the publisher
> 4b. The address_id update to the contact record appears to be uploaded
> to the publisher (confirmed by running SQL profiler)
> 4c. After the replication session is complete the address_id update to
> the contact record appears to have not been made or is rolled back
> 5. Replication downloads changes to the subscriber and determines that
> the address is not part of the partition for the subscriber (because
> the address_id is not present in the contact record) and removes it
> from the subscriber (the address is still present on publisher)
>
> If I were to bet on a theory about why the address_id update to the
> contact record is getting lost I would put my money on a deadlock (or
> similar issue) and rollback but I would be interested to hear if
> anyone has run into similar issues. I'd also be interested to know why
> SQL 2005 Express would behave differently when replicating than MSDE
> 2000 (this setup has been running for almost 2 years on the MSDE with
> no issues). If it is a deadlock/rollback then does the MSDE subscriber
> handle the rollback differently than the Express subscriber? Is there
> a re-try step that is not running in Express that does run in MSDE?
>
|||On Jun 25, 10:06 pm, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
> Have you logged to an output file or run profiler to determine exactly what
> is happening?
> If it is a deadlock the merge agent is transactional in nature and will put
> the error in a retry loop at the end of each batch.
> So this doesn't really explain what you are seeing.
> --
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com"Brian Fell" <brianf...@.gmail.com> wrote in message
> news:1182807685.623799.115710@.u2g2000hsc.googlegro ups.com...
>
>
>
>
> - Show quoted text -
I ran profiler and saw no evidence of any problem however I do see the
update with the address_id in it (and an entry that indicated that
replication thought the upload was successful (Uploaded 2 change(s) in
''contacts'' (1 insert, 1 update) - one of those for the address entry
as well). Unfortunately, it took me three weeks to catch this thing
with profiler and I didn't have the replication logging to a file when
I started it up that day (was switching back and forth between
watching the console and reviewing a log). Any ideas about something
to look at would be greatly appreciated.
Thanks,
Brian Fell
|||You will probably have to try to repro the problem using the specific set of
commands you outline in your original post.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Brian Fell" <brianfell@.gmail.com> wrote in message
news:1182824624.031896.140300@.o61g2000hsh.googlegr oups.com...
> On Jun 25, 10:06 pm, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
> I ran profiler and saw no evidence of any problem however I do see the
> update with the address_id in it (and an entry that indicated that
> replication thought the upload was successful (Uploaded 2 change(s) in
> ''contacts'' (1 insert, 1 update) - one of those for the address entry
> as well). Unfortunately, it took me three weeks to catch this thing
> with profiler and I didn't have the replication logging to a file when
> I started it up that day (was switching back and forth between
> watching the console and reviewing a log). Any ideas about something
> to look at would be greatly appreciated.
> Thanks,
> Brian Fell
>

No trusted SQl connection

Hello,
I am using the MSDE from Visual Studio.NET. I can access the SQL Server from
the server explorer only if I am logged into 2000 as administrator (I
installed MSDE using admin). If I try to connect from another login on the
same machine, I get the following error "Login failed. Not associated with a
trusted SQL Server connection". Any ideas?
Thanks,
Rick
hi Rick,
"rick_md" <rick_mc_806@.msn.com> ha scritto nel messaggio
news:CrqdnTC2aJqMiPLcRVn-qA@.comcast.com
> Hello,
> I am using the MSDE from Visual Studio.NET. I can access the SQL
> Server from the server explorer only if I am logged into 2000 as
> administrator (I installed MSDE using admin). If I try to connect
> from another login on the same machine, I get the following error
> "Login failed. Not associated with a trusted SQL Server connection".
> Any ideas?
that means that your non admin Windows account is not a regitered and
authorizated login to access SQL Server...
you have to log in as administrator and grant all non admin Windows account
privilege to access SQL Server
have a look at
http://support.microsoft.com/default...N-US;q325003#8
a good article about security you should read can be found at
http://support.microsoft.com/default...b;en-us;325022
we are here referring to Windows authentication...
if you like to log in in your MSDE instance using SQL Server authentication,
providing "User" and "pasword" credential, you have to modify the
authentication mode to Mixed mode..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply