I am in the process of migrating 40 access databases to SQL Server. I am migrating the tables to the backend. All of these databases are Identical in structure and purpose. The goal is to centralize all of the databases backends into one Sql server database, but the data needs to stay seperated by each location. So I added a location field to each table in the database; so that each locations data will be seperated by location. How do I go about filtering out the the data so that each location can only update, delete, an view their own data? (I dont mind a long answer.)
I would like to migrate an access data to SQL Server. However, the Access database has an OLE data type field that stores word documents. Is there a way to handle this in SQL Server?
Hello,We maintain a VB6 front-end application using an Access 2000 database. Allcode and forms are in VB6. The program also uses several queries/reportsdefined in Access. For corporate reasons we must move to SQL Server rightaway. Based on our configuration, we're hoping someone can give us a feelfor what's involved here. Since we're only using Access for the data we'renot sure what an "upsizing" would entail. Can someone point us in the rightdirection, tell us the main gotchas, etc. Thanks a lot.Teri Welch
got some MS Access SQL Code that needs converting into TSQL:
SELECT dbo_qryMyServices.FormsServiceID, dbo_qryMyServices.ServiceName, Sum(IIf(IsNull([CompletionDate]),0,1)) AS Completed, Count([pkServiceID])-Sum(IIf(IsNull([CompletionDate]),0,1)) AS Uncompleted, Count(dbo_MyServiceRequests.pkServiceID) AS TotalCount FROM dbo_qryMyServices LEFT JOIN dbo_MyServiceRequests ON dbo_qryMyServices.FormsServiceID = dbo_MyServiceRequests.PostType GROUP BY dbo_qryMyServices.FormsServiceID, dbo_qryMyServices.ServiceName ORDER BY dbo_qryMyServices.ServiceName;
because it's Access and got VBA stuff in it - IIF and ISNULL, I can't figure out how to make it work in proper SQL.
I was really happy to see the Migration Assitant for transferring the Access2000 data to SQL 2005. Unfortunately, during the migration wizard, when it comes to the window of "connect to SQL Server 2005" it gives an error. It says "Connection to SQL Server Failed. An error has occured while establishing connection to the server... also point out it could be SQL server not allowing remote connections (I checked), and something that says: provider: named pipes provider , error 40" ... I'm stuck at this window. Please please help? you can email me directly if you wish to fh.erdogan(at)gmail.com Thanks. p.s. I have a fresh install of SQL Server 2005. All on the same machine.
Venkatesh writes "In MS-Access table a coulmn is specified as Auto number property. I want to migrate this table into SQL Server.
We can create a new column that has identity property in SQL Server 2000, which simulate autonumber property of MS-Access.
My access table contains 700 records and I need to set the column (ListID) as Auto number. i.e., I m going to modify this coulmn with identity property.
But I cant set the identity property for the existing column.
Can u pls send me the sql query that modify the existing column(ListId) with Identity property.
I migrated the Northwind database using SQL Migration Assistant for Access. it worked fine and I was able to link the access forms to Local machine SQL Server 2005 and it worked fine.
Now i want to link the same Northwind access database to Another Server on the network.
When i try to run the wizard again, it won't migrate the user objects like tables to server, it will just create a database and that is it. it will give me this error too.
I attempted to use SSMA to migrate a 2000 file format .mdb into SQL Server Express (and, as I've just purchased VS2005 Pro, into SQL Server Developer Edition).
The file is actually a backend, so nothing to migrate other than tables.
After several runs during which I received (and fixed up) some errors, the process runs smoothly with no errors or warnings, until it comes to the last step; migrating the data itself.
Data migration into 'parent' tables works fine. However, wherever I have data in a table with a foreign key relationship to any of the aforementioned 'parent' tables, it refuses to migrate it. The text of the error message will be very smiliar to the following (from the log):
[Datamigrator: Error] [464/7] [2007-09-23 14:18:54]: Exception: The INSERT statement conflicted with the FOREIGN KEY constraint "Branch$CompanyBranch". The conflict occurred in database "DPMTest", table "dbo.Company", column 'CompanyID'.
There is nothing wrong, so far as I can determine, with the relationships involved.
I can insert data into the tables using any of the following methods: 1. Directly in Access, in the source backend. 2. Using the original Access frontend application, attached to the source backend. 3. Using VB.Net forms I am developing, in the 'upsized' database. 4. Directly in the Management Studio, in the 'upsized' database.
None of these four methods complains in the least about the relationships which SSMA balks at.
I downloaded the Microsoft SQL Server Migration Assistant for Access 4 weeks ago. Today, I tried this program for the first time. I added one Database with 3 Access 2003 Tables to the Access Metadata Explorer. I right clicked Databaes on the Access Metadata pane and did not see the "Convert Schema" highlighted!!!??? What is wrong with the program? How can I make it highlighted? Please help and advise.
At work we are migrating several Access databases to SQL Server 2005 standard edition. These Access databases have no user interface forms. They do however have a series of macros that execute make table queries.
I'm trying to determine what are options are for replacing the make table queries in the macros. My first thought was to do the work in a SQL Server stored prodecure. I am asking for advice on what our options are. Is a stored procedure the way to go? Any suggestions on how to do it?
Hello all, Does anyone know of a utility to migrate Access 97 Queries to SQL Server 7? I've over 400 of them and I am trying not to have to do them by hand.
Also I tried to use to migration wizard from MS instead of the DTS and all I got was Error after error. 'Invalid Date/Time', 'Error with YES/NO field' and 'Timed out' were the most common. In the end only 4 tables out of 89 were migrated.
Hi- Can you give me any help/assistance on the development process involved with migration from MS Access to SQL Server 7. Specifically, I need my current MS Access data migrated to SQL, and then I need two (2) fairly simple forms developed for data input and searching on the web. The developers I have been speaking too seem to want to buy their Hawaiian condo from this one project...which seems like A LOT OF $$ for the development of an off-the-shelf product that costs $15,000. Any leads and/or thoughts would be GREATLY APPRECIATED. THANKS.
I'm very new to MS SQL Server; I just downloaded Express 2005 yesterday. I have it up and running; it seems to be working fine.
Now onto business - I need to migrate data from existing MS Access 2003. How, exactly, do I do this? I've tried searching MSDN, TechNet, and here, and while I get results that seem to tell part of the story, I don't seem to get a true "How to" for this task.
I'm using the SSMA to migrate Access databases into SQL Sever. It's a pretty nifty tool, however, I am having some trouble fully migrating the data over.
When I select 'Convert Schema' the schemas for all the tables are created on the server and *all* the table names appear in the Server Metadata Explorer. There are the usual warnings about name changes and primary key additions and the like but importantly, the output window says that there were no errors. Scrolling through all the tables on the server explorer with the 'Table' tab selected confirms that the schemas for all the tables have been migrated, but for one or two of the newly created tables, the 'Data' tab shows the error message "Failed to retrieve data: Invalid object name 'NewDB.dbo.Pref'" for example. Consequently, when I move on to migrating the data, the operation fails for the tables showing these errors and the error message 'The table 'NewDB.dbo.[Pref]' does not exist in SQL Server' is shown when it is displaying in the Metadata Explorer. When I view the server schema in Management Studio Express, it confirms that they have not been migrated. I have tried to look at the failing tables' schemas and identify any similarities which might be causing them to fail migration but they are all very different so I don't think it's a schema issue.
I've downloaded the migration tool to convert an Access 2000 DB to a SQL DB. The VB code utilizes DAO (3.6) for hourly automatic compaction and the creation of an encrypted security database. ADO is used for the data maintenance functions. I expect the current connection methodology of ODBC using Jet 4.0 will need to be modified (many articles here address this). All the SQL code is inline and also must be modified. The Coldfusion code utilizes Micrsoft Access with Unicode via an ODBC connection with only SQL Select statements. At another job, I migrated an Informix 7 database to MS SQL 7 and for the most part the SQL code remained the same except for the wildcard spec from * to %.
I'm looking for insights and/or shortcuts on this effort, primarily in the SQL command mods area. I'm perusing the threads here as we speak, but hoped someone knew of a specific thread I could go to....laziness is alive and well for us chronologically gifted people, i.e. over 55.
I've installed SQL 2005 Express Addition which created a default database using Windows Authentication -- MachineName/SQLEXPRES. I want to convert some access databases to sql server in the migration assistant, however, when I try to connect the migration assistant to the default database I can't find the database in the drop down box wizard? I'm perplexed? Please shed some light or point me to some articles that will help. Thanks.
we want to completely do away with access, on my report tool,which is crystal report, we want query to be our data source so , we do not want to use ssis packageor import from access to sql, how can l handle bringing all table and the query from Access together.
we recently migrated from our in-house domain to the Enterprise domain. Everything went smooth except for the fact that I can no longer accept my dBs using my SA or my domain admin account. There is only 1 account I can get into the management studio with but it has no admin privileges, so I can't make any  password changes or add accounts. I don't have a test environment so kind of hesitant to experiment with our production system.
hi, We have machine where SQL 2005 server is installed.Atleast 3 web applications are running on it with data size 22GB in all. We need to migrate all data/tables/groups/users from this server to another server.On target server, SQL server 2005 will be installed.After that this migration activity needs to be carried out.what are options available to migrate to target server? Microsoft migration tool? Any already existing stored procedure etc?which is preferred solution in such case?
We have sql server 7 Sqlserver ServicePack SP3 Sort Order = 32 BuildNumber 7.00.961
on Windows NT,Now we are planning to upgrade operating system from win NT machine to windows 2000. Please let me know what and all precausion do i need to take what and what all backup should be done apart from user database. How do i take care of the users,logins,roles, DTS Job and Replication.
Please help me in this and also any links if u have on this topic
Soon I shall have to migrate 2 medium sized databases from SQL server 7 to 2005. Any words of wisdom, “how to�, “do and don’t� would be greatly appreciated.
Here are the details: SQL 7.0 SP4, on Win2000 SQL 2005SP1,on Win2003
Sql 2005 needs to be installed on a new server (Win 2003), which will also be used as a web server (IIS6). I was thinking to go with a clean install for sql 2005 first, and after that to migrate the databases.
When i tried to migrate to SQL Server 2005, it is working fine in the SQL Server 2005 installed in Windows 2003 Server. System tables(syscolumns, sysobjects etc)are created in "Database->Tables->SystemTable".
But when i tried to run in SQL Server 2005 installed in Windows XP, I'm facing the following problems.
1."The object 'CK_SavedSear_LastL_4B422AD5' is dependent on column'LastLoadedTime'
"ALTER TABLE DROP COLUMN LastLoadedTime failed because one or more objects access this column"
2.Moreover none of the tables had been created in "Database->Tables->SystemTable".
In both XP and 2003 Server, While installing, i have choosen same options.
Please anybody could help me to resolve this issue.
I'm migrating 15 user databases from one server to another. The current production server is Windows 2000 Server SP4 and SQL Server 2000 Standard Edition SP4. The new production server is Windows 2003 Server and SQL Server 2000 Enterprise Edition SP4. The new server does not have the same directory structure as the current server.
I plan to detach the database, move the .mdb and .ldb files to the new server and then attach the database again. I'm not sure what to do with the master and msdb databases. Do I need to bring over the master? I know I need the msdb for all the job information. Since these are system databases, do I need to follow a different process? I want to get all these databases over to the new server so I can begin some parallel testing prior to the final cutover.
For anyone that has gone through this process, is there anything that I need to pay special attention to? Any issues moving from Windows 2000 to Windows 2003 or SQL Server 2000 Standard to SQL Server Enterprise Edition?
When i tried to migrate to SQL Server 2005, it is working fine in the SQL Server 2005 installed in Windows 2003 Server. System tables(syscolumns, sysobjects etc)are created in "Database->Tables->SystemTable".
But when i tried to run in SQL Server 2005 installed in Windows XP, I'm facing the following problems.
1."The object 'CK_SavedSear_LastL_4B422AD5' is dependent on column'LastLoadedTime'
"ALTER TABLE DROP COLUMN LastLoadedTime failed because one or more objects access this column"
2.Moreover none of the tables had been created in "Database->Tables->SystemTable".
In both XP and 2003 Server, While installing, i have choosen same options.
Please anybody could help me to resolve this issue.
Scenario Recently moved a SQL2000 database to SQL2005. Collation on SQL 2000 database server was SQL_Latin1_General_CP1_CI_AS Colaltion on SQL 2005 database server is Latin1_General_CI_AS
After restoring the SQL 2000 database on SQL 2005 we observed that the database collation was SQL_Latin1_General_CP1_CI_AS. We have altered the database collation to Latin1_General_CI_AS. We understand this will work for all new objects created on the database but existing objects (prior to the collation change) will continue to have the 'SQL_Latin1_General_CP1_CI_AS' collation.
What is the best method to change the collation of the older columns to 'Latin1_General_CI_AS' - 1) Run ALTER TABLE ALTER COLUMN <colname> <datatype> COLLATE Latin1_General_CI_AS <nullability> on each varchar/char column
or
2) For each table BCP out data DROP TABLE RECREATE TABLE (taking the new collation Latin1_General_CI_AS) BCP in data
hi, i need some help here,i made a simple data driven website in my development PC, at first, i used MS Access for my data base then i migrate it to sql server express 2005, and it works fine when i try to run it in my development PC with my IIS. but of course i will be deploying it to a real server, in our office were i will deploy my data driven site, we have a PC server Win Server 2003 with SQL Server 2000 Enterprise (im not pretty sure by the name but i know its not a free version, its something like a 2000 sql version with a word enterprise at the end).so my question is, i am developing an ASPdotNET site originally used SQL server 2005 express,how can i migrate my site to the Win Server 2003 and my database from SQL Server 2005 express to SQL server 2000 enterprisewill it work?? if not, what are the possible solution that i can do in cases like mine?i used Visual Web Developer 2008 Express Ed. in making my sites, and its DOES NOT allow databases in SQL Server 2000!!!!!it says "can't recognize the database"i hope you can help me with this.Thanks-SALAMAT PO....=)
We are in the process of Migrating our SQL Server 7.0 databases to SQL Server 2000. We have purchased two new servers for this process. What is the best method for the Database Migration ? - Copy Database Wizard ? - DTS ?
Hi! I have an SQL server installation with a 6.5GB database online at a particular location. I need to move the Database to another location which is a 1000 Miles away.
I have an additional physical Server at the other location which I can use to Sync the database from the original location. Can anyone please guide me to the best strategy to sync the database from the original location to the new location with minimum downtime??
Hi All, We are planning to move from sql server 2000 and sql server 2005. Just want to know how well is the backward compatibility and things that we should take care of before migration.
