Showing posts with label experience. Show all posts
Showing posts with label experience. Show all posts

Monday, March 26, 2012

MSDE 2000 on XP help...

Hello all, im new here and do not have no experience with sql. I am trying to install a tax software that I need to run my little business. When I install it gets to a popint that it asks me for my SQL server usernme and password. I remember doing this last year and I reinstalled MSDE and set up a username and password. I seem to not remember what I used, i tried all that I would have but can not get past that step.

I remember adding some lines in the setup,ini file when I installed it last year. Now I can go ahead and reinstall it again and set up a new one, but will the uninstalling and reinstalling of MSDE affect my previous software from last year? Its the same software but I need this years installed.

I have tried using sa as the username and a blank password, with a password and others that I have read up on, still cant log on. Keep getting worng credential screen.

Is there a way to get that info, i doubt it or else it would not be secure, or can I just simply reinstall MSDE?

Many thanks!!

Forget MSDE. Use Sql Server Express instead. It's much easier:http://www.microsoft.com/sql/editions/express/default.mspx

|||

If you are going to uninstall and reinstall it again, you will be loosing all the data that is there from the previous year. So if you are ok with that , you can go ahead and reinstall it.

Also, since you are using a application, the application needs to store the access details some where, may be in registry or INI or something like that, so check for that or ask the maker of the software to send you the details about where the Server details are stored by the application. Then, you can open them up and find the details.

|||

Yeah thats the thing, I don't want to loose the data. OK, so I will talk to them and see what they can help me with. Thanks.

|||

Well don't know anything about sql, msde, all i know is that the program asks for the login credentials when its installing, other than that, I don't mess with MSDE.

sql

Saturday, February 25, 2012

msdb recreate cause replication problems

We just went through a nasty experience whereby we had to recreate the
MSDB database.
System is now back, but replication is completely messed up. Is there a
way to get all the MS* tables back, in the MSDB? I tried to de-install
and install Replication, but that doesn't seem to generate all the
required tables and procs
SQL2005, SP1.
Any help much appreciated!
I take it you mean you want your jobs to pick up where they left off.
Dropping and recreating the publications and subscriptions should do that.
If you mean the replication table in msdb, they are created there when you
install sql server.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
<renedevries@.gmail.com> wrote in message
news:1159994716.013545.158270@.i3g2000cwc.googlegro ups.com...
> We just went through a nasty experience whereby we had to recreate the
> MSDB database.
> System is now back, but replication is completely messed up. Is there a
> way to get all the MS* tables back, in the MSDB? I tried to de-install
> and install Replication, but that doesn't seem to generate all the
> required tables and procs
> SQL2005, SP1.
> Any help much appreciated!
>
|||Eventually called MS Tech Support. The goal was to het replication
working at all, never mind the jobs or the previous state. But since
all relevant tables in msdb where gone, the whole thing was in limbo
The only REAL option is indeed a fresh install of SQL. However, they
where able to help me out, though a number of steps which involved
removing repliation from the database, dropping the distribution db,
and some other assorted trickery. But eventually we got it to work.
Turns out that if you re-create the distribution database all the
associated msdb tables and jobs are also recreated. Fortunately ;)
Lesson: make sure you keep good, validated backups of msdb at all
times. Bitten once again
Rene
Hilary Cotter schreef:

> I take it you mean you want your jobs to pick up where they left off.
> Dropping and recreating the publications and subscriptions should do that.
> If you mean the replication table in msdb, they are created there when you
> install sql server.
> --