Hi,
I have a DTS package that I would like to execute from an application
that uses MSDE as it's back end. Is it possible to 'attach' a DTS
package to an MSDE database and execute it from Say example VB.Net.
Any info will be appreciated.
Thanks,
VaughnIf you save a DTS package as VBScript, you should be able to run that
package from a .NET application.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
<vaughn.haybittle@.gmail.com> wrote in message
news:1157129984.437055.7530@.e3g2000cwe.googlegroups.com...
> Hi,
> I have a DTS package that I would like to execute from an application
> that uses MSDE as it's back end. Is it possible to 'attach' a DTS
> package to an MSDE database and execute it from Say example VB.Net.
> Any info will be appreciated.
> Thanks,
> Vaughn
>sql
Showing posts with label application. Show all posts
Showing posts with label application. Show all posts
Friday, March 30, 2012
MSDE Advice Please
Hi I am planning a desktop application I want to develop in C# and I was thinking about using MSDE instead of an Access database. I have never used of even looked into MSDE before. Do you simply create a database on SQL Server add your tables and Sp's, setup your conection and program against this as normal, then with the install of the software setup MSDE and install the tables and SP's etc into the instance of MSDE?
TIAFrom my experience MSDE has some limitations (db size, number of connections, etc.) but it is real database engine with all features. You can manage it by ISQL or OSQL (if you have installed somewhere in NET enterprise manager - you can use it for MSDE).|||Hi,
The database size is limited to 2GB. Once the DB gets to this size MSDE will not allow the program to use it. You can still go into the DB with Enterprise Manager or Query Analyzer or shareware tools. But nothing will run.
As for connections I beleive the limit is 30.
As for your install.
Create the database on the SQL server and write your program against it. Then back the database up when you are finished debugging it. Include it with your install packaging (I am not a developer so I won't tell you how).
When the install process starts have the MSDE install first (See MS Knowledge Base or google "MSDE install"). Then restore the database to the MSDE ( I suggest osql). Then create your ODBC connection. And finish with your program.
Have fun !|||Thanks for all your comments and advise :)
TIAFrom my experience MSDE has some limitations (db size, number of connections, etc.) but it is real database engine with all features. You can manage it by ISQL or OSQL (if you have installed somewhere in NET enterprise manager - you can use it for MSDE).|||Hi,
The database size is limited to 2GB. Once the DB gets to this size MSDE will not allow the program to use it. You can still go into the DB with Enterprise Manager or Query Analyzer or shareware tools. But nothing will run.
As for connections I beleive the limit is 30.
As for your install.
Create the database on the SQL server and write your program against it. Then back the database up when you are finished debugging it. Include it with your install packaging (I am not a developer so I won't tell you how).
When the install process starts have the MSDE install first (See MS Knowledge Base or google "MSDE install"). Then restore the database to the MSDE ( I suggest osql). Then create your ODBC connection. And finish with your program.
Have fun !|||Thanks for all your comments and advise :)
MSDE 7.0 and SQL2000
Can you install SQL2000 on a server with an application
that is using MSDE 7.0 which was installed with the
software ?
If you can, what is the best way to do so without it
affecting the previous installation of MSDE 7.0 ?Yes you can. BE aware, though, that MDAC on the machine will be upgraded to 2.6 (if not or higher
already), so make sure you test the app for that MDAC version.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Valencia" <vahorda@.hotmail.com> wrote in message news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
> Can you install SQL2000 on a server with an application
> that is using MSDE 7.0 which was installed with the
> software ?
> If you can, what is the best way to do so without it
> affecting the previous installation of MSDE 7.0 ?
>|||Thank you Tibor. I checked the version of MDAC and it is
2.5.
>--Original Message--
>Yes you can. BE aware, though, that MDAC on the machine
will be upgraded to 2.6 (if not or higher
>already), so make sure you test the app for that MDAC
version.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Valencia" <vahorda@.hotmail.com> wrote in message
news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
>> Can you install SQL2000 on a server with an application
>> that is using MSDE 7.0 which was installed with the
>> software ?
>> If you can, what is the best way to do so without it
>> affecting the previous installation of MSDE 7.0 ?
>
>.
>sql
that is using MSDE 7.0 which was installed with the
software ?
If you can, what is the best way to do so without it
affecting the previous installation of MSDE 7.0 ?Yes you can. BE aware, though, that MDAC on the machine will be upgraded to 2.6 (if not or higher
already), so make sure you test the app for that MDAC version.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Valencia" <vahorda@.hotmail.com> wrote in message news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
> Can you install SQL2000 on a server with an application
> that is using MSDE 7.0 which was installed with the
> software ?
> If you can, what is the best way to do so without it
> affecting the previous installation of MSDE 7.0 ?
>|||Thank you Tibor. I checked the version of MDAC and it is
2.5.
>--Original Message--
>Yes you can. BE aware, though, that MDAC on the machine
will be upgraded to 2.6 (if not or higher
>already), so make sure you test the app for that MDAC
version.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Valencia" <vahorda@.hotmail.com> wrote in message
news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
>> Can you install SQL2000 on a server with an application
>> that is using MSDE 7.0 which was installed with the
>> software ?
>> If you can, what is the best way to do so without it
>> affecting the previous installation of MSDE 7.0 ?
>
>.
>sql
Wednesday, March 28, 2012
MSDE 2K vs SQL2K
Hello,
For my application I need to know how I can see the difference (by query) between a MSDE and SQL server.
I need to know if the server is MSDE or SQL...
Is there any information in the system tables where I can see it?
Thank a lot for your informationsI believe this will do it
select @.@.version|||This query returns a string wich described the version of the server.
I'm looking after a number version or something else wich does the same thing. I don't know if it exist... Maybe i'm looking for something that doesn't exist?|||select @.@.version on my pc gives this
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Evaluation Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
I believe you can check whether or not your pc is a MSDE or SQL server 200o etc using this.
I just forgot this ... from the Holy Book (SQL server Books Online)
SERVERPROPERTY
Returns property information about the server instance.
Syntax
SERVERPROPERTY ( propertyname )
Arguments
propertyname
Is an expression containing the property information to be returned for the server. propertyname can be one of these values.
Property name Values returned
Collation The name of the default collation for the server.
Returns NULL if invalid input or error.
Base data type: nvarchar
Edition The edition of the Microsoft SQL Server instance installed on the server.
Returns:
'Desktop Engine'
'Developer Edition'
'Enterprise Edition'
'Enterprise Evaluation Edition'
'Personal Edition'
'Standard Edition'
Base data type: nvarchar(128)
Engine Edition The engine edition of the SQL Server instance installed on the server.
1 = Personal or Desktop Engine
2 = Standard
3 = Enterprise (returned for Enterprise, Enterprise Evaluation, and Developer)
Base data type: int
For my application I need to know how I can see the difference (by query) between a MSDE and SQL server.
I need to know if the server is MSDE or SQL...
Is there any information in the system tables where I can see it?
Thank a lot for your informationsI believe this will do it
select @.@.version|||This query returns a string wich described the version of the server.
I'm looking after a number version or something else wich does the same thing. I don't know if it exist... Maybe i'm looking for something that doesn't exist?|||select @.@.version on my pc gives this
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Evaluation Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
I believe you can check whether or not your pc is a MSDE or SQL server 200o etc using this.
I just forgot this ... from the Holy Book (SQL server Books Online)
SERVERPROPERTY
Returns property information about the server instance.
Syntax
SERVERPROPERTY ( propertyname )
Arguments
propertyname
Is an expression containing the property information to be returned for the server. propertyname can be one of these values.
Property name Values returned
Collation The name of the default collation for the server.
Returns NULL if invalid input or error.
Base data type: nvarchar
Edition The edition of the Microsoft SQL Server instance installed on the server.
Returns:
'Desktop Engine'
'Developer Edition'
'Enterprise Edition'
'Enterprise Evaluation Edition'
'Personal Edition'
'Standard Edition'
Base data type: nvarchar(128)
Engine Edition The engine edition of the SQL Server instance installed on the server.
1 = Personal or Desktop Engine
2 = Standard
3 = Enterprise (returned for Enterprise, Enterprise Evaluation, and Developer)
Base data type: int
MSDE 2K Is there a compatibility issue with Backupexe or Sharepoint
We have installed an application that usese MSDE as the database, no error m
essage during install process. When application is opened and attempts to c
onnect with the database we get the following message:
sql code = -1
sql db code = 10004
"SQL Error: unable to connect: SQL server is unavailable or does not
exist. unable to connect: sql server does not exist or network access
denied"
We can get to the database and view contents using ODBC and OSQL. The syste
m is Windows Server 2003 Small Business Server, and we are using MSDE releas
e A. Other software on the system that might create a problem (hints I've s
een on other forums) are Ba
ckupexe and Sharepoint.
We have checked all issues of access rights and security issues we can think
of but apparently have overlooked something. This is a pretty high priorit
y issue for us so if anyone can help we would certainly appreciate it!I know this may not help much, but if you have no problem connecting from
OSQL and other application, you might want to check with teh vendor of the
application and find out how the connection to SQL Server is made from the
application. This might help lead to you why the error is occurring.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql
essage during install process. When application is opened and attempts to c
onnect with the database we get the following message:
sql code = -1
sql db code = 10004
"SQL Error: unable to connect: SQL server is unavailable or does not
exist. unable to connect: sql server does not exist or network access
denied"
We can get to the database and view contents using ODBC and OSQL. The syste
m is Windows Server 2003 Small Business Server, and we are using MSDE releas
e A. Other software on the system that might create a problem (hints I've s
een on other forums) are Ba
ckupexe and Sharepoint.
We have checked all issues of access rights and security issues we can think
of but apparently have overlooked something. This is a pretty high priorit
y issue for us so if anyone can help we would certainly appreciate it!I know this may not help much, but if you have no problem connecting from
OSQL and other application, you might want to check with teh vendor of the
application and find out how the connection to SQL Server is made from the
application. This might help lead to you why the error is occurring.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql
MSDE 2000A Upgrade to SQL Express SP1 with Merge Replication
Hello,
I have the following scenario. An application using SQL Server 2000 SP3 on the server side and clients using MSDE 2000A (SP3a) on the client machine. Since the client is offline quite often merge replication is used to keep the clients in sync.
Now we try to upgrade to SQL Server 2005 SP1. The publisher and distributor upgrade (on the same box) worked fine and all clients could still synchronize. Fine :-)
Now we try to upgrade the clients to SQL Express SP1. Now the problems start :-(
1) After the upgrade the entry within the Synchronization Manager is gone (we can overcome this by using sp_MSregistersubscription or by manually disable and enable Synchronization manager on the subscription properties)
2) Initial Synchronization (takes a long time but) works fine, if I apply changes to the subscriber or force a reinitialize all following synchronization will fail. With the following messages:
Error messages:
The merge process could not clean up the subscription to 'tstvmw23':'TestBase:'TestBase'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
Get help: http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help: http://help/3989
Remark the test system I use is a nearly empty db (only with full schema and a few lookup tables) with 15MB. The same error occures if I create a new database an subscribe to the same publication.
Please help otherwise I'm forced to step back to MSDE.
Thanks in advance,
Thomas Hotz
Hi,just to make sure you do not want SQL Server Express to the a merge replicant...
http://msdn2.microsoft.com/en-us/library/ms165616.aspx
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de|||What this table on the BOL means is that SQL Server Express cannot act as a Distributor/Publisher on a merge replication and the main cause is that it does not have an Agent.
http://technet.microsoft.com/en-us/library/ms143470.aspx
See the topic SQL Server does not include an agent on that reference.
SQL Server Express can act as a subscriber on Merge Replication though. If you have a type of subscription Pull, as the Agent runs on the subscribers you have to use RMO on your code to instantiate an agent or use Windows Synchronization Manager (Start Menu-> Accessories -> Synchronize)
We have SQLE running as subscribers on a pull merge replication topology...sql
MSDE 2000A Upgrade to SQL Express SP1 with Merge Replication
Hello,
I have the following scenario. An application using SQL Server 2000 SP3 on the server side and clients using MSDE 2000A (SP3a) on the client machine. Since the client is offline quite often merge replication is used to keep the clients in sync.
Now we try to upgrade to SQL Server 2005 SP1. The publisher and distributor upgrade (on the same box) worked fine and all clients could still synchronize. Fine :-)
Now we try to upgrade the clients to SQL Express SP1. Now the problems start :-(
1) After the upgrade the entry within the Synchronization Manager is gone (we can overcome this by using sp_MSregistersubscription or by manually disable and enable Synchronization manager on the subscription properties)
2) Initial Synchronization (takes a long time but) works fine, if I apply changes to the subscriber or force a reinitialize all following synchronization will fail. With the following messages:
Error messages:
The merge process could not clean up the subscription to 'tstvmw23':'TestBase:'TestBase'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
Get help: http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help: http://help/3989
Remark the test system I use is a nearly empty db (only with full schema and a few lookup tables) with 15MB. The same error occures if I create a new database an subscribe to the same publication.
Please help otherwise I'm forced to step back to MSDE.
Thanks in advance,
Thomas Hotz
Hi,just to make sure you do not want SQL Server Express to the a merge replicant...
http://msdn2.microsoft.com/en-us/library/ms165616.aspx
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||What this table on the BOL means is that SQL Server Express cannot act as a Distributor/Publisher on a merge replication and the main cause is that it does not have an Agent.
http://technet.microsoft.com/en-us/library/ms143470.aspx
See the topic SQL Server does not include an agent on that reference.
SQL Server Express can act as a subscriber on Merge Replication though. If you have a type of subscription Pull, as the Agent runs on the subscribers you have to use RMO on your code to instantiate an agent or use Windows Synchronization Manager (Start Menu-> Accessories -> Synchronize)
We have SQLE running as subscribers on a pull merge replication topology...
MSDE 2000 which version to use?
Hi,
I'm planning to develop a VB.NET application using MSDE but came across
these sites... so I'm sort of confused which version of MSDE 2000 to use.
http://www.microsoft.com/downloads/d...displaylang=en
http://www.microsoft.com/downloads/d...displaylang=en
After checking the above two sites, please try to answer the following
questions:
1. What's the difference between these two MSDE 2000?
2. Which one to use for development? (VB.NET)
3. Which one to re-distribute with my custom application?
I was thinking that I have to use the 70MB MSDE file. BUT after comparing
the dates, I'm a bit confused. The 70MB file is older.
Thank you for you time.
Sukhdev.
hi Sukhdev,
"Sukhdev" <Sukhdev@.discussions.microsoft.com> ha scritto nel messaggio
news:73B0850D-01E3-41C3-83D5-CF1ED3DAE36B@.microsoft.com
> Hi,
> I'm planning to develop a VB.NET application using MSDE but came
> across these sites... so I'm sort of confused which version of MSDE
> 2000 to use.
>
http://www.microsoft.com/downloads/d...displaylang=en
>
http://www.microsoft.com/downloads/d...displaylang=en
> After checking the above two sites, please try to answer the following
> questions:
> 1. What's the difference between these two MSDE 2000?
the final result, after installation, is actually the same... both install
MSDE at the 3a service pack level..
but there's both a technical and an EULA difference..
MSDE Web Release A can only install fresh instances of MSDE 2000, while the
other package can both install new fresh instances and upgrad existing
instance at the service pack 3a level
as regard the EULA, the second package must be licensed by an appropriate
license of Visual Studio, Fox Pro, MSDN, SQL Server and so on, while MSDE
release A is really free for download, and you only have to register for
redistribution rights if you want to at
http://www.microsoft.com/sql/msde/ho...tregister.asp, but not for
use...
> 2. Which one to use for development? (VB.NET)
I strongly suggest to buy the Developer edition of SQL Server (about $50),
which includes all the server tools like Enterprise Manager, Query Analyzer,
Profiler and all the wizards like Index Tuning to troubleshoot development
issues...
> 3. Which one to re-distribute with my custom application?
chose the one you prefer... redistribution, in this case, is not a
problem...(as long as you are entitled for both)
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
I'm planning to develop a VB.NET application using MSDE but came across
these sites... so I'm sort of confused which version of MSDE 2000 to use.
http://www.microsoft.com/downloads/d...displaylang=en
http://www.microsoft.com/downloads/d...displaylang=en
After checking the above two sites, please try to answer the following
questions:
1. What's the difference between these two MSDE 2000?
2. Which one to use for development? (VB.NET)
3. Which one to re-distribute with my custom application?
I was thinking that I have to use the 70MB MSDE file. BUT after comparing
the dates, I'm a bit confused. The 70MB file is older.
Thank you for you time.
Sukhdev.
hi Sukhdev,
"Sukhdev" <Sukhdev@.discussions.microsoft.com> ha scritto nel messaggio
news:73B0850D-01E3-41C3-83D5-CF1ED3DAE36B@.microsoft.com
> Hi,
> I'm planning to develop a VB.NET application using MSDE but came
> across these sites... so I'm sort of confused which version of MSDE
> 2000 to use.
>
http://www.microsoft.com/downloads/d...displaylang=en
>
http://www.microsoft.com/downloads/d...displaylang=en
> After checking the above two sites, please try to answer the following
> questions:
> 1. What's the difference between these two MSDE 2000?
the final result, after installation, is actually the same... both install
MSDE at the 3a service pack level..
but there's both a technical and an EULA difference..
MSDE Web Release A can only install fresh instances of MSDE 2000, while the
other package can both install new fresh instances and upgrad existing
instance at the service pack 3a level
as regard the EULA, the second package must be licensed by an appropriate
license of Visual Studio, Fox Pro, MSDN, SQL Server and so on, while MSDE
release A is really free for download, and you only have to register for
redistribution rights if you want to at
http://www.microsoft.com/sql/msde/ho...tregister.asp, but not for
use...
> 2. Which one to use for development? (VB.NET)
I strongly suggest to buy the Developer edition of SQL Server (about $50),
which includes all the server tools like Enterprise Manager, Query Analyzer,
Profiler and all the wizards like Index Tuning to troubleshoot development
issues...
> 3. Which one to re-distribute with my custom application?
chose the one you prefer... redistribution, in this case, is not a
problem...(as long as you are entitled for both)
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
MSDE 2000 Vs MS SQL 2000 Server
I am about to setup an application server. This app will generate reports and instead of just having a HTML page up, I am considering running dotnetnuke type portal to offer the userbase a better interface for the reports, info, announcement, etc.
Server isn't too bad (2x1.7Ghz Xeon I think, 2GIG RAM) type of setup (may be little more or less). App doesn't require as much resources, but we are planning for the future )
While I have some resource to play with, I also need to make sure I don't load much that may impact the application performance. In my experience, SQL Server 2000 will take a lot of resources even when not used as much. So I am considering MSDE.
I am curious however, WHAT ARE THE MAIN DIFFERENCES BETWEEN SQL 2000 Server Vs MSDE 2000 ?
Beside no Client tool and mostly command line specific command, what else there to convince that I should go for server vs desktop engine?
Now our company has Enterprise license for SQL, so I am not worried about the cost (well a little maybe), but mostly wondering about performance.
If you think of any reason why I go to SQL Server 2000 over MSDE, please let me. Otherwise, I think MSDE in this case is the appropriate RDBMS to go for.
Regards,
ImpuMicrosoft has a good chart summarizing each of the SQL Server products:SQL Server 2000 Product Overview. You will see that MSDE is the same thing as SQL ServerStandard Edition, with these exceptions:
-- does not include graphical management tools
-- has a workload governor that limits the number of concurrent transactions
-- does not include any analysis capbilities (OLAP, DTS, data mining & warehousing)
-- has different scalability limits
On top of all of that, theEnterprise edition (which you already own), gives you the ability to use failover clustering, log shipping, advanced analysis features, improved scalability, availability, and performance. (SeeFeatures by Edition for more specifics in this area.)
You might find that your database access is your bottleneck, and that you'd want the best performance possible from the database, which would be the Enterprise edition. We inadvertently had moved from the Enterprise Edition to the Standard Edition a while back, and there was a SIGNIFICANT decrease in performance. We had maybe 2 dozen people hitting the database and it was awful. The Standard Edition just would/could not take advantage of the hardware in the server. But looking at the hardware you have on your server (dual processor with 2 gig of RAM, it would seem that the Standard would be able to fully utiltize that)
How many users will be hitting your application at once? MSDE will only handle 25 concurrent processes (note: not USERS), which may or may not be enough for your purposes.
Terri|||Awesome response Terri (Thanks).
since this would be an applicaiton server (reporting software that uses built-in db), we will have very limited use for the MS SQL Server or even MSDE. Mainly I need to install it because I want to install dotnetnuke :) ...
Traffic would be very few to this site as the site will have link to reports that are running off of that other reporting engine. As I said, I could easily get by with a IIS/HTML based website for this purpose.
Having the Enterprise or Standard SQL server will give us a lot of advantages, but you are suggesting I will have performance gain too? Even though MSDE have so little functionality than SQL server (Std or Ent)? Then I oughta go for MS SQL Server then (even though it would be pretty much useless other than housing the dotnetnuke tables.
Regards,
impu|||For others if anyone curious, I found this response from a MSFT guy to another person who asked similar question (Lesson learn, do a little more searching before asking a question :))
*************Start of MSFT engineer's response***********************
SQL Server 2000 Desktop Engine (MSDE 2000) is a version of the
SQL Server data engine designed for redistribution with client-side
applications. Desktop Engine supports most of the functionality of the
other editions of SQL Server 2000, as well as the APIs they support.
Desktop Engine has been optimized for use on smaller computer systems such
as laptops, stand-alone workstations, and servers that support small
workgroups.
Therefore, if there is an instance of SQL server 2000 (Enterprise) on your
computer, it is not necessary to install MSDE 2000 again on the same
machine. In this case, if MSDE 2000 is still installed on your machine, it
will be the named instance. Generally, the application requiring
installation of MSDE will run the .sql files to install the databases on
the SQL Server instance. You can check and see the introductions of your
application if it also does the same. If so, based on my experience, there
is not obvious difference between SQL Server 2000 and MSDE 2000.
Desktop Engine implements all of the basic functionality of SQL Server
2000, as well as most of the additional services. There are, however, a few
differences to keep in mind while planning your installation:
1. The size of Desktop Engine databases cannot exceed 2 gigabytes (GB).
2. Desktop Engine supports symmetric multiprocessing on a maximum of two
processors.
3. Desktop Engine uses the same concurrent workload governor as SQL Server
2000 Personal Edition. When more than five batches are run concurrently,
the workload governor will insert no-ops in direct proportion to the number
of excess batches submitted for processing, thereby reducing system
performance.
4. Desktop Engine participates in replication as:
a. A Subscriber in transactional replication.
b. Both Subscriber and Publisher in snapshot and merge replication.
5. Desktop Engine does not support SQL Mail.
6. Desktop Engine is not supported on Windows? Advanced Server, Limited
Edition.
For more information about the features supported by Desktop Engine, please
refer to the article on SQL Server Books Online.
Topic "Features Supported by the Editions of SQL Server 2000."
817788 Support WebCast: Microsoft SQL Server 2000 Desktop Engine (MSDE)
http://support.microsoft.com/?id=817788
***************end of his response**********************
p.s. Notice #3 (same thing Terri pointed out). May be a decision factor why I should choose SQL Server Ent over MSDE. Didn't think of it from this angle (but then again, would I see more than 4 users? I might. :p
Thanks
Impu|||Take a look at this:http://www.microsoft.com/sql/msde/productinfo/features.asp According to this Microsoft MSDE 2000 Features Article, MSDE does in fact support DTS, it just cannot create them by default because it does not come with the DTS designer (if you have access to SQL Enterprise Manager you should have no problem designing the package).
I will be testing to verify, I will let you know what I find...
Monday, March 26, 2012
MSDE 2000 Release A - Still can be used to distribute commercially?
Can MSDE 2000A still be used to distribute in an application for sale?
Regards,
jz
Yes. You need to have a license though (see
http://www.microsoft.com/sql/msde/ho...msderights.asp) or you can
register:
http://www.microsoft.com/sql/msde/ho...stregister.asp
Jacco Schalkwijk
SQL Server MVP
"Jeff" <joedirt@.datahook.com> wrote in message
news:eU501BVaEHA.1840@.TK2MSFTNGP11.phx.gbl...
> Can MSDE 2000A still be used to distribute in an application for sale?
> Regards,
> jz
>
Regards,
jz
Yes. You need to have a license though (see
http://www.microsoft.com/sql/msde/ho...msderights.asp) or you can
register:
http://www.microsoft.com/sql/msde/ho...stregister.asp
Jacco Schalkwijk
SQL Server MVP
"Jeff" <joedirt@.datahook.com> wrote in message
news:eU501BVaEHA.1840@.TK2MSFTNGP11.phx.gbl...
> Can MSDE 2000A still be used to distribute in an application for sale?
> Regards,
> jz
>
MSDE 2000 named instance with my application
I am writing an application and wish to distribute MSDE with it.
I was considering using a batch file to do the install using the line
setup INSTANCENAME="InstanceName" SAPWD="AStrongSAPwd"
However, the next step would be to call osql to either script the schema or
sp_attach_db the database. Well this raises the issue of once installed
with a named instance how do I do osql -E -S MACHINENAME\InstanceName
without knowing it ahead of time? Is there perhaps 1. an easier way or 2. a
different syntax to achieving it? I am pretty sure I will run into more
grief when attempting to set up the ODBC connections also.
Maybe I'd just be better off rewriting this to use an Access database
instead
hi Bradley,
"Bradley M. Small" <BSmall@.XNOSPAMXmjsi.com> ha scritto nel messaggio
news:ejW7scifEHA.1424@.tk2msftngp13.phx.gbl...
> I am writing an application and wish to distribute MSDE with it.
> I was considering using a batch file to do the install using the line
> setup INSTANCENAME="InstanceName" SAPWD="AStrongSAPwd"
> However, the next step would be to call osql to either script the schema
or
> sp_attach_db the database. Well this raises the issue of once installed
> with a named instance how do I do osql -E -S MACHINENAME\InstanceName
> without knowing it ahead of time? Is there perhaps 1. an easier way or 2.
a
> different syntax to achieving it? I am pretty sure I will run into more
> grief when attempting to set up the ODBC connections also.
> Maybe I'd just be better off rewriting this to use an Access database
> instead
you don't actually need to reference the Machine name... just refer to it as
"(local)" or "."
so, the full instance name will be
(local)\InstanceName
stay this MSDE... you'll love it =;-D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2npor3F3baroU1@.uni-berlin.de...
> hi Bradley,
> "Bradley M. Small" <BSmall@.XNOSPAMXmjsi.com> ha scritto nel messaggio
> news:ejW7scifEHA.1424@.tk2msftngp13.phx.gbl...
> you don't actually need to reference the Machine name... just refer to it
as
> "(local)" or "."
> so, the full instance name will be
> (local)\InstanceName
> stay this MSDE... you'll love it =;-D
> --
Great!!! Seemed like there had to be a better syntax
Now, all I need to figure out is how to add the odbc connection from a batch
file. Is that even possible?
I was considering using a batch file to do the install using the line
setup INSTANCENAME="InstanceName" SAPWD="AStrongSAPwd"
However, the next step would be to call osql to either script the schema or
sp_attach_db the database. Well this raises the issue of once installed
with a named instance how do I do osql -E -S MACHINENAME\InstanceName
without knowing it ahead of time? Is there perhaps 1. an easier way or 2. a
different syntax to achieving it? I am pretty sure I will run into more
grief when attempting to set up the ODBC connections also.
Maybe I'd just be better off rewriting this to use an Access database
instead
hi Bradley,
"Bradley M. Small" <BSmall@.XNOSPAMXmjsi.com> ha scritto nel messaggio
news:ejW7scifEHA.1424@.tk2msftngp13.phx.gbl...
> I am writing an application and wish to distribute MSDE with it.
> I was considering using a batch file to do the install using the line
> setup INSTANCENAME="InstanceName" SAPWD="AStrongSAPwd"
> However, the next step would be to call osql to either script the schema
or
> sp_attach_db the database. Well this raises the issue of once installed
> with a named instance how do I do osql -E -S MACHINENAME\InstanceName
> without knowing it ahead of time? Is there perhaps 1. an easier way or 2.
a
> different syntax to achieving it? I am pretty sure I will run into more
> grief when attempting to set up the ODBC connections also.
> Maybe I'd just be better off rewriting this to use an Access database
> instead
you don't actually need to reference the Machine name... just refer to it as
"(local)" or "."
so, the full instance name will be
(local)\InstanceName
stay this MSDE... you'll love it =;-D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2npor3F3baroU1@.uni-berlin.de...
> hi Bradley,
> "Bradley M. Small" <BSmall@.XNOSPAMXmjsi.com> ha scritto nel messaggio
> news:ejW7scifEHA.1424@.tk2msftngp13.phx.gbl...
> you don't actually need to reference the Machine name... just refer to it
as
> "(local)" or "."
> so, the full instance name will be
> (local)\InstanceName
> stay this MSDE... you'll love it =;-D
> --
Great!!! Seemed like there had to be a better syntax
Now, all I need to figure out is how to add the odbc connection from a batch
file. Is that even possible?
Friday, March 23, 2012
MSDE 2000 Install Problems
I have been developing an application that uses MSDE 2000 as it's database.
In the process of testing/debugging my installation, I have run into an
interesting and very frustrating problem. MSDE now completely refuses to
install anymore! I cannot get the installer to install either as part of my
installer package using the MSDEBootstrap release candidate "or" by running
the MSDE setup from the command line.
I tried attaching the verbose log from my last command-line attempt, but
this newsgroup blocks my message due to size constraints. If anyone can
provide me any insight into how to resolve this, it would be much
appreciated. The error generated by the install is the ambiguous error
1603. The portion of the log which seems to contain the location where
things are goofin up follows:
MSI (s) (2C:08): Doing action:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B
Action start 8:35:54:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B.
MSI (s) (2C:08): Creating MSIHANDLE (49) of type 790542 for thread 3592
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
TempFolder is
C:\DOCUME~1\sbrodie\LOCALS~1\Temp\{689404D2-1C94-44B3-9203-BEC5594FDA7A}\
Loading extended custom action library
C:\DOCUME~1\sbrodie\LOCALS~1\Temp\{689404D2-1C94-44B3-9203-BEC5594FDA7A}\sql
cax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
Starting custom action SetPropSQLMSDEInstalled
FindSet for ProductCode <{689404D2-1C94-44B3-9203-BEC5594FDA7A}> returned 2
Setting SQLMSDEInstalled by MsiSetProperty returned 0
Setting SQLMSDESelected by MsiSetProperty returned 0
End SetPropSQLMSDEInstalled
Action ended 8:35:55:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B. Return value
1.
MSI (s) (2C:08): Doing action:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B
Action start 8:35:55:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B.
MSI (s) (2C:08): Creating MSIHANDLE (59) of type 790542 for thread 3592
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
Entering Function MyMsiEvaluateCondition
MsiEvaluateCondition for SQLMSDEInstalled returned TRUE
End Function MyMsiEvaluateCondition
Error reading setup parameters
Action ended 8:35:55:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. Return value 3.
Action ended 8:35:55: INSTALL. Return value 3.
MSI (s) (2C:08): Note: 1: 2262 2: Control 3: -2147287038
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir = C:\DMSF
Property(S): SqlProgramDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlInstanceName = DMSF
Property(S): SqlSa...
Property(S): VersionNT = 501
Property(S): ALLUSERS = 1
Property(S): ARPNOMODIFY = 1
Property(S): DefaultUIFont = Tahoma8
Property(S): INSTALLLEVEL = 3
Property(S): LIMITUI = 1
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductCode = {689404D2-1C94-44B3-9203-BEC5594FDA7A}
Property(S): ProductLanguage = 1033
Property(S): ProductName = Microsoft SQL Server Desktop Engine
Property(S): ProductVersion = 8.00.761
Property(S): MsiHiddenProperties = SqlSa...
Property(S): ProgramFilesFolder.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B =
C:\Program Files\
Property(S): StartupFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B =
C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): SystemFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B =
C:\WINDOWS\System32\
Property(S): SQLVersion.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 8.00.194
Property(S): SQLMSDEInstalled = 1
Property(S): SQLExitCode.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 1603
Regards
Shane Brodie
"Shane Brodie" <sbrodie@.deorkit.com> wrote in message
news:u5BCBXJIEHA.4052@.TK2MSFTNGP12.phx.gbl...
> I have been developing an application that uses MSDE 2000 as it's
database.
> In the process of testing/debugging my installation, I have run into an
> interesting and very frustrating problem. MSDE now completely refuses to
> install anymore! I cannot get the installer to install either as part of
my
> installer package using the MSDEBootstrap release candidate "or" by
running
> the MSDE setup from the command line.
>
You may want to try a manual removal of the SQL Server 2000 Desktop database
(MSDE), reboot then re-install.
http://www.support.microsoft.com/?id=320873
Steve
|||Thanks Steve:
Been there ... done that ... got the t-shirt. Following is a part of my
daily blog at work:
...
Frustration day. Had a bunch of problems with MSDE and the release candidate
installer used to install the database as part of a VS.Net project. For
whatever reason, the installer is refusing to install MSDE on my machine
even after performing an in-place update of Windows XP, uninstalling and
re-installing SQL Server tools and another instance of MSDE I am running and
performing an exhaustive filesystem and registry "search and destroy
mission" to remove any existing references to my database instance. BTW:
It would be really ... nice ... if Microsoft would post expected release
dates of the final release of "release candidate" software(give or take 6
months ; ) ).
Existing newsgroup postings report similar problems and the log files
generated by the Windows Installer and Event Viewer are somewhat less than
informative ...
In the meantime, I have managed to install an instance of MS SQL Server
using the official SQL Server 2000 Personal Edition CD so that I can
continue development while I fight with this issue. I am following up on the
MS newsgroups and elsewhere to see if there are permanent work-arounds/fixes
for this problem.
...
As well installation fails whether I use the generated installation from my
VS.Net solution or if I perform a command-line install of MSDE2000a.
Sorry about the double post ... Outlook Express complained on the size of
the message plus log (and I assumed that it meant it did not send ...) and
then sent it anyways.
Regards
Shane Brodie
In the process of testing/debugging my installation, I have run into an
interesting and very frustrating problem. MSDE now completely refuses to
install anymore! I cannot get the installer to install either as part of my
installer package using the MSDEBootstrap release candidate "or" by running
the MSDE setup from the command line.
I tried attaching the verbose log from my last command-line attempt, but
this newsgroup blocks my message due to size constraints. If anyone can
provide me any insight into how to resolve this, it would be much
appreciated. The error generated by the install is the ambiguous error
1603. The portion of the log which seems to contain the location where
things are goofin up follows:
MSI (s) (2C:08): Doing action:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B
Action start 8:35:54:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B.
MSI (s) (2C:08): Creating MSIHANDLE (49) of type 790542 for thread 3592
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
TempFolder is
C:\DOCUME~1\sbrodie\LOCALS~1\Temp\{689404D2-1C94-44B3-9203-BEC5594FDA7A}\
Loading extended custom action library
C:\DOCUME~1\sbrodie\LOCALS~1\Temp\{689404D2-1C94-44B3-9203-BEC5594FDA7A}\sql
cax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
Starting custom action SetPropSQLMSDEInstalled
FindSet for ProductCode <{689404D2-1C94-44B3-9203-BEC5594FDA7A}> returned 2
Setting SQLMSDEInstalled by MsiSetProperty returned 0
Setting SQLMSDESelected by MsiSetProperty returned 0
End SetPropSQLMSDEInstalled
Action ended 8:35:55:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B. Return value
1.
MSI (s) (2C:08): Doing action:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B
Action start 8:35:55:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B.
MSI (s) (2C:08): Creating MSIHANDLE (59) of type 790542 for thread 3592
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
Entering Function MyMsiEvaluateCondition
MsiEvaluateCondition for SQLMSDEInstalled returned TRUE
End Function MyMsiEvaluateCondition
Error reading setup parameters
Action ended 8:35:55:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. Return value 3.
Action ended 8:35:55: INSTALL. Return value 3.
MSI (s) (2C:08): Note: 1: 2262 2: Control 3: -2147287038
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir = C:\DMSF
Property(S): SqlProgramDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlInstanceName = DMSF
Property(S): SqlSa...
Property(S): VersionNT = 501
Property(S): ALLUSERS = 1
Property(S): ARPNOMODIFY = 1
Property(S): DefaultUIFont = Tahoma8
Property(S): INSTALLLEVEL = 3
Property(S): LIMITUI = 1
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductCode = {689404D2-1C94-44B3-9203-BEC5594FDA7A}
Property(S): ProductLanguage = 1033
Property(S): ProductName = Microsoft SQL Server Desktop Engine
Property(S): ProductVersion = 8.00.761
Property(S): MsiHiddenProperties = SqlSa...
Property(S): ProgramFilesFolder.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B =
C:\Program Files\
Property(S): StartupFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B =
C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): SystemFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B =
C:\WINDOWS\System32\
Property(S): SQLVersion.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 8.00.194
Property(S): SQLMSDEInstalled = 1
Property(S): SQLExitCode.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 1603
Regards
Shane Brodie
"Shane Brodie" <sbrodie@.deorkit.com> wrote in message
news:u5BCBXJIEHA.4052@.TK2MSFTNGP12.phx.gbl...
> I have been developing an application that uses MSDE 2000 as it's
database.
> In the process of testing/debugging my installation, I have run into an
> interesting and very frustrating problem. MSDE now completely refuses to
> install anymore! I cannot get the installer to install either as part of
my
> installer package using the MSDEBootstrap release candidate "or" by
running
> the MSDE setup from the command line.
>
You may want to try a manual removal of the SQL Server 2000 Desktop database
(MSDE), reboot then re-install.
http://www.support.microsoft.com/?id=320873
Steve
|||Thanks Steve:
Been there ... done that ... got the t-shirt. Following is a part of my
daily blog at work:
...
Frustration day. Had a bunch of problems with MSDE and the release candidate
installer used to install the database as part of a VS.Net project. For
whatever reason, the installer is refusing to install MSDE on my machine
even after performing an in-place update of Windows XP, uninstalling and
re-installing SQL Server tools and another instance of MSDE I am running and
performing an exhaustive filesystem and registry "search and destroy
mission" to remove any existing references to my database instance. BTW:
It would be really ... nice ... if Microsoft would post expected release
dates of the final release of "release candidate" software(give or take 6
months ; ) ).
Existing newsgroup postings report similar problems and the log files
generated by the Windows Installer and Event Viewer are somewhat less than
informative ...
In the meantime, I have managed to install an instance of MS SQL Server
using the official SQL Server 2000 Personal Edition CD so that I can
continue development while I fight with this issue. I am following up on the
MS newsgroups and elsewhere to see if there are permanent work-arounds/fixes
for this problem.
...
As well installation fails whether I use the generated installation from my
VS.Net solution or if I perform a command-line install of MSDE2000a.
Sorry about the double post ... Outlook Express complained on the size of
the message plus log (and I assumed that it meant it did not send ...) and
then sent it anyways.
Regards
Shane Brodie
MSDE 2000 how many users
How many users and transaction can handle MSDE 2000. I have an application w
ith 2 pc and I would like to know if MSDE 2000 would work perfectly on that
environment. I was reading the MSDE documentation and I did not found anythi
ng about it. Any additional information I would appreciate.
Sincerely,
RafaelHi
There is quite alot of information in Books Online which can be downloaded
at
http://www.microsoft.com/downloads/...&displaylang=en
For information on the workload govenor see
http://msdn.microsoft.com/library/d...r />
_0neh.asp
http://msdn.microsoft.com/library/d...r />
_5fs6.asp
For capacity details see
http://msdn.microsoft.com/library/d...br />
8dbn.asp
For features see
http://msdn.microsoft.com/library/d...br />
8dbn.asp
If you have two users each with a single connection, you should be fine. You
throughput may be limited by the specification of the machine that it is
running on.
John
"Rafael Tejera" wrote:
> How many users and transaction can handle MSDE 2000. I have an application with 2
pc and I would like to know if MSDE 2000 would work perfectly on that environment. I
was reading the MSDE documentation and I did not found anything about it. Any addit
ion
al information I would appreciate.
> Sincerely,
>
> Rafael|||Why not use SQL Server 2005 Express Edition?
David
"Rafael Tejera" <rafaeltejera@.hotmail.com> wrote in message news:uDRTNf9iGHA
.836@.TK2MSFTNGP02.phx.gbl...
How many users and transaction can handle MSDE 2000. I have an application w
ith 2 pc and I would like to know if MSDE 2000 would work perfectly on that
environment. I was reading the MSDE documentation and I did not found anythi
ng about it. Any additional information I would appreciate.
Sincerely,
Rafael|||"Rafael Tejera" <rafaeltejera@.hotmail.com> wrote in message
news:uDRTNf9iGHA.836@.TK2MSFTNGP02.phx.gbl...
How many users and transaction can handle MSDE 2000. I have an application
with 2 pc and I would like to know if MSDE 2000 would work perfectly on that
environment. I was reading the MSDE documentation and I did not found
anything about it. Any additional information I would appreciate.
Depends on the PC hosting. Is it at least Win2000 or XP (Pro)?
Then no problem. I have a few clients running a small network all with
MSDE. They have 10 users on their network and only a few are ever in the
app at any time (5) .sql
ith 2 pc and I would like to know if MSDE 2000 would work perfectly on that
environment. I was reading the MSDE documentation and I did not found anythi
ng about it. Any additional information I would appreciate.
Sincerely,
RafaelHi
There is quite alot of information in Books Online which can be downloaded
at
http://www.microsoft.com/downloads/...&displaylang=en
For information on the workload govenor see
http://msdn.microsoft.com/library/d...r />
_0neh.asp
http://msdn.microsoft.com/library/d...r />
_5fs6.asp
For capacity details see
http://msdn.microsoft.com/library/d...br />
8dbn.asp
For features see
http://msdn.microsoft.com/library/d...br />
8dbn.asp
If you have two users each with a single connection, you should be fine. You
throughput may be limited by the specification of the machine that it is
running on.
John
"Rafael Tejera" wrote:
> How many users and transaction can handle MSDE 2000. I have an application with 2
pc and I would like to know if MSDE 2000 would work perfectly on that environment. I
was reading the MSDE documentation and I did not found anything about it. Any addit
ion
al information I would appreciate.
> Sincerely,
>
> Rafael|||Why not use SQL Server 2005 Express Edition?
David
"Rafael Tejera" <rafaeltejera@.hotmail.com> wrote in message news:uDRTNf9iGHA
.836@.TK2MSFTNGP02.phx.gbl...
How many users and transaction can handle MSDE 2000. I have an application w
ith 2 pc and I would like to know if MSDE 2000 would work perfectly on that
environment. I was reading the MSDE documentation and I did not found anythi
ng about it. Any additional information I would appreciate.
Sincerely,
Rafael|||"Rafael Tejera" <rafaeltejera@.hotmail.com> wrote in message
news:uDRTNf9iGHA.836@.TK2MSFTNGP02.phx.gbl...
How many users and transaction can handle MSDE 2000. I have an application
with 2 pc and I would like to know if MSDE 2000 would work perfectly on that
environment. I was reading the MSDE documentation and I did not found
anything about it. Any additional information I would appreciate.
Depends on the PC hosting. Is it at least Win2000 or XP (Pro)?
Then no problem. I have a few clients running a small network all with
MSDE. They have 10 users on their network and only a few are ever in the
app at any time (5) .sql
MSDE 2000 database setup trouble
Hello
I am running a stand-alone test environment for an application in XP Pro
which I can only use MSDE to manage my databases.
I've successfully installed msde and am finally able to connect using 'osql
-Usa -Ppassword -S (local)\testmachine' , because I can get the '1>' command
prompt.
My trouble is when I try to create and/or restore a database for the test
application to use I'm running into trouble. For example enter this :
1> USE master
2> RESTORE DATABASE master FROM DISK='C:\master\master_db2.BAK'
3>GO
and I get an error message telling me that "RESTORE DATABASE must be used in
single user mode when trying to restore the master database" ...... I also
get a similar message when trying to create and restore a database called
'public'.
how do I successfully get into 'single user mode' ?
hi,
APB wrote:
> Hello
> I am running a stand-alone test environment for an application in XP
> Pro which I can only use MSDE to manage my databases.
> I've successfully installed msde and am finally able to connect using
> 'osql -Usa -Ppassword -S (local)\testmachine' , because I can get the
> '1>' command prompt.
> My trouble is when I try to create and/or restore a database for the
> test application to use I'm running into trouble. For example enter
> this :
> 1> USE master
> 2> RESTORE DATABASE master FROM DISK='C:\master\master_db2.BAK'
> 3>GO
> and I get an error message telling me that "RESTORE DATABASE must be
> used in single user mode when trying to restore the master database"
> ...... I also get a similar message when trying to create and
> restore a database called 'public'.
> how do I successfully get into 'single user mode' ?
have a look at http://msdn2.microsoft.com/en-us/library/ms180965.aspx ..
typically you open a command window, navigate to the \Binn folder of the
instance you want to start and execute something like
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\>sqlservr.exe -s
InstanceName -m
this will start the instance in single user modo, so that you'll be able to
restore the master database...
to restore "normal user's" database(s) the single user mode is not required,
but the database(s) to be restored must not be in use... so no active
connections must be running against the database(s) to be restored..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply
I am running a stand-alone test environment for an application in XP Pro
which I can only use MSDE to manage my databases.
I've successfully installed msde and am finally able to connect using 'osql
-Usa -Ppassword -S (local)\testmachine' , because I can get the '1>' command
prompt.
My trouble is when I try to create and/or restore a database for the test
application to use I'm running into trouble. For example enter this :
1> USE master
2> RESTORE DATABASE master FROM DISK='C:\master\master_db2.BAK'
3>GO
and I get an error message telling me that "RESTORE DATABASE must be used in
single user mode when trying to restore the master database" ...... I also
get a similar message when trying to create and restore a database called
'public'.
how do I successfully get into 'single user mode' ?
hi,
APB wrote:
> Hello
> I am running a stand-alone test environment for an application in XP
> Pro which I can only use MSDE to manage my databases.
> I've successfully installed msde and am finally able to connect using
> 'osql -Usa -Ppassword -S (local)\testmachine' , because I can get the
> '1>' command prompt.
> My trouble is when I try to create and/or restore a database for the
> test application to use I'm running into trouble. For example enter
> this :
> 1> USE master
> 2> RESTORE DATABASE master FROM DISK='C:\master\master_db2.BAK'
> 3>GO
> and I get an error message telling me that "RESTORE DATABASE must be
> used in single user mode when trying to restore the master database"
> ...... I also get a similar message when trying to create and
> restore a database called 'public'.
> how do I successfully get into 'single user mode' ?
have a look at http://msdn2.microsoft.com/en-us/library/ms180965.aspx ..
typically you open a command window, navigate to the \Binn folder of the
instance you want to start and execute something like
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\>sqlservr.exe -s
InstanceName -m
this will start the instance in single user modo, so that you'll be able to
restore the master database...
to restore "normal user's" database(s) the single user mode is not required,
but the database(s) to be restored must not be in use... so no active
connections must be running against the database(s) to be restored..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply
MSDE 2000 and SQL2005
I have to install MSDE 2000 with a backup application (CommVault Express
6.1) that does not yet support SQL 2005. I also need to install 2005 for
apps that will utilize this version. Are there any known problems with
running both of these versions of SQL on the same server?
Thanks,
Mark B.I have installed 2000 & 2005 on the same server before and they both work.
The 2000 install is the default instance and the 2005 is the named instance.
The only issue might be whether your server has enough resources to handle
both. Memory in particular. I don't think that both instaces share the same
memory space so you would have to make sure there is enough for both.
"Mark Bohlsen" wrote:
> I have to install MSDE 2000 with a backup application (CommVault Express
> 6.1) that does not yet support SQL 2005. I also need to install 2005 for
> apps that will utilize this version. Are there any known problems with
> running both of these versions of SQL on the same server?
> Thanks,
> Mark B.
>
>|||Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
with SQL Server 2005 instances on the same computer. Considering SQL Server
performance, your computer may need much more memory and disk space for the
coexistance.
Please feel free to let us know if you need further assistance. Have a good
day!
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||What about MSDE 2000 and SQL 2000 on the same server? Almost every website
I
read on this topic says something different.
I have a server that currently runs two named instances of MSDE 2000 SP3a.
I want to install SQL2000 (as the default instance) on the server (the serve
r
is light duty, but has 3GB of RAM). I'd imagine I could upgrade the MSDE
databases to SQL 2000 first, but I rather not since the MSDE instances are
working fine.
- Kevin
"Charles Wang[MSFT]" wrote:
> Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
> with SQL Server 2005 instances on the same computer. Considering SQL Serve
r
> performance, your computer may need much more memory and disk space for th
e
> coexistance.
> Please feel free to let us know if you need further assistance. Have a goo
d
> day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ========================================
=============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>
6.1) that does not yet support SQL 2005. I also need to install 2005 for
apps that will utilize this version. Are there any known problems with
running both of these versions of SQL on the same server?
Thanks,
Mark B.I have installed 2000 & 2005 on the same server before and they both work.
The 2000 install is the default instance and the 2005 is the named instance.
The only issue might be whether your server has enough resources to handle
both. Memory in particular. I don't think that both instaces share the same
memory space so you would have to make sure there is enough for both.
"Mark Bohlsen" wrote:
> I have to install MSDE 2000 with a backup application (CommVault Express
> 6.1) that does not yet support SQL 2005. I also need to install 2005 for
> apps that will utilize this version. Are there any known problems with
> running both of these versions of SQL on the same server?
> Thanks,
> Mark B.
>
>|||Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
with SQL Server 2005 instances on the same computer. Considering SQL Server
performance, your computer may need much more memory and disk space for the
coexistance.
Please feel free to let us know if you need further assistance. Have a good
day!
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||What about MSDE 2000 and SQL 2000 on the same server? Almost every website
I
read on this topic says something different.
I have a server that currently runs two named instances of MSDE 2000 SP3a.
I want to install SQL2000 (as the default instance) on the server (the serve
r
is light duty, but has 3GB of RAM). I'd imagine I could upgrade the MSDE
databases to SQL 2000 first, but I rather not since the MSDE instances are
working fine.
- Kevin
"Charles Wang[MSFT]" wrote:
> Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
> with SQL Server 2005 instances on the same computer. Considering SQL Serve
r
> performance, your computer may need much more memory and disk space for th
e
> coexistance.
> Please feel free to let us know if you need further assistance. Have a goo
d
> day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ========================================
=============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>
MSDE 2000 and SQL2005
I have to install MSDE 2000 with a backup application (CommVault Express
6.1) that does not yet support SQL 2005. I also need to install 2005 for
apps that will utilize this version. Are there any known problems with
running both of these versions of SQL on the same server?
Thanks,
Mark B.
I have installed 2000 & 2005 on the same server before and they both work.
The 2000 install is the default instance and the 2005 is the named instance.
The only issue might be whether your server has enough resources to handle
both. Memory in particular. I don't think that both instaces share the same
memory space so you would have to make sure there is enough for both.
"Mark Bohlsen" wrote:
> I have to install MSDE 2000 with a backup application (CommVault Express
> 6.1) that does not yet support SQL 2005. I also need to install 2005 for
> apps that will utilize this version. Are there any known problems with
> running both of these versions of SQL on the same server?
> Thanks,
> Mark B.
>
>
|||Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
with SQL Server 2005 instances on the same computer. Considering SQL Server
performance, your computer may need much more memory and disk space for the
coexistance.
Please feel free to let us know if you need further assistance. Have a good
day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||What about MSDE 2000 and SQL 2000 on the same server? Almost every website I
read on this topic says something different.
I have a server that currently runs two named instances of MSDE 2000 SP3a.
I want to install SQL2000 (as the default instance) on the server (the server
is light duty, but has 3GB of RAM). I'd imagine I could upgrade the MSDE
databases to SQL 2000 first, but I rather not since the MSDE instances are
working fine.
- Kevin
"Charles Wang[MSFT]" wrote:
> Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
> with SQL Server 2005 instances on the same computer. Considering SQL Server
> performance, your computer may need much more memory and disk space for the
> coexistance.
> Please feel free to let us know if you need further assistance. Have a good
> day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
sql
6.1) that does not yet support SQL 2005. I also need to install 2005 for
apps that will utilize this version. Are there any known problems with
running both of these versions of SQL on the same server?
Thanks,
Mark B.
I have installed 2000 & 2005 on the same server before and they both work.
The 2000 install is the default instance and the 2005 is the named instance.
The only issue might be whether your server has enough resources to handle
both. Memory in particular. I don't think that both instaces share the same
memory space so you would have to make sure there is enough for both.
"Mark Bohlsen" wrote:
> I have to install MSDE 2000 with a backup application (CommVault Express
> 6.1) that does not yet support SQL 2005. I also need to install 2005 for
> apps that will utilize this version. Are there any known problems with
> running both of these versions of SQL on the same server?
> Thanks,
> Mark B.
>
>
|||Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
with SQL Server 2005 instances on the same computer. Considering SQL Server
performance, your computer may need much more memory and disk space for the
coexistance.
Please feel free to let us know if you need further assistance. Have a good
day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||What about MSDE 2000 and SQL 2000 on the same server? Almost every website I
read on this topic says something different.
I have a server that currently runs two named instances of MSDE 2000 SP3a.
I want to install SQL2000 (as the default instance) on the server (the server
is light duty, but has 3GB of RAM). I'd imagine I could upgrade the MSDE
databases to SQL 2000 first, but I rather not since the MSDE instances are
working fine.
- Kevin
"Charles Wang[MSFT]" wrote:
> Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
> with SQL Server 2005 instances on the same computer. Considering SQL Server
> performance, your computer may need much more memory and disk space for the
> coexistance.
> Please feel free to let us know if you need further assistance. Have a good
> day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
sql
MSDE 2000 and SQL2005
I have to install MSDE 2000 with a backup application (CommVault Express
6.1) that does not yet support SQL 2005. I also need to install 2005 for
apps that will utilize this version. Are there any known problems with
running both of these versions of SQL on the same server?
Thanks,
Mark B.I have installed 2000 & 2005 on the same server before and they both work.
The 2000 install is the default instance and the 2005 is the named instance.
The only issue might be whether your server has enough resources to handle
both. Memory in particular. I don't think that both instaces share the same
memory space so you would have to make sure there is enough for both.
"Mark Bohlsen" wrote:
> I have to install MSDE 2000 with a backup application (CommVault Express
> 6.1) that does not yet support SQL 2005. I also need to install 2005 for
> apps that will utilize this version. Are there any known problems with
> running both of these versions of SQL on the same server?
> Thanks,
> Mark B.
>
>|||Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
with SQL Server 2005 instances on the same computer. Considering SQL Server
performance, your computer may need much more memory and disk space for the
coexistance.
Please feel free to let us know if you need further assistance. Have a good
day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||What about MSDE 2000 and SQL 2000 on the same server? Almost every website I
read on this topic says something different.
I have a server that currently runs two named instances of MSDE 2000 SP3a.
I want to install SQL2000 (as the default instance) on the server (the server
is light duty, but has 3GB of RAM). I'd imagine I could upgrade the MSDE
databases to SQL 2000 first, but I rather not since the MSDE instances are
working fine.
- Kevin
"Charles Wang[MSFT]" wrote:
> Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
> with SQL Server 2005 instances on the same computer. Considering SQL Server
> performance, your computer may need much more memory and disk space for the
> coexistance.
> Please feel free to let us know if you need further assistance. Have a good
> day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>
6.1) that does not yet support SQL 2005. I also need to install 2005 for
apps that will utilize this version. Are there any known problems with
running both of these versions of SQL on the same server?
Thanks,
Mark B.I have installed 2000 & 2005 on the same server before and they both work.
The 2000 install is the default instance and the 2005 is the named instance.
The only issue might be whether your server has enough resources to handle
both. Memory in particular. I don't think that both instaces share the same
memory space so you would have to make sure there is enough for both.
"Mark Bohlsen" wrote:
> I have to install MSDE 2000 with a backup application (CommVault Express
> 6.1) that does not yet support SQL 2005. I also need to install 2005 for
> apps that will utilize this version. Are there any known problems with
> running both of these versions of SQL on the same server?
> Thanks,
> Mark B.
>
>|||Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
with SQL Server 2005 instances on the same computer. Considering SQL Server
performance, your computer may need much more memory and disk space for the
coexistance.
Please feel free to let us know if you need further assistance. Have a good
day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||What about MSDE 2000 and SQL 2000 on the same server? Almost every website I
read on this topic says something different.
I have a server that currently runs two named instances of MSDE 2000 SP3a.
I want to install SQL2000 (as the default instance) on the server (the server
is light duty, but has 3GB of RAM). I'd imagine I could upgrade the MSDE
databases to SQL 2000 first, but I rather not since the MSDE instances are
working fine.
- Kevin
"Charles Wang[MSFT]" wrote:
> Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
> with SQL Server 2005 instances on the same computer. Considering SQL Server
> performance, your computer may need much more memory and disk space for the
> coexistance.
> Please feel free to let us know if you need further assistance. Have a good
> day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>
Wednesday, March 21, 2012
msde 2000 and sql server
Hi group!
I am developing an application using MSDE 2000.
I made a Setup.exe by using Installshield tool.
in Installshield I add the msde2000.msm with named
instance. so msde2000 will be installed to the end client
machine.
my question is if the end client machine has SQL server
(for example version 2000, 7.5, 6.0), after my installtion
the sql server in end client machine is still OK?
I found the msde installtion will install dll file to
C:\Program Files\Microsoft SQL Server\80,if end client
machine has SQL server, the msde installtion will rewrite
C:\Program Files\Microsoft SQL Server\80.
thank?
yan
Hi Yan,
I'd strongly suggest you:
1. Modify the setup.ini file to have the settings you want for MSDE and to
install it with an instance name that is unique to you. (That will avoid any
clash with an existing installation)
2. Get the end-customer to run the ms-supplied setup for the MSDE before
installing your app.
Unfortunately, there are just way too many problems with auto-installing it
at present. These will be rectified with SQL Express in the future.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"ycjj" <yan@.mcr-sol.pic.melco.co.jp> wrote in message
news:061a01c49b8f$74866590$a301280a@.phx.gbl...
> Hi group!
> I am developing an application using MSDE 2000.
> I made a Setup.exe by using Installshield tool.
> in Installshield I add the msde2000.msm with named
> instance. so msde2000 will be installed to the end client
> machine.
> my question is if the end client machine has SQL server
> (for example version 2000, 7.5, 6.0), after my installtion
> the sql server in end client machine is still OK?
> I found the msde installtion will install dll file to
> C:\Program Files\Microsoft SQL Server\80,if end client
> machine has SQL server, the msde installtion will rewrite
> C:\Program Files\Microsoft SQL Server\80.
> thank?
> yan
I am developing an application using MSDE 2000.
I made a Setup.exe by using Installshield tool.
in Installshield I add the msde2000.msm with named
instance. so msde2000 will be installed to the end client
machine.
my question is if the end client machine has SQL server
(for example version 2000, 7.5, 6.0), after my installtion
the sql server in end client machine is still OK?
I found the msde installtion will install dll file to
C:\Program Files\Microsoft SQL Server\80,if end client
machine has SQL server, the msde installtion will rewrite
C:\Program Files\Microsoft SQL Server\80.
thank?
yan
Hi Yan,
I'd strongly suggest you:
1. Modify the setup.ini file to have the settings you want for MSDE and to
install it with an instance name that is unique to you. (That will avoid any
clash with an existing installation)
2. Get the end-customer to run the ms-supplied setup for the MSDE before
installing your app.
Unfortunately, there are just way too many problems with auto-installing it
at present. These will be rectified with SQL Express in the future.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"ycjj" <yan@.mcr-sol.pic.melco.co.jp> wrote in message
news:061a01c49b8f$74866590$a301280a@.phx.gbl...
> Hi group!
> I am developing an application using MSDE 2000.
> I made a Setup.exe by using Installshield tool.
> in Installshield I add the msde2000.msm with named
> instance. so msde2000 will be installed to the end client
> machine.
> my question is if the end client machine has SQL server
> (for example version 2000, 7.5, 6.0), after my installtion
> the sql server in end client machine is still OK?
> I found the msde installtion will install dll file to
> C:\Program Files\Microsoft SQL Server\80,if end client
> machine has SQL server, the msde installtion will rewrite
> C:\Program Files\Microsoft SQL Server\80.
> thank?
> yan
MSDE 2000 and merge modules
I have a vb.net desktop application that uses msde 2000 for its databasing. I am trying to create a setup file using the output of my desktop application and the msde 2000 merge modules in order to install my own build plus an instance of msde 2000.
The setup runs properly and then asks me to restart my machine. After the restart, however, there is no such instance running on my machine. I am adding the following internal properties to my msi file using ocra:
SQLMSDESelected 1
SqlInstanceName Midas
SqlSaPwd Password1
SqlSecurityMode SQL
SqlDataDir C:\Program Files\Microsoft SQL Server\MSSQL$Midas\Data
SqlProgramDir C:\Program Files\Microsoft SQL Server
This should create an instance of msde on my machine but when I try to connect using enterprize manager or query analizer (I connect to <<machinename>>\Midas), then I get the standard can not connect error.
I am at my witt's end and would really appreciate any help.
Thanks.
Hi,
maybe you could help me....
I'm trying to create a setup file using the VS2003 "Setup Project" and MSDE2000SP4 Merge Modules (editing properties with ORCA).
But when I run the installation file, it shows the following message:
"The Error Code is 2920".
Do you know how to fix that ?
Thanks,
Jo?o Paulo.
sqlMSDE 2000 and merge modules
I have a vb.net desktop application that uses msde 2000 for its databasing. I am trying to create a setup file using the output of my desktop application and the msde 2000 merge modules in order to install my own build plus an instance of msde 2000.
The setup runs properly and then asks me to restart my machine. After the restart, however, there is no such instance running on my machine. I am adding the following internal properties to my msi file using ocra:
SQLMSDESelected 1
SqlInstanceName Midas
SqlSaPwd Password1
SqlSecurityMode SQL
SqlDataDir C:\Program Files\Microsoft SQL Server\MSSQL$Midas\Data
SqlProgramDir C:\Program Files\Microsoft SQL Server
This should create an instance of msde on my machine but when I try to connect using enterprize manager or query analizer (I connect to <<machinename>>\Midas), then I get the standard can not connect error.
I am at my witt's end and would really appreciate any help.
Thanks.
Hi,
maybe you could help me....
I'm trying to create a setup file using the VS2003 "Setup Project" and MSDE2000SP4 Merge Modules (editing properties with ORCA).
But when I run the installation file, it shows the following message:
"The Error Code is 2920".
Do you know how to fix that ?
Thanks,
Jo?o Paulo.
Subscribe to:
Posts (Atom)