I want to view the sample databases within Access 2003. When I try to view them an error message appears saying I need MSDE 2000 but this will not run on Windows Vista which is my operating system. What do I need to view the sample database as well as develop applications within Access using SQL server?
View 1 RepliesI have an application built with Access 2003 (MDB). It is running under Windows XP without any problems. If I run it under Vista, it works technically well but I get the data very slow from the server.
Server:
Windows Server 2003 R2, SP2
SQL Server 2005, version 9.00.3054.00
Firewall: off
Client:
Access 2003, SP3
Connection strings:
ODBC;DRIVER={SQL Native Client};UID=SD_Admin;DATABASE=SDX;SERVER=MARS;PWD=xxx;
or
ODBC;DRIVER={SQL Native Client};DATABASE=SDX;Trusted_Connection=Yes;SERVER=MARS;
Windows Firewall on client: off
Onecare Firewall on client: off
How can i Fix this issue?
Installation of MSDE 2000 fails on 64-bit Windows Vista (Build 5308).
The error message is "Setup failed to configure the server.Please refer the error logs for more information". No error log can be found on the machine at the time of installation. Please let me know if anyone else has encountered this problem?
Is it possible to install MSDE 2000 on 64-bit Windows Vista(Build 5308)?
Thanks in advance.
I€™m having a few issues with a server that keeps grinding to a halt and having frequent system issues requiring a reboor. It is Sql 2000 32 bit enterprise edition running 64 bit 2003 server. Im not sure of the impact of having the AWE switch set for this server because even though it has 8Gb of RAM it is only using 262Mb and is used extensively. It is set to dynamically configure sql server memory with a minuimum memory of 3075 and maximum of 6144
Is it worth me removing the AWE option or are there any more tweaks I can make to make this system run more effectively?
Can SQL 2000 32 bit run on a Windows 2003 64-bit Intel OS installation? What about the SQL 2000 64 bit version? Is the Enterprise Edition required for this?
View 1 Replies View RelatedI have been running Windows 2003 64bit and SQL2000 SP4 for over 2 months with out any issues.
Sadly we had a server crash "NTldr missing or corrupted"
now when the one engineer looked at it he suggested to reload the server with Windows 2003 32 bit version as there were known compatibility problems between 2003 64bit and SQL 2000 32bit but that you can install SQL 2000 32bit onto a Windows 2003 64 bit server.
Now i dont really believe this statement nor can i find any documentation supporting this. I believe this server might have crashed due to a new patch that was released the last 2 or 3 week either on Windows or SQL. Does anyone know where i can verify what patches was released?
Maybe someone else can share their thoughts with me.
I have a large VB 6.0 application running with Jet 4.0 Access DB. I am considering moving the DB to MSDE. For testing, I installed MSDE on another computer in a peer to peer network running XP sp1, loaded up the DB from Access to MSDE2000A -- all without problem. (I should add the obvious fact I am new to using SQL server.)
What I find is that with a relatively small test DB, running just a single instance of the application, query response from MSDE is taking several seconds (4-5 second lag) longer than response from the Access DB, which runs extremely fast. This is with the Access DB installed on the same network drive, running the same application and the same queries syntax -- only changing configuration of connection for each (SQL vs Jet 4).
Any clues as to what may be going on? The lag time is unacceptable. I am using SQL password instead of NT security. It seems the process is perhaps lagging in the process of authorization.
Thanks for any suggestions or ideas on this.
Currently a server running 2003 small business operating system has MSDE 2000 and Microsoft##SSEE.
A memory problem exists with SQL consuming over 50% of RAM. Total RAM is 4GB.
There is a SQL 2000 patch for this type of problem. However, it calls for SQL to be upgraded to SP4.
Problem:
Can this MSDE 2000 be upgraded with SP4 and have memory patch applied with Microsoft##SSEE also on this box?
Please let me know. Thank you.
Hey
Ive read on some pages that it is in fact possible to install and run SQL Server 2000 on Vista. In my university, SQL Server 2000 is still used to teach us about databases and how to administrate them. The computers run Windows 2000 Professional. I need to be able to use 2000 so I can not only have compatibility but also know the steps and all possible conditions and solutions to problems.
Would installing and running SQL Server 2000 on Vista be possible or am I better off using 2005? Is there much difference between these 2 versions?
Will it be possible to do an in-place upgrade from SQL 2000 Server Enterprise SP4 32 bit running on top of 64 bit Windows 2003 Enterprise , clustered, to SQL 2005 Enterprise 64 bit?
The 32 bit SQL 2000 to 64 bit SQL 2005 in place upgrade seems questionable to me...
Anybody tried anything like this?
Parameter
Access 2000/XP
SQL Server 7.0
SQL Server 2000
MSDE 2000
Number of instances per server
n/a
n/a
16
16
Number of databases per instance / server
n/a
32,767
32,767
32,767
Number of objects per database
32,768
2,147,483,647
2,147,483,647
2,147,483,647
Number of users per database
n/a
16,379
16,379
16,379
Number of roles per database
n/a
16,367
16,367
16,367
Overall size of database (excluding logs)
2 GB
1,048,516 TB
1,048,516 TB
2 GB
Number of columns per table
255
1024
1024
1024
Number of rows per table
limited by storage
limited by storage
limited by storage
limited by storage
Number of bytes per row
(Excluding TEXT/MEMO/IMAGE/OLE)
2 KB
8 KB
8 KB
8 KB
Number of columns per query
255
4,096
4,096
4,096
Number of tables per query
32
256
256
256
Size of procedure / query
64 KB
250 MB
250 MB
250 MB
Number of input params per procedure / query
199
1,024
2,100
2,100
Size of SQL statement / batch
64 KB
64 KB
64 KB
64 KB
Depth of subquery nesting
50
32
32
32
Number of indexes per table
32
250 (1 clustered)
250 (1 clustered)
250 (1 clustered)
Number of columns per index
10
16
16
16
Number of characters per object name
64
128
128
128
Number of concurrent user connections
255
32,767
32,767
5
i am trying to exporting sql 2000 to ms access 2003 with relationship also exported to access as well as the data.
help plz
I have used the Access 2003 Upsize Wizard to create SQLServer Tables, all worked fine except I cannot Update the tables from Access.
The idea being to use Access Forms as the front end to an SQLserver back end as the Access database is quite complex and filled with macros and queries, not one of mine.
I can update the table in SQLServer but the connected tables at the Access end are read only. Why?
Kind regards,
Johnv
Hello,
I'm not sure if it's the setup I did wrong, but I can't seem to get my
text datatype in my database to store more than 900 characters.
I'm trying to setup a news database for my website, which will populate
the information into a datagrid. To test, I manually added a news
item in the database through the visual studio 2003 gui. I
immediately noticed a problem as the I was getting an error after a
long news item saying:
"The value you entered is not consistent with the data type or length of the column, or over grid buffer limit."
I couldn't find anthing to set the buffer limit and the datatype is
"text" filled with simple text in the column. As a further test,
I
simply entered 12334567890123... up to 900 characters and still
recevied the error.
I would appreciate someone leading me in the right direction on this one.
Thanks a lot.
Hi,
I have a customer with Office 2000 and uses Access 2000. I normally use SQL/7, but for this job would it be save to use MSDE on the web site so the customer can upload and download the MSDE file for product information? I use SQL/7 for the backend. Please advise.
Duane
Hi everyone,In using the SQL Server Database Wizard in Access 2000 to create a newaccess project, I get two consecutive error messages and then the wizardshuts down. The first, which apprears immediately after starting the wizardis a message box stating something like "the property value is too large".After clicking through and filling out the values in the connection anddatabase dialog, I get a second dialog box with the message "Overflow" andthe wizard terminates.My operating system is Windows 2000 Professional with Access 2000 and MSDE2000.Does anyone have any thoughts about what might be causing these errors?Thanks in advance.
View 3 Replies View Relatedi am working on upgrading the clients and server computers from 2000 MSDE to 2005 SQL Express Adv. Plan to upgrade using the template.ini.
i can find the version of sql server running on th server by @@version but how do i find the version of client connctivity components the computer has installed in order to ugrade?
1. somehow i need to know whether to upgrade a client computer CONNECTIVITY COMPONENTS from 2000 to 2005?
2. is there a way to enable tcp/ip in installation script of SQL Express?
THANKS
Hi,
I have an MS-Access database on a shared drive.The Access database has tables linked to a SQL server database.When I try to query the tables in MS-Access database by accessing the share drive,I get the ODBC--call failed error.So I tried creating an ODBC driver for the SQL Server and when I try to link the tables,no tables are displayed.Can anyone help me out with this problem?
-Ruth
I am using two almost idential laptops, one with XP and one with Vista, the only differences is that the XP laptop has 1G of RAM and running Office XP and the Vista has 2G RAM and is running Office 2007.
I have a MS Access database that has linked tables to a SQL Server 2000 database. The performance of the Access database on Vista is 5-10 times slower on the Vista machine. Just flipping through records or opening forms can take 5 - 15 seconds on the Vista machine while the XP machine takes 1 sec or less.
What gives? I looked at the CPU performance and the network performance while the Access database was busy flipping through records, the network traffic was < 2% and the CPU would spike to 40% on one of the CPUs (dual core) but would remain under 5% most of the time.
I also previously had Office XP installed on the Vista machine and it had the same performance issue so bought and install Office 2007 on the Vista machine and it did not solve the problem.
It seems that Vista is doing something that is slowing down Access with linked tables. Is this a issue between Vista and using an ODBC connection to SQL Server?
Thanks in advance for any help on this
I'm trying to configure SQL server 2000 (standard edition) to send e-mail on a Small Business Server 2003. There's a great article on how to do this on a SBS 2000 server (KB304967), but it does not apply to SBS 2003. Can anyone point me to a article or white paper on how to configure SQL on a SBS 2003 server to send e-mail. Thanks.
David Neahusan
Where can I further educate myself on this subject?
Right off from the start I would assume that installing SQL Server 2000 or 2005 on Windows Server 2003 that is set up as a web server hosting a website would be against "best practices." Is my assumption right?
Common sense tells me to not to host a website on a pc that is also hosting my database.
I am trying to change the computer name of a machine running MSDE but I get an error when SQL Server starts. With regular SQL when I change the name of a computer I re-run setup and setup fixes this problem. MSDE can only be installed from unattended mode so I can’t rerun setup and fix the problem.
My question is "How do I change the name of a computer running MSDE with out reinstalling MSDE"
Hi,
I have come to know that the upcoming OS releases VISTA, and Longhorn are no more going to (Courtesy: Microsoft Directions) support the MSDE version of the SQL. So, all the applications that are to be ported on to VISTA and are dependent on MSDE engine would first have the MSDE content be shifted to other compatible databases such as SQL Express, SQL Server (2k, 2k5).
If this is true, i'm wondering how Microsoft WSS release is going to be positioned from the Vista onwards as the typical install of WSS installs MSDE instance on the machine and add the configuration content on MSDE. That said, do we have to manually move our configuration databases to other compatible ones and let go with the functionality or if Microsoft has any plans of releasing any such tool that does this process automatically.
I appreciate your answers.
Regards,
Sagar
Getting error 1326.
I'm running SQL Express on Server 2003 SP1 (workstation - although, I did dcpromo promote and demote prior to installing SQL Express).
I'm trying to connect from SQL Studio Express on Vista.
TCP and Named Pipes are selected in Surface Area Config; sp_config remote, access..., 1 was run (per KB); ports 1433 & 1434 are open (I think 435 also was opened when I ran the KB instructions); Mixed mode is selected, user is set for SQL Auth, password is correct; all permissions are granted.
I found an article online which stated that mixed versions of MDAC can lead to the problem. The server has 2.82.1830 and the client has 6.0.5600.16834. Could this be the problem? If so, how to solve?
Thanks, John
I am trying to install MSDE according to:
http://www.siue.edu/~dbock/cmis460/msde.htm
But it says I need to go to control panel to install components, but it is not listed on the VS.NET 2003 install.
In VS.NET 2002 it worked fine as per instructions, but now i can't seem to get it to work in VS.nET 2003
Hi,
Got a problem with network access for MSDE on Win2003 SBS. I have tried all the usual stuff (SVRNETCN, firewall check) to get windows to open the port for network access, but I am having no luck.
Thought it maybe something to do with win2003 "increased" security.. so check the IPSec policy but nothing looks like it is assigned, plus I could also be checking the wrong policy.
As you can probably tell I know only little bits about server, policies and everything that goes with it (I normally work with the lovely pre setup database) but guess its time I should learn.
So with my small and probably dangerous knowledge can someone please let me know if I am looking in the right area for allowing port 1433 to open for MSDE? If I am how to I edit the policy to allow something to run accross the network?
Basic Server Stats
O/S: Windows 2003 Small Business Server Standard (all updates +sp)
NIC: One gigabit (know win2003 recommends 2)
Hardware: Hugly over the minimum spec!!
MSDE: 3* instances (2 pre installed - SBSMonitoring, SharePoint and 1 user defined that needs sharing)
Thanks so much for any help, background information on group policies and alike would be nice to know as well, but don't worry too much about that!
I am in the process of preforming backwards compatibility testing inside our software with our sql statements. In the past we have run into problems where we write our SQL code in 2005 and SQL 2k cannot handle that code. (ie: nested sub selects within the select statement) I want to maximize effiency and install MSDE 2k on my Vista test machine but i have heard rumors that this could be potentially bad. Also if anyone has done this can you explain how to set the instance name if you already have sql 2005 installed? I would assume this would be done in the setup.ini in the MSDE folder before launch. If this cannot be done i can certainly put a XP test machine online for me to dial into and install MSDE 2k as well but it would have an existing 2005 session on it and i would need to find out how to name the instance before msde installed.
Thanks in advance
-Loryn
I have an application written in VB6 that creates a ADO connection using the (native SQL2005 clien)t from the client to SQLServer 2005 on Server 2003 configured as a stand alone server. The application works great on XP and has for a number of years.
Now I am attempting to deploy in Vista and using the same code the connection speed CRAWLS. it's in the magnitude of atleast 10 times slower. It eventualy works but the selects and doing a readnext against the resulting record set is at a snails pace.
What am I missing. It's has to be some sort of configuration problem somewhere.
Hi,
I need to import an SQL string from MS Excel 2003 to SQL SERVER 2000.
The string I need to import is composed by 5 different several blocks and looks like:
Code Snippet
CommandLine01 = "USE mydb"
CommandLine02 = "SELECT Block ..."
CommandLine03 = "GO
ALTER TABLE Block...
GO"
CommandLine04 = "UPDATE Block..."
CommandLine05 = "SELECT Block..."
The detail of the SQL string is at:
http://forums.microsoft.com/msdn/showpost.aspx?postid=2093921&siteid=1&sb=0&d=1&at=7&ft=11&tf=0&pageid=1
I am trying to implement OJ's suggestion:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2117223&SiteID=1
to use multi - batch processing to import the string to SQL SERVER, something like:
Code Snippet
Dim SqlCnt, cmd1, cmd2, cmd3
'set the properties and open a connection
cmd1="use my_db"
cmd2="create table mytb"
cmd3="insert into mytb"
SqlCnt.execute cmd1
SqlCnt.Execute cmd2
SqlCnt.Execute cmd3
Below is the code (just partial) I have, and I need help to complete it.
Thanks in advance,
Aldo.
Code Snippet
Function TestConnection()
Dim ConnectionString As New ADODB.Connection
Dim RecordSet As New ADODB.RecordSet
ConnectionString = "Driver={SQL Server};Server=myServer;Database=myDBName;Uid=UserName;Pwd=Password"
ConnectionString.Open
CmdLine01 = " USE " & myDB
CmdLine02 = " SELECT ACCOUNTS.FULLNAME FROM ACCOUNTS" ...
CmdLine03 = "GO
ALTER TABLE Block...
GO"
CmdLine04 = "UPDATE Block..."
CmdLine05 = "SELECT Block..."
RecordSet.Open CmdLine01, ConnectionString
RecordSet.Open CmdLine02, ConnectionString
ConnectionString.Execute CmdLine01
ConnectionString.Execute CmdLine02
'Retrieve Field titles
For ColNr = 1 To RecordSet.Fields.Count
ActiveSheet.Cells(1, ColNr).Value = RecordSet.Fields(ColNr - 1).Name
Next
ActiveSheet.Cells(2, 1).CopyFromRecordset RecordSet
'Close ADO objects
RecordSet.Close
ConnectionString.Close
Set RecordSet = Nothing
Set ConnectionString = Nothing
End Function
I may not be the best forum for this post, however I believe some onecan still help me or direct me somewhere else.I'm finding that win 2003 x64 and SQL 2005 CTP is slower than win 2003and SQL 2000.Machine A: Opteron 2.2 (248) w/ 2 cpus. 8GB memory. SCSI disk array.Windows Enterprise 2003 x64 final release. SQL Server 2005 enterpriseCTP.Machine B: Opeteron 2.2 (248) w/ 2 CPUs. 4GB Memory. IDE Drives.Windows Server 2003 (32bit) and SQL Server 2005 (standard).I'm using Cognos' DecisionStream as the ETL tool (32bit). I have theidentical job on both machines. Machine A is slower to do my nightlybuild (1h 20m) vs. Machine B (50m).I've done no tweaking of the databases. I Used SQL 2005's studio tocopy the database from Machine B to Machine A.The only major difference is the O/S and SQL, the machines are samespeed, however Machine A has twice the memory and faster disk; so Iwould expect it to be faster.Can anyone think of smoking guns I might be missing?TIA
View 2 Replies View RelatedI am trying to install MSDE 2.8 on this OS. When I try to install, I receive the following error: Fatal error setup This setup does not support installing on this operating system
Any ideas?
We migrated a MS Access 2003 mdb into MS Access 2007. The mdb has linked tables to SQL Server via a DSN and utilizes a mdw file. In 2003, the username/password is "passed" to SQL Server, so the UID/PWD that is used for opening the mdb, is used in SQL Server.
Opening the same file in 2007 using the same mdw, gives a secondary login on SQL Server.
Is there a way to have MS Access 2007 pass the UID/PWD to SQL Server on linked tables, the same way that 2003 does?
Thanks!
Hi,
Does anyone know if you can run MSSoap on a Windows Vista OS? reason being I have upgraded my laptop from Windows XP to Vista and now I cant get SOAP to work atall, where as on Windows XP I could.
Basically this is my typical install
Install SOAP Toolkit 3.0
Instal MSXML 4.0
Install RegLogEventDLLs
Register following DLLs:
C:Program FilesCommon FilesMSSoapBinariesMSSOAP30.dll
C:Program FilesCommon FilesMSSoapBinariesSOAPIS30.dll
C:Program FilesCommon FilesMSSoapBinariesWHSC30.dll
C:Program FilesCommon FilesMSSoapBinariesWISC30.dll
Register my SOAP Object DLLs
Configure IIS as follows:
Add ISAPI Extension .WSDL to use "C:Progra~1Common~1MSSoapBinariesSOAPIS30.dll"
if its a Windows 2003 server then I allow unknown ISAPI Extensions
Configure user credentials to run the SOAP Objects under Directory SecurityAuthentication
Setup Virtual Direcorys for each of my SOAP Objects
Restart IISThen with a bit of luck it all kinda works however under Windows Vista things are slightly different in that I cant find where to add the ISAPI Extension for the .WSDL or where to set user credentials to run my SOAP Objects.
When i use my test application to call one of my SOAP Objects I get a 5415 Timeout.
Has anyone got any ideas what i'm doing wrong or if i need to configure anything differently or install a newer version of the SOAPToolkit or anything?
Cheers
Steve
C:Program FilesCommon FilesMSSoapBinariesSOAPIS30.dll