Ive been given a query analizer for MSDE are there others

Greetings,

I've been sent an alternative "Query Analizer" thingy to play with and it seems to do the job - but it ain't my area.

I've posted the tool in a free public place for a short time:
http://www.adoanywhere.com/members/yeohray/7C1_SQLTool.zip

But, for the benefit of people reding this from the archives, please follow
the registerable author link [ http://81.130.213.94/myforum/forum_posts.asp?TID=78&PN=1&TPN=1 ]

Apart from needing documentation (we all know about that old scenario) it seems good.

It didn't waste my time (and I wouldn't waste yours I hope). Could I have your comments please ?

Also, I'm looking for other tools that do the same as this one - so I can compare functionality. Even without try the freebie, any links please ?

TIAyou've "been sent"? by whom? where's it from? did you virus-check it?

okay, i tried it (yes, i took a chance, i'm stupid that way)

it actually works nicely -- a damn site better at submitting queries to MSDE than the way i was doing it up till now (via a pass-through query in access)

it's cute, too|||Good point about the security!

I'll address that issue with the author, virus scanners here should have picked them up though.

I got it from a chap I was assisting with some Delphi knowledge.

Thanks for checking it out, I didn't understand all of it myself.|||so, this isn't yours, then? i mean, it isn't adoanywhere's? don't they have something similar? how come you posted it on their forum? do you work for adoanywhere? do they mind you mentioning what appears to be a competing product? just what does their product do, anyway? and where did you say you got this little Delphi app, in case it screws somethying up on my machine and i feel like visiting the said chap at his place of residence with a clue-by-four?

:D|||Ther author was having problems with bugs in Delphi and retrieval of stats & plans through ADO. With adoanywhere forum help he eventually got it resolved and posted the tool for us to play with. I've used it witout problems since it was uploaded but I'll make it clearer in future posts and on the forum that all these third party apps are at downloaders risk.

I work for adoanwyhere - I wrote adoanywhere, and it's no problem adding other tools to forum if you know of any. Glad to 'ave 'em.

Mike (adoanywhere)|||okay, thanks for the clarification

by the way, does your product allow me to run queries against MSDE too?

i should mention i haven't a clue what ADO is (and no particular desire to find out)|||Yeah, you can query MSDE with adoanywhere.

ADO is an interface (bit like ODBC), so you can query databases that have and ADO "driver" - called provider in ado lingo.

Most databses have an ADO provider. Problem is though that ADO has loads of properties are that may or may not be available at any give time in your application.

Adoanywhere lets you fiddle with the ado settings. So although you can query data with it, it does more complex stuff at its heart.

I generally use adoanywhere for querying & checking ado properties - then switch to proprietry tools (like query analizer and Enterprise manager) for database management stuff. Horses for courses as they say.

All the best, Mike.sql

It is possible to install MSDE in a USB memory key?

It is possible to install MSDE in a USB memory key?I think that should work, what I know is that the datafiles can be put
on the USB key. I always showed that example for presenting failover
and recovery functions :-)
HTH, Jens Suessmeyer.
|||Thanks Jens, but I want to "run" MSDE from a USB key (without installing
nothing in the PC). Is this possible?
"Jens" <Jens@.sqlserver2005.de> escribi en el mensaje
news:1128600102.492204.49100@.g44g2000cwa.googlegro ups.com...
>I think that should work, what I know is that the datafiles can be put
> on the USB key. I always showed that example for presenting failover
> and recovery functions :-)
> HTH, Jens Suessmeyer.
>
|||This is really wacky, because the service and the registry will be
edited on the pc. But another thing would be to use a virtual pc on a
usb stick running Windows and MSDE. Not to say that this is very
performant but it works.
HTH, Jens Suessmeyer.
|||Thanks
"Jens" <Jens@.sqlserver2005.de> escribi en el mensaje
news:1128602086.467141.47430@.g49g2000cwa.googlegro ups.com...
> This is really wacky, because the service and the registry will be
> edited on the pc. But another thing would be to use a virtual pc on a
> usb stick running Windows and MSDE. Not to say that this is very
> performant but it works.
> HTH, Jens Suessmeyer.
>
|||Jens wrote:
> This is really wacky, because the service and the registry will be
> edited on the pc. But another thing would be to use a virtual pc on a
> usb stick running Windows and MSDE. Not to say that this is very
> performant but it works.
>
ROTFL
:D:D
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||You are laughing, but did you see this here: :-D ?
http://www.wrightthisway.com/Articles/000154.html
Cheers, Jens Suessmeyer.
|||hi Jens,
Jens wrote:
> You are laughing, but did you see this here: :-D ?
> http://www.wrightthisway.com/Articles/000154.html
>
actually I only have MSDE databases (autoclose striclty true :D:D) on LaCie
USB2 external HD, like http://www.lacie.com/products/product.htm?pid=10655 ,
but not in RAID :D:D
ok... just a note on Virtual... an additional license is required for th OS

Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

ISV using SQL Authentication and a small concern

Hi,
I am an independent software vendor and my app will be deployed on users machine, it will use msde for db needs on clients machine. I am using sql authentication and my app will be connecting to the database using a fixed username and password always, fo
r e.g. sa as user and "myPassword$2" as password. (I know I know that this is not 100% great, but we want to keep things very very simple but dont want windows authentication)
Now, please imagine this situation:
a) small office environment
b) My app installed on three machines.
c) database on 4th machine
d) all 3 users running my app on their individual machines and talking to db.
my concern is, will this scenario work, I mean no matter who the user is, my app logs into msde using sa and "myPassword$2", so will MSDE allow 3 users with same logins to access database at the same time.
Looking forward to hearing from you..
Thanks
Hello,
It is working correctly, but if you want to have some security (for example
a part of the program is not enabled if a user is working on another part,
you will have some problems.). For example, if user 1 has a crash, the
program will still believe that user 1 is still connected. Unless you lock
the tables...
Marc Allard
Allcomp
"dev" <anonymous@.discussions.microsoft.com> a crit dans le message de
news:3C66C1B4-CD85-4473-8B9C-9BF40E84853F@.microsoft.com...
> Hi,
> I am an independent software vendor and my app will be deployed on users
machine, it will use msde for db needs on clients machine. I am using sql
authentication and my app will be connecting to the database using a fixed
username and password always, for e.g. sa as user and "myPassword$2" as
password. (I know I know that this is not 100% great, but we want to keep
things very very simple but dont want windows authentication)
> Now, please imagine this situation:
> a) small office environment
> b) My app installed on three machines.
> c) database on 4th machine
> d) all 3 users running my app on their individual machines and talking to
db.
> my concern is, will this scenario work, I mean no matter who the user is,
my app logs into msde using sa and "myPassword$2", so will MSDE allow 3
users with same logins to access database at the same time.
> Looking forward to hearing from you..
> Thanks
|||Hello, (sorry I was in hollidays)
For example, in our program, when a user is working on a project (Project 1)
, any user can enter a new or a position in Project 1, but no other one
modify the project.
Another user can work with project 2 without any restriction so we can not
lock the full table. We had to write a column str_Wholocked on the Project
table to know that the a specific project is locked.
The problem is that if a user crash, he will not free the wholocked field so
you have to know if a user that has locked a fiel is still connected or not.
To make it, when a user connect in my application, I write his connectionID,
login_time... on a table. After that, I look at all the users connected. If
they have a login_time or connection ID different than the one on my table,
it mean that they have crashed so I can free the wholocked field. I make
this test for every connection and every access to something that can be
locked.
PS : I hope that I am clear enough, if not, please tell me what you don't
understand.
"dev" <anonymous@.discussions.microsoft.com> a crit dans le message de
news:765961A8-8196-4B6F-B87A-228DDB63F1F9@.microsoft.com...
> Allcomp please elaborate my what you mean by saying "but if you want to
have some security (for example
> a part of the program is not enabled if a user is working on another part,
you will have some problems.)."
> Thanks
sql

Issues/Problems with SQL MSDE running on Windows XP

Can anyone tell me if there are known problems/issues with running SQL MSDE
on Windows XP? We have a wise install program that installs an Excel
application with msde and it runs fine on Windows 2000 but not on XP. The
install program completes fine but when we go to view the database we find
that the SQL Server instance is there with the msdb, model, and other default
system databases but none of the databases that the install script creates.
When the same installation is ran on 2000 everything works beautifully.
Any help greatly appreciated!
Thanks,
Ang
This is likely an issue with your installation program and not with MSDE.
MSDE works just fine with XP. Contact your application vendor.
-Andrew
"Angela" <Angela@.discussions.microsoft.com> wrote in message
news:E0E98FDB-4923-4CE0-9E1F-D2F8733B4B79@.microsoft.com...
> Can anyone tell me if there are known problems/issues with running SQL
> MSDE
> on Windows XP? We have a wise install program that installs an Excel
> application with msde and it runs fine on Windows 2000 but not on XP. The
> install program completes fine but when we go to view the database we find
> that the SQL Server instance is there with the msdb, model, and other
> default
> system databases but none of the databases that the install script
> creates.
> When the same installation is ran on 2000 everything works beautifully.
> Any help greatly appreciated!
> Thanks,
> Ang

Issues with MSDE after installing WMSDE, WSUS

I have a stable 3rd party application which has been running on MSDE Sp3 (ver
2000.80.760.0) as the default instance. I installed WSUS, which apparently
uses WMSDE (version 2000.80.884.0), as a named instance. After this
installation I noticed that the original SQL server has a memory leak,
consuming the resources of the server over a few hours.
I upgraded (replaced) the Sp3 default instance with Sp4 (version
2000.80.2039.0). Howeveer the problem seems to be continuing. Is it wise to
have these 2 different database versions running on the same machine or
should I separate/amalgamate them?
TIA
hi,
Lance wrote:
> I have a stable 3rd party application which has been running on MSDE
> Sp3 (ver 2000.80.760.0) as the default instance. I installed WSUS,
> which apparently uses WMSDE (version 2000.80.884.0), as a named
> instance. After this installation I noticed that the original SQL
> server has a memory leak, consuming the resources of the server over
> a few hours.
> I upgraded (replaced) the Sp3 default instance with Sp4 (version
> 2000.80.2039.0). Howeveer the problem seems to be continuing. Is it
> wise to have these 2 different database versions running on the same
> machine or should I separate/amalgamate them?
> TIA
WMSDE is a modified version of MSDE that enables db size larger then 2gb per
database, that is one of the constraints/limitations of "standard" MSDE, and
is provided for SharePoint, AFAIK..
unfortunately no sp4 for this edition has still been provided, even if it
has been promised...
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

Issues upgrading MSDE to SP4

Hello I'm having some issues upgrading MSDE sp3 to MSDE sp4. I don't
see anything in the log file of any importance, no return value 3 just
an occasional 2 which is interesting because I'm not canceling. The
only error I can find is in the application log:
Event Type:Warning
Event Source:MsiInstaller
Event Category:None
Event ID:1015
Date:6/14/2005
Time:1:41:48 PM
User:domain\user
Computer:servername
Description:
Failed to connect to server. Error: 0x800401F0
I am part of the system administrators role so should be able to
contact the database. I did stop all of the services prior to
beginning the install so that I would not have to reboot in order for
the upgrade to go through. This is a production machine and I can't
afford downtime nor any reboots.
Thanks in advance for your help.
Also this is not a named instance and I have already attempted to use
the proper MSP file to accomodate the upgrade.
|||hi,
Kewlhand wrote:
> Hello I'm having some issues upgrading MSDE sp3 to MSDE sp4. I don't
> see anything in the log file of any importance, no return value 3 just
> an occasional 2 which is interesting because I'm not canceling. The
> only error I can find is in the application log:
> Event Type: Warning
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 1015
> Date: 6/14/2005
> Time: 1:41:48 PM
> User: domain\user
> Computer: servername
> Description:
> Failed to connect to server. Error: 0x800401F0
> I am part of the system administrators role so should be able to
> contact the database. I did stop all of the services prior to
> beginning the install so that I would not have to reboot in order for
> the upgrade to go through. This is a production machine and I can't
> afford downtime nor any reboots.
> Thanks in advance for your help.
please have a look at http://tinyurl.com/bwrvv if helps
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||none of those keys exist with those parameters. Thanks for the info
though. If you've got anything else I'd love to hear it.
Thanks.
Kewlhand
|||I too am experiencing this issue. I've found that on two systems
running XP SP2 that I can connect to the SQL server using SQLDMO, but
not using Enterprise Manager over a remote TCP/IP connection.
I also am seeing this on both systems' Application Event Logs when MSDE
starts:
SuperSocket info: ConnectionListen(Shared-Memory (LPC)) : Error 5.
and
SuperSocket info: (SpnRegister) : Error 1355.
Both systems report the same MSDE version:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
I'm pressed for time, so I'll be backing up data and reinstalling MSDE
then SP4 on the two machines, but any tips for the future would be
greatly appreciated.
Kind regards,
Jordan.
Kewlhand wrote:
> none of those keys exist with those parameters. Thanks for the info
> though. If you've got anything else I'd love to hear it.
> Thanks.
> Kewlhand

Issue with Identity Columns after replication Changes

Dear all,

We have an application that use merge replication between MSDE and Devices with SQL CE.

Due to a major application changes, we have to change our replication on all our workstation. Our process is the following:

- drop current replication

- recreate our replication

After first check our replication seems to work but after some test we have identify that all identity ranges have been reset on the workstation. As side effect, device start to reuse existing range and also existing value in the range.

- Have you ever encounter this type of issue?

- What can create it?

- Is our approach fully inappropriate?

Please let me know if you need more information,

Best regards,

I have a client (SQL2000<->SqlCE) that is experiencing similar problems. We have been unable to determine a cause as yet.

Symptoms:

-"duplicate key on insert" errors during replication for one table (two subscribers appearing to be sharing the same number range)

-"duplicate key on insert" error with a back-end process inserting data into a publisher table (diff to the one above)

The tables are using automatic identity range management and have been synchronising happily for a long time prior to this.

Does anyone know of any actions that might cause the automatic identity range management to go screwy like this?

|||You can try re-adjusting your identity ranges, look at sp_adjustpublisheridentityrange. Otherwise i'm not sure what could have caused the issue, maybe someone manually reset the identity seed on the dbs?

Issue with Identity Columns after replication Changes

Dear all,

We have an application that use merge replication between MSDE and Devices with SQL CE.

Due to a major application changes, we have to change our replication on all our workstation. Our process is the following:

- drop current replication

- recreate our replication

After first check our replication seems to work but after some test we have identify that all identity ranges have been reset on the workstation. As side effect, device start to reuse existing range and also existing value in the range.

- Have you ever encounter this type of issue?

- What can create it?

- Is our approach fully inappropriate?

Please let me know if you need more information,

Best regards,

I have a client (SQL2000<->SqlCE) that is experiencing similar problems. We have been unable to determine a cause as yet.

Symptoms:

-"duplicate key on insert" errors during replication for one table (two subscribers appearing to be sharing the same number range)

-"duplicate key on insert" error with a back-end process inserting data into a publisher table (diff to the one above)

The tables are using automatic identity range management and have been synchronising happily for a long time prior to this.

Does anyone know of any actions that might cause the automatic identity range management to go screwy like this?

|||You can try re-adjusting your identity ranges, look at sp_adjustpublisheridentityrange. Otherwise i'm not sure what could have caused the issue, maybe someone manually reset the identity seed on the dbs?

Issue restoring database

I'm running into a problem restoring a database to MSDE.
Actually, osql reports RESTORE DATABASE successfully
worked but when I view the database from enterprise
manager it tells me the database is still "loading..."
Any suggestions?
Sounds like you are using NORECOVERY with the RESTORE command. This will
leave the database expecting additional restores.
Jim
"Tim" <tim.huenke@.ngc.com> wrote in message
news:0f9c01c4dee6$ebe38f60$a401280a@.phx.gbl...
> I'm running into a problem restoring a database to MSDE.
> Actually, osql reports RESTORE DATABASE successfully
> worked but when I view the database from enterprise
> manager it tells me the database is still "loading..."
> Any suggestions?