My current website is based on access and running fine but a bit slow, the size of the file have always increase rapidly (i don't know why) and I have to download the mdb file every week, using access to compact it and send it back to the hosting company's server. Therefore I concern to upgrade it to SQL server or MSDE. I never used any of them and I have no idea how they work. Here are a few questions:
1, Should I use SQL server or MSDE? I know the differences among access, SQL server and MSDE, but I am curious why is MSDE free? are there any limitation or anywhere worse then access? (considering access does cost money but less powerful then MSDE)
2, Is there a file size problem like what I got with mdb files? it is very important to me because I have limited space for the hosting company.
3, I downloaded MSDE and installed into my WindowsXP, and what I see is only an icon in the task bar any nothing else. I have no clue how it work at all. What else do I need for the upgrade? What are the steps?
4, It seems SQL server and MSDE are tightly integrated into the system. Can I still have a database file and upload it to the hosting company just simply replace the mdb file? Please if someone could provide any tutorial how to run and manage MSDE.
In the readme of v3.5, it mentions that if I use 3.5 to open a database file created by previous version, the version number will be updated to 3.5, so I opened it in c# and run some select statement, then I run the verify() command and here's what's returned:
it seems the database file did not get updated to v3.5. Unless it's returning original info.
Then, I take this same database file and try to access from another project with v3.5 runtime + Enterprise Library, and it generates this error:
An exception of type 'System.Data.SqlServerCe.SqlCeException' occurred in guardian.exe but was not handled in user code
Additional information: You are trying to access an older version of a SQL Server Compact Edition database. If this is a SQL Server CE 1.0 or 2.0 database, run upgrade.exe. If this is a SQL Server Compact Edition 3.0 or later database, run Compact / Repair. [ Db version = 3505053,Requested version = 3004180,File name = D:Dataceguardian.sdf ]
I am confused. Shouldn't 3.5 opens it up regardless of what version it is?
I just attempted to upgrade to SQL Server Compact Edition (2005? 3.1?). The install appeared to go ok but I have no idea really and judging from the version numbers that appear in the references of my projects, I'd say there could be a problem. First, here is what I installed (and the order I installed it):
1) SQL Server 2005 Compact Edition (SQLServerCE31-EN.msi) 2) SQL Server 2005 Compact Edition Developer SDK (SSCE31SDK-ENU.msi) 3) SQL Server 2005 Compact Edition Tools for Visual Studio 2005 SP1 (SSCE31VSTools-ENU.exe)
The first two installs went normal and said they completed successfully. The VS Tools install was strange... it appeared to install but there was no message saying it was complete or successful. The install dialog just disappeared when it was done.
I had some projects that already had references to SQL Server Mobile 2005, so I loaded up a few of those projects, went to the references and removed the SqlServerCe reference and re-added it. I figured the version number would change but it didn't. The version number in the references dialog is 3.0.3600.0. However, the file that it's pointing to is 3.0.5300.0 (browsed to it in Explorer and looked at the properties). Does anyone know what the real version of SSCE is now?
Also, when I removed the reference to SqlServerCe and added it back, I got an application error in VS2005. This has happened every time with every project I've tried. I have to remove the reference, exit VS, reload VS and add the reference back. Which may all just be a waste of time since it doesn't look like it's doing anything.
One other small thing I noticed in the references is that the path for SqlServerCe has an extra between the "SDK" and "SQL Server" directories:
C:Program FilesMicrosoft Visual Studio 8SmartDevicesSDK\SQL ServerMobilev3.0System.Data.SqlServerCe.dll
I'm very confused at this point and hope someone can clear some of this up for me. Thanks!
I have read a few books on SQL Server and on access. I recently got my 1st programming job (vb.net)
I want to move my database from Access to SQL server. But I would like to Use access as the front end for simple data entry, queries and reports. I dont know how to do this,, (using Access as a front end for SQL Server)
Can anyone recomend topics of interest or a good book?
I have a problem regarding the importing the access database in the SQL server 7.0. We have a matrimonial portal named www.viwahmandap.com which is using an access database.We are using the dsn to access this .mdb file. Now we will be upgrading to SQL 7.0.The server administrator won't do anything like importing the access database .So i will have to download the access database on our domain ,import this access file into an SQL database using the DTS wizard which is available in SQL 7.0(This i can do). This will create the respective .mdf & .ldf files.Now What are the next steps to be followed at my end? What should i ask for from the the server administrator?Are there any changes required in my ASP application.What else should be done?Please help.
I have just tried to upgrade an Access database for the first time. All the tables & data have been moved into SQL Server, but all the Primary Keys & Foreign Keys have disappeared. The Primary Key columns are marked as allowing NULL values in SQL Server, and I can't change them to be NOT NULL.
I used the ACCESS export facility to upgrade the database.
Can anyone help me put the constraints into the SQL Server database???
We are entertaining the idea of moving our data to a cloud and I need to know how to convert my Access backend DB to SQL. which version of SQL will I need to use to do the conversion and will also work in a cloud environment.
Oke here is the problem. I hope sombody can help me with it.
After a lot of discussion, I finaly got the people that control the MS SQL server with my appertment as far to allow me to upgrade my access database to the MS SQL server. After this I've created an access project. Devellopping in access I concluded I made a mistake in the rowsource property of one of the tablefields. The people that control the MS SQL server don'n allow me to make changes to the database structure from within access. So I've to write a SQL statement to change this.
Im consulting a financial company on their Access database. It has a back-end with about 100 tables (some close to 100,00 records) and a front-end with all the Forms, Queries, Modules, and Reports. The last few weeks they have had to compact and repair the front end twice a week where before it was a bi-weekly thing.
Im trying to sell them the service of moving everything I can to SQL Server and link it back to the front-end Access GUI, but Im not sure of everything that goes into this process and how long it will take - of course my client needs the process on paper with an estimate timeline/cost.
My questions are: 1) What does Compact and Repair actually do? 2) Can Access Queries be moved to SQL Server Views and be linked? 3) What can I do about Access Modules and Macros? Can they be moved to SQL Server somehow easily? 4) What other concerns should I have?
Also if any of you fine people have done this sort of thing in the past please share your stories :)
Hi, I am trying to learn more about SQL Server, so I can try to make the transition from Access, as I have read, and heard from many people that SQL server is far superior. I have a few questions that I am unsure of, I have basically no real experience with SQL server. 1) I have been watching the "How Do I" videos, posted on MSDN (which are AWESOME, btw), and for most of their examples, they use the SQL Server 2005 Express which comes with VWD. I do not have any problem running any of the sample applications on my local machine, but what about for when you want to actually create a web app to publish online? From what I have read, most hosts do not give support for the express edition of SQL Server 2005, so how do you go about changing your app? For example, if you wanted to use the Login control, which automatically creates a SQL express database for you, can it be changed to implement regular SQL server 2005, or SQL server 2000? I am just confused as to how to make use of the features available other than on a local machine. 2) Where would be a good place to learn more? Any recommended books? 3) Does anyone know of a good (affordable) host that would offer SQL Server 2005/ASP.NET 2.0 support? Any advice would be greatly appreciated. I know these are probably very basic questions, but I am very new to SQL server. Thanks,
1. Is it legal and OK to use a MSDN SQL copy on a production environment or is it strickly for test environments ??
2. If I own a legal copy of SQL 7 with 5 cals, can I legally use SQL MSDE and have more than 5 people access my SQL server or am I also limited to 5 users as my original ??
We're going to be upgrading our Server from 6.5 to 7.0. In addition we're getting a new SQL Server Box.
Which of the following is better: a) Install SQL 6.5 on the new box, restore the DB from old box to the new box, then install 7.0 on the new box and use the upgrade wizard to upsize the DB. (We'll have room to leave the 6.5 devices on the box after upgrading.) or b) Install SQL 7.0 on the new box and upsize the db across the network (100megabit network cards).
Thanks,
Kevin M. Tupper EZLinks Golf, Inc. http://www.ezlinksgolf.com
I'm following a white paper and have run chkupg65 and am stuck at resolving keyword conflicts. I see many TechNet references about fixing them...but none about how. A little help? Below are the conflicts: Keyword conflicts Column name: SyncModification.ACTION[SQL-92 keyword] Column name: Jobs.EXPIREDATE[SQL-92 keyword] Column name: SqlStoreTable.SIZE[SQL-92 keyword] Column name: JobDetails.TIME[SQL-92 keyword] Column name: SchedulerSafeDelete.TIME[SQL-92 keyword] Column name: SMSEvent.TIME[SQL-92 keyword] Column name: SyncModification.TIME[SQL-92 keyword] Column name: vJobDetails.TIME[SQL-92 keyword] Column name: vSMSEvent.TIME[SQL-92 keyword] Column name: Sites.TIMESTAMP[SQL-92 keyword] Column name: QueryExpressions.VALUE[SQL-92 keyword]
Does anyone know of a good book or resource on what's the best way to upgrade 6.5 to 2k? Or generally how would you do that considering you need to do on more then 50 servers?
So I'm using Visual Studio's one click deployment to install/update software for users. SQL Express 2005 is the default, and I need to get all current and new users to update to SQL Express 2005 SP2. Ontop of that, I need to change the sa password for all current users (I should be able to manually set it for the new guys).
The problem I'm having is that instead of just updating the current SQL Express engine installed, it creates a new instance of the SQL Express engine when installing SQL Express SP2.
Is there anyway to just update SQL Express to SP2? Is there an easy way to change the sa password when doing so?
I have an application which installs MySQL 3.23. It's hard-coded. Irealize there are newer versions, so I am thinking, what's easiest:1) install the application with its default 3.23 and then run a scriptto convert 3.23 to 4.1 or later,or2) modify the application to install a newer version of MySQL from thestart.
I'm in the process of upgrading a gazillion apps from using .MDB files to using SQLCE 3.5. (Or, at least planning the upgrade). Is there an easy way to save existing .MDB files as .SDFs? Also, we have an occasional app that's web based (eg. certification exam, where we have 10 people take it online at the same time, in one day, and the database keeps the score, questions, etc.); is it a good idea to move that kind of app to SQLCE from MDB?
Hey, I have a SQL Server 2005 Express Edition installed, and I want to upgrade to SP2. Is there a way to configure (using the setup ini file maybe?) the installer to install only the SP2?
When I run SP3 & SP4 for SQL Server it runs okay. I get no errors after the installation & both installations call for a reboot which I do with no problems.
But yet when I get back into my machine, go to the Query Analyzer & run "Select @@version" and execute it, it's still showing v8.00.194 (Original release). It should be showing 8.00.2039.
We are upgrading our servers from 6.5 to 7.0 SQL servers. I used the same configurations on both 6.5 server and 7.0 server like ANSI and the others. But SQL7.0 server turns out to have different data on some tables. Here is the example on one table. Why?
WT_PAY_PERIOD_DATE WT_RDC_HOURS WT_RDC_EXPENSE WT_MS_SUB_HOURS WT_MS_APPR_IND WT_NEW_EMPL_FLAG ------------------------------------- -------------------------- --------------------------------- -------------------------------- ----------------------------- -------------------------------- 2002-04-20 00:00:00.000 23.50 135.2050 23.50 Y X
WT_ASSOC_OTH_EXPENSE WT_ASSOC_TOT_EXP WT_MS_TOT_EXP WT_MS_MILE_LIM ------------------------------------------- ----------------------------------- -------------------------- --------------------------- 3.7600 135.2050 135.2050 373 ************************************************** ************************************************** ************************************************** ********************** I have checked the datatypes that are transferred from SQL6.5. They are the same types as SQL6.5. Plus the configurations are the same on both 6.5 and 7.0. The question is that why the values are different? What the way is to fix it?
Well there's always a first for everything!! I have a SQL 7.0 server on sP1 and ran upgrade to sp3 and recieved error 'error in upgrade script' retry or cancel. When I retried the upgrade ended. I tried to run the upgrade again and it tries continue where it ended before, but the upgrade ends unsucessfully. I even tried extracted the sp3 exe to a diffrent folder and ran the sp3 upgrade with same results.
I started the MSSQL service ok but not able to use Query Analyzer, DTS, EM.
Get the following message:ISQL.EXE - Entry Point not found. The procedure entry point?DeleteRow@CDataCTLStorage@@UAEJJPAPAG@Z could not be located in the dynamic link library SQLGUI.dll
I get similar msgs when trying to open DTS, Enterprise manager from the server. The user databases and appear to be ok. I am able to get to Query Analyzer, etc. from my worksation fine.
Has anyone encountered this before? Is there a fix for it or do I need to rebuild the server from SP1 and restore the databases, etc.??
Has anyone attempted an upgrade from sql7 to 2000? is it a difficult process? what happens to the users. Is there a good site i can go to to get this info ?
Does anyone know how to upgrade a sql driver. Or where to get the driver dll from. The client machine is running 3.70.06.23 and needs 3.70.08.20 to connect to the sql server!
One of my students' company is doing an upgrade from SQL 6.5 to SQL 7.0 and everything converts fine except one veiw. Does anyone know what would cause this to happen? If they run the script in SQL 7.0 it works fine. Any thoughts?
CREATE VIEW dbo.vewRptWooActiveList AS SELECT vewRptWooActiveListSub1.wotUserValue1, vewRptWooActiveListSub1.wooNum, vewRptWooActiveListSub1.wooCreatedWhen, vewRptWooActiveListSub1.wooDispatchedWhen, vewRptWooActiveListSub2.MaxOfwslInsertedWhen AS wooLastStatusWhen, vewRptWooActiveListSub1.wosUserValue1, vewRptWooActiveListSub1.sitName, vewRptWooActiveListSub1.empFullName_Cp, vewRptWooActiveListSub1.Company, vewRptWooActiveListSub1.Region, vewRptWooActiveListSub1.ServiceCenter, vewRptWooActiveListSub1.Zone FROM vewRptWooActiveListSub1 INNER JOIN vewRptWooActiveListSub2 ON vewRptWooActiveListSub1.wooID = vewRptWooActiveListSub2.wsl_WooIDFk
I have a couple of 6.5 installations with different codepages/sort orders, when I come to upgrade these databases, is it possible to change the code pages/sort order during the upgrade of my existing databases so that I have the same sort order/codepages across all my sites?
The databases don't actually have any extended characters in.
All the documentation I have read talks about upgrading from SQL Server 6.x. I presume I can use the upgrade wizard to upgrade my 6.0 system directly to 7.0 without having to upgrade to 6.5 first.
Any thoughts, comments or help would be much appreciated.
Does the upgrade wizard in 7.0 help me upgrade ALL the database objects in SQL 6.5 (including stored procedures, triggers) to 7.0? Has anyone encountered any problems?
Have you ever faced a problem like this. I am running MS SQL Server 6.5 on Windows NT 4.0 computer whose name is with dashes (hou-is). Now, I try to update to version 7.0 and it gives me error message: @@nameserver from export 6.5 is not valid. Use sp_addserver and sp_netname. How you can change a sql server name to non-dash name in order to complete the upgrade sql server? I know this is a challenging tech question. I appreciate your tech expertise.
Currently running SQL Server 7, and have databases. I want to upgrade to SQL Server 2000. How can achieve it without delete or losing my databases. This is NOT a production server, BUT I still want to keep my databases. Ideally I would like to uninstall and reinstall so that there are no SQL Server 7 files lying around when I have SQL 2000 running. Thanks.
We are trying to upgrade from SQL Server v7.0 to SQL Server 2000. Here's our set up,
Current Server: Win NT, SQL Server v7.0 New Server : Win 2000, SQL Server 2000 Client (my PC): Win XP, SQL Server 2000
The New Server is designated SQL Server machine -- company-wide. That is, all the apps/projects uses this machine as the SQL Server. It only has one instance of SQL Server running.
Different project are assigned a dedicated 'Drive' (logical only) and allocated certain disk size as the work space. We (my team) will be the new entry for this server.
Q: When doing the Copy Wizard (from my PC) to upgrade/copy the existing v7.0 db (from Current Server) to New SQL Server 2000, do I need to specify the physicall 'Data' folder? Or, can I copy the database to the selected path -- which is my dedicated drive?
