Hi,
I am a VB programmer and we have a VB application that uses Access as its db (~500MB mdb file) using DAO.
We want to upgrade to MSDE/Sql Server because we have clients that will use around 5 connections to the db and others with no more then 20 users.
I was asked to build a simple test program in Vb under MSDE that will
enable us to test few clients working simultaneously (I have few days for that).
There is so much material on MSDE and we just ordered an MSDE Developer
guide book from the Amazon that will arrive in a few days.
The amount of material is confusing like hell and I didn't work with ADO
before, I don't even know if to work with Access 2000 or with a different db, can you advice ?
Do you know of a good sample that show a beginner like me how to access
MSDE from VB using ADO?
If you do please please advice it will ease the pressure and the days are
numbered.
Thanks a lot.
the service is already automatic, but when starting Windows XP MSDE "asks" to be installed correctly, run setup again and as you can imagine i did so. I can't find the answer
Am very new to MS SQL adminstration Can anybody help me out how to work on Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Release A just for the practice.
The activity which am going to workout on MSDE is below.
How to install SQL(on XP) How the layout will be(like if i insall MSDE what are all Application will be and how they depends on each other) How to create/delete tables if so, how can we do it either by GUI or CUI
Will any application developed against SQL Server 2000 Developer Edition work on an identical platform with only MSDE 2000 installed? I understand there's a concurrency limit with MSDE 2000 of around 25 (and there's no GUI) but apart from that, are there any aspects of SQL Server 2000 functionality (from the .NET applicaiton code's point of view) that are "disabled" in MSDE 2000?
I am creating an install program and I'm wondering if there is a difference between SQL Server 2000 and MSDE 2000? Do they have different entries in the Registry?
From the documentation that I've read it seems as if they are one and the same.
However, if someone knows how to differentiate between them in the Registry it would be greatly appreciated.
After installing WebMatrix on my computer, I installed Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) in my computer, but I can't see MSDE on my Start menu. I am really new to this and don't know how to open MSDE, so I could work with it. Nothing displayed after I installed MSDE, such as the typical "Installation is complete."
Sorry for such a silly question, but please help me. How can I open MSDE from the Start menu. I have windows XP Home.
I have spent megabucks buying a book called MSDE Bible and they have started the book by not telling how you create a database (with all the exact steps required so you can actually work with it. I find this highly unprofessional, and wonder if the authors David C Walls and Denise M Gosnell actually know anything about teaching. (One enormally teaches step 1 before step 2 where I come from - obviously not in some places). Anyway, later on in the book there is an example on creating a database.
My problem is that it does not work because I do not understand what is required in terms of security clearance / user names / passwords / user authority. (They also assume you know all about that too).
All I have done is installed MSDE 2000 Rel A and am now trying to use it. The only question I was asked during the install was to define a "Strong Password" and thats all.
I am now attempting to
1) Create a Database 2) Create a table with some fields 3) See if I can access the database
Now is that too much to ask ?
Here is the code that supposedly creates the database:
The problem is in the connect - something to do with security of some sort that is completely overlooked.
dim oMSDEserver dim oDatabase dim oDataFile dim oLogFile
set oMSDEserver = CreateObject("SQLDMO.SQLServer") set oDatabase = CreateObject("SQLDMO.Database") set oDataFile = CreateObject("SQLDMO.DBFile") set oLogFile = CreateObject("SQLDMO.LogFile")
While installing the MSDE I get the folowing error: A storng SA password is required forsecurity reasons. Please use SAPWD switch to supply the same. Refer to readme for more details. Setup will now exit.
Hi, I have installed the MSDE and use mixed mode authenticaton. The SQL Server Agent will not start due to login failures. Normally, I would use the Enterprise Manager Managment wizard to correct the System Account and Connection Credentials.
Can anyone tell me how to achieve this using OSQL?
I never use Microsoft SQL Server .. somebody told me to start with 2000 version .. but I know that there is 2005 I want to know if it is ok to start with 2000 version and at the same time i can follow others who use 2005? Thanks
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.
Hi all,I just got SQL Server 2000, but I already have MSDE installed. Is there anyreason I would want to keep MSDE around on my computer if I install SQLServer 2000? I use MS Visual Studio 2002 on Windows XP SP2, in case itmakes any difference. I intend to deinstall MSDE before installing SQLServer 2000, but I get the impression from a few posts that some people haveboth installed and I'm not sure why that would be done. What functionalityis in MSDE that is not in SQL Server 2000?Thanks for answering.--Diana
how i can do it?Under Xp/2000, i write a application that stop/start this serices, butunder Win98, how i do it?Exists a method via SqlServer or a dos command to stop/start the MSDEprogram?Thanks a lotTomas--Questa è una firma automatica di MesNews.Sito: http://mesnews.no-ip.com
I'm new to sql. Can someone help me to write a script to select overlapping start dates for each client records. For example: Clientid 1 have 3 episode as below(I only want to see the first two records with overlapping start date records)
We have a sql2000 clustered server running on a windows 2003 cluster, today we noticed that the SQL resources where in a Online Pending state and do not came up anymore.
I have searched the net and found some info about the sqlstate = 08001 Native error 11 , witch indicated that the SQL Network name could have been renamed , however this is not the case here , . i also found that there might be Resolve issue but The Cluster Name and the SQL Network name can be resolved by both Cluster nodes ..
does anyone here got experience with this kind of problem ? Pls Help
Here is a part of the cluster.log with the errors :
ERR SQL Server : [sqsrvres] ODBC sqldriverconnect failed ERR SQL Server : [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 11; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. ERR SQL Server : [sqsrvres] ODBC sqldriverconnect failed ERR SQL Server : [sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 2; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). ERR SQL Server : [sqsrvres] ODBC sqldriverconnect failed ERR SQL Server : [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 11; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. ERR SQL Server : [sqsrvres] ODBC sqldriverconnect failed ERR SQL Server : [sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 2; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). INFO [CP] CppRegNotifyThread checkpointing key SOFTWAREMicrosoftMicrosoft SQL ServerDBHSBMSSQLSERVER to id 4 due to timer INFO [Qfs] QfsGetTempFileName C:DOCUME~1SRVCCL~1LOCALS~1Temp, CLS, 13 => C:DOCUME~1SRVCCL~1LOCALS~1TempCLSD.tmp, status 0
According to the SQL server log the server is started and all databases are brought on-line then a stop request from Service Control Manager terminates SQL Server see log below:
2007-11-05 14:04:02.89 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: )
2007-11-05 14:04:02.89 server Copyright (C) 1988-2002 Microsoft Corporation. 2007-11-05 14:04:02.89 server All rights reserved. 2007-11-05 14:04:02.89 server Server Process ID is 3264. 2007-11-05 14:04:02.89 server Logging SQL Server messages in file 'P:mssqlMSSQL$DBHSBlogERRORLOG'. 2007-11-05 14:04:02.89 server SQL Server is starting at priority class 'high'(2 CPUs detected). 2007-11-05 14:04:03.61 server initdata: Warning: Could not set working set size to 823168 KB. 2007-11-05 14:04:03.66 server SQL Server configured for thread mode processing. 2007-11-05 14:04:03.72 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks. 2007-11-05 14:04:03.77 server Attempting to initialize Distributed Transaction Coordinator. 2007-11-05 14:04:06.32 spid2 Starting up database 'master'. 2007-11-05 14:04:06.52 spid2 Server name is 'HSBSQL01DBHSB'. 2007-11-05 14:04:06.52 spid5 Starting up database 'msdb'. 2007-11-05 14:04:06.52 spid6 Starting up database 'model'. 2007-11-05 14:04:06.52 spid8 Starting up database 'dbHSB'. 2007-11-05 14:04:06.52 server Using 'SSNETLIB.DLL' version '8.0.2039'. 2007-11-05 14:04:06.56 server SQL server listening on 10.122.131.103: 1433. 2007-11-05 14:04:06.62 spid8 Analysis of database 'dbHSB' (7) is 100% complete (approximately 0 more seconds) 2007-11-05 14:04:06.63 server SQL server listening on TCP, Shared Memory, Named Pipes. 2007-11-05 14:04:06.63 server SQL Server is ready for client connections 2007-11-05 14:04:06.66 spid6 Clearing tempdb database. 2007-11-05 14:04:07.10 spid6 Starting up database 'tempdb'. 2007-11-05 14:04:07.20 spid2 Recovery complete. 2007-11-05 14:04:07.20 spid2 SQL global counter collection task is created. 2007-11-05 14:04:16.41 spid1 Warning: unable to allocate 'min server memory' of 1658MB. 2007-11-05 14:10:45.18 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.
I have a client that is moving their web ap (which has already been developed) from one host to their own servers. The problem is that they don't have MS SQL Server 2000, but they have MSDE. All the code is already writen to work with SQL SERVER 2000.
I have a couple of questions:
1. Can I safely assume that all this code will work with MSDE and all I have to change is the connection string? For example:
SqlConnection myConn = new SqlConnection(connstring);
In other words, can I still use the SqlClient classes to work with MSDE, or will I have to modify the code?
2. Will it be a problem creating the tables and migrating the data from SQL SERVER to MSDE? Can I use Enterprise Manager to do this?
3. I never had to remotely (or even locally) connect to a MSDE database alone, I always develop with a SQL Server db. Can I use a similar connection string for the MSDE database? Do I have to create a data provider on the local machine? Can you give me an example of a MSDE connection string?
I have MSDE installed on a production machine together with a bunch of ASP.NET applications. I was asked to replace MSDE with SQL Server 2000 and move every application from MSDE to SQL Server 2000 with minimum downtime.
Did any of you go through a similar process?
What is the best way of doing this conversion?
How to move the backups from MSDE to SQL Server?
Is it possible to have MSDE and SQL Server 2000 coexists for a time while moving stuff around and redirecting every connection?
Any hints or suggestions would be greatly appreciated.
Hi, I am developing an web-database application using ASP.net,c# and MSDE. and after the completion of the project i want to deploy the database over the server whichs got sql server professional edition. Are there any changes to be made while deploying it over the server and also will the connection string for MSDE and SQL client the same ? Please do clear me the confusions i have got .. thanks inadvance
I developed an app which stored data in SQL 2005, and encrypted some data using EncryptByPassPhrase( PassPhrase, TheData ), DecryptByPassPhrase( PassPhrase, TheData).
One of the implementations of this will have to store the data in SQL 2000, which doesn't support this functionality. Is there a simple data encryption functionality somewhere that I can implement within a stored proc so I can have my app be independent of the back-end data base server?, i.e. so I can have two different stored procedures depending on the back end db, and not to have the front end handle the encryption?
I have an application that is already installed on a Win2k3 Server using SQL Express 2005. I have another application that wants to use MSDE 2000 (already tried using SQL Express 2005, but it won't install). My question is, can both of these be installed on the same server and running at the same time without any problems? Thanks!
I have just started to create a new web project using the new VS 2005, but just discovered that my ISP has not yet converted to SQL Server 2005 and uses 2000 MSDE.
My first question is, assuming I don't use any new SQL Server 2005 features will there be any problems in using SQL 2000? Can I create/ reports and use the reporting services, or will I have to make 2 versions of my application?
2nd question is: I have to use their database name and userid. To me, this means changing every form that connects to SQL Server from my local information. Is there a way to make this dynamic so that I can change the DB name, userid, pw, etc. without creating 2 or more versions of this Web application?
With SQL 2000 and MSDE 2000, I only had to put a "." for the server name in a connection string. Now with SQL Express 2005 I have to acually reference the server instance name ".SQLEXPRESS".
Why is this?
Also, when running the command line tools for running scripts, I have to include the parameter "-S MACHINESQLEXPRESS" in the command line where as before I never used the -S parameter at all.
Anyone know why? I am curious because it is going to cause an impact on our upgrades for the client.
My only answer to these questions is that there is no SQL Agent running anymore.
Hello everyone,i want to know abt the "Difference between MSDE and SQL Server 2000". For example the features they support, capacity and requirements etc...
Hi I have upgraded my local to sql server 2005, but still need to access the remote instance which is still at version 2008/8.0. Enterprise Manager has been removed (by the SQL server 2005 installation) Does anyone know how I can restart older version of SQL server instance (ie 2000/8.0) using SQL server Management Studio?
I don't have admin access on the server which the sql remote instance is hosted. Can get around it by asking the sys admin guy to do it for now but would prefer to continue to be able to do it myself. SQL Server Configuration Manager can only manage SQL server 2005 versions - a nice little caveat!
Is there a way to stop/start remote services using 'net stop/start'? - without having to write code.... I'll continue to search for a solution, but if someon can point me in the right direction, I'd be most greatful.
Can someone advise me if this is basically SQL server 2000 and will work effectively to simulate sql server on a stand alone development machine ? Is this what its meant for?
I have been using MSDE and I recently got Microsoft SQL ServerTM 2000 Developer Edition as part of my MAPS pack. Can and should I replace MSDE with Microsoft SQL Server 2000 Developer Edition on my development pc? Thanks in advance for any advice on pros and cons or known issues?
Hello gurus:Hopefully someone can shed some light on some questions I have. I amtasked to build an application that will schedule and track tasks. Ifirmly believe in not reinventing the wheel however also feel thatcustomizing is certainly not out of the question.I am looking to build something in ASP (or .NET) that can allow anindividual to work "disconnected" from the network while stillaccessing a database (MSDE?) that will sync with SQL 2000 oncere-connected. I have built multiple db apps that are strictly webbased and consider myself somewhat knowledgeable (read.. dangereous)SQL/ASP dude. I understand that for a stand-alone client app I mayhave to use .NET and load the framewsork on the client in order to runthe dynamic pages for database updates. Here are my questions:1) Is there a way for SQL server to "replicate" its tables into aschema/data recognized by MSDE (i.e. generate the "mother ship" tablesand schema first, then use SQL Server to automatically create (export)the client MSDE tables)2) are there tools to manage MSDE so one can see what the heck is inthere? I understand Enterprise manager will not work in this regard.3) Are there any resources (documents, tutorials etc..) for datareplication (i.e. dbsync from MSDE up to MSSQL and vice-versa)4) Am I wasting my time doing this from scratch because there isalready something out there that does all this that is moderatelypriced and customizable?Thanks for your attention and consideration.Eric B
hi .everyone ! i have ms visual studio 2005 with sql sever 2005 management tools
anyway .. i want to use and install sql server 2000 in this machine .. i tried to install it, but when i tried to connect to the server .. it gives me this error: "you must use sql server 2005 management tools to connect to this server"