Move SQL Server database for App Controller

I need to migrate our App Controller server to another SQL Server.
I have copied the relevant SQL Server database. How can I reconfigure App Controller to use this new database?

Hi evilclive1,
To minimize the risk of data loss, I recommend the following steps:
Export the AES encryption key
from your existing App Controller installation
Make sure you have a backup of the App Controller database
On a spare VM, install a new instance of App Controller and connect to the new SQL server (you'll need the AES key from step 1).
Verify that the new instance of App Controller works correctly with the new SQL server (this will verify that you have a good copy of the App Controller database on the new SQL server)
Uninstall the original App Controller
On the original App Controller server, reinstall and point to the new database (you'll need the AES key from step 1)
Verify that this instance of App Controller works correctly with the new SQL server
There isn't a supported way to just change the database used by an existing install.
Kind Regards,
Richard
This posting is provided "AS IS" with no warranties, and confers no rights.

Similar Messages

SQL server preparation for APP-V

Hello,
after 2 years of not touching APP-V I am back. I had a successful experience that allowed me to deploy some virtual apps for a small group of production pc. Than the project was terminated.
So I am back to the "ocean" of info. Sure, that my previous experience helps me to quickly understand and I am confident that it will go well with reading and trying.
I am starting with deployment of a new APP-V infrastructure for a large environment (no time pressure)
At first stage I have to deliver same apps that I sequenced 2 years ago with 4.6. Sure I will resequence everything.
At least I know it worked from APP-V server and RDS.
I have time and powerfull HP G7 server for start. I will use Hyper-V platform. Hardware resources are not the issue.
I want to start with Management server and have a question about SQL server that will be dedicated for APP-V and serve for a long term.
Didn't read best deployment practices yet.
I believe that from general description above a dedicated SQL server (on server 2012 R2 VM) will be better idea than installing SQL on the APP-V Management server VM.
Any link for a good deployment blog, best practices
Sure, I am digging in on MS site and saw very nice topics. Just cannot digest all quickly that is why asking for some quick answers, just to move forward faster.
Thanks for understanding :)
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

Hi,
it has always been a good advice to separate services (IIS / Exchange / SQL / File..) ti different machines, as you then can scale them more easily. However, just for playing around (or: for a test and evaluation environment, as you may call it when justifying
to your managers), having SQL on the same box as the native App-V components is fine.
Some of us actually have a book's chapter made avaulable that covers 'everything' about the native infrastructure. Check the 'fireside' link in my signature below.
Falko
Twitter
@kirk_tn   |   Blog
kirxblog   |   Web
kirx.org   |   Fireside
appvbook.com

Compare methods in C # to connect to SQL Server database in terms of speed,quality and functionality.

Please compare
methods in C # to connect to SQL Server
database (for example,
3-tier architecture of traditional and
entity Framework(linq to entity or linq to sql object model)
and Linq to SQL) in terms of speed, quality and functionality
to give me tips.
Thank you.
Mojtaba Malakouti.

That means we need to compare and post the results here?
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Best practise for creating an application that connects to a SQL Server database

I have created an application that connects to a SQL Server database and views information using a datagrid and performs several updates when a button
is selected.
I have created a SQLcontrol.vb using the following code:
Imports System.Data.Sql
Imports System.Data.SqlClient
Public Class SQlControl
'connection 1
    Public SQLCon As New SqlConnection With {.ConnectionString
= "Data Source=;Initial Catalog=;Integrated Security=True"}
'connection 2
    Public SQLCon1 As New SqlConnection With {.ConnectionString
= "Data Source;Initial Catalog=;Integrated Security=True"}
    Public sqlcmd As SqlCommand
    Public sqlda As SqlDataAdapter
    Public sqldataset As DataSet
    Public Function hasconnection() As Boolean
        Try
            SQLCon.open()
            SQLCon.close()
            Return True
        Catch ex As Exception
            MsgBox(ex.Message)
            Return False
        End Try
    End Function
    Public Sub runquery(query As String)
        Try
            SQLCon.Open()
            sqlcmd = New SqlCommand(query,
SQLCon)
            'LOAD
SQL RECORDS FOR DATAGROD
            sqlda = New SqlDataAdapter(sqlcmd)
            sqldataset = New DataSet
            sqlda.Fill(sqldataset)
BH READ DIRECTLY FROM THE DATABASE
            'Dim
R As SqlDataReader = sqlcmd.ExecuteReader
            'While
R.Read
            'MsgBox(R.GetName(0)
& ": " & R(0))
            'End
While
            SQLCon.Close()
        Catch ex As Exception
            MsgBox(ex.Message)
            'will
close connection if still open
            If SQLCon.State
= ConnectionState.Open Then
                SQLCon.Close()
            End If
        End Try
    End Sub
    Public Sub runquery1(query As String)
        Try
            SQLCon1.Open()
            sqlcmd = New SqlCommand(query,
SQLCon1)
            'LOAD
SQL RECORDS FOR DATAGROD
            sqlda = New SqlDataAdapter(sqlcmd)
            sqldataset = New DataSet
            sqlda.Fill(sqldataset)
BH READ DIRECTLY FROM THE DATABASE
            'Dim
R As SqlDataReader = sqlcmd.ExecuteReader
            'While
R.Read
            'MsgBox(R.GetName(0)
& ": " & R(0))
            'End
While
            SQLCon1.Close()
        Catch ex As Exception
            MsgBox(ex.Message)
            'will
close connection if still open
            If SQLCon1.State
= ConnectionState.Open Then
                SQLCon1.Close()
            End If
        End Try
    End Sub
End Class
A code for one of my button which views displays data grid contains the following code:
Private Sub Button1_Click_1(sender As Object,
e As EventArgs) Handles Button1.Click
        If SQL.hasconnection
= True Then
            SQL.runquery("select
* from tablea")
            If SQL.sqldataset.Tables.Count
> 0 Then
                DGVData.DataSource = SQL.sqldataset.Tables(0)
            End If
        End If
    End Sub
I am fairly new to vb.net and have read a few books and followed a few tutorials on youtube, what I would like to know is, are there any disadvantages
to the way I have connected to a SQL database using the SQLControl.vb. A lot of the vb books include data adapter and dataset within the form, I'm not sure if I'm following best practice by have the connection details outside of the form.
My other question is, I have created two connections in the SQLControl and call these connections within the same form using the same data adapter
and dataset. It all works fine but I just wanted to know of any potential issues?
Public SQLCon As New SqlConnection With {.ConnectionString
= "Data Source=;Initial Catalog=;Integrated Security=True"}
'connection 2
    Public SQLCon1 As New SqlConnection With {.ConnectionString
= "Data Source;Initial Catalog=;Integrated Security=True"}
Thanks

My other question is, I have created two connections in the SQLControl and call these connections within the same form using the same data adapter and dataset. It all works fine but
I just wanted to know of any potential issues
1) You are not using Sepration of concerns for a solution that is doing data access, like using a DAL.
http://en.wikipedia.org/wiki/Separation_of_concerns
2) You are directly issuing SQL commands at the UI, leading to sql injection attacks.
3) You are not using a UI design pattern, which leads you to tightly couple database activity to the UI.
http://www.codeproject.com/Articles/228214/Understanding-Basics-of-UI-Design-Pattern-MVC-MVP
@System243trd, parameters are important to prevent SQL injection attacks (people will insert SQL commands into the database if you do not perform basic checking of what you are passing to the database). If you write a stored procedure try to make
the variables the correct SQL server data type to avoid problems later of people trying to call it directly.  Darnold924 is right, I see no code to prevent against SQL injection attacks. In addition, during development in some instances LocalSQLDB
database system is used and during deployment you usually need to use the production SQL server database. Moreover, Linq-to-SQL is used on Windows Phone 8.1 and it is required for phone development later and so I highly recommend learning
it if you plan on developing windows phone applications.
@System243trd, If you want the code for the windows phone app I think it uses the MVVM model or that might be for universal apps or regular windows phone apps. I have been using the windows phone Silverlight pivot or panorama template (it might
be pieces of both). I've already submitted to the windows phone marketplace and it had to go through certification first. I plan on later making an article on it but I need to first fix one or two simple problems I have with it. Here's a link to
the source code if you later want to look at the source code (in vb.net):
https://jeffsblogcodesamples.codeplex.com/downloads/get/1445836
Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - Sherlock Holmes. speak softly and carry a big stick - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog
- http://www.computerprofessions.us

Accessing an SQL Server Database created by MS Access Web App

1.I have tried to use MS Access Web App which has created an SQL Server Database. I would like to access the database using SQL Management Studio Express 2014. In access I can see the server name on windows.net and the database name but I do not know
how to connect to this using SSMS Express 2014. Can you please help?
2.I also want to view our emails on MS Exchange in real-time. In MS Access Jet I can do this by linking the folders as tables. Is there a way of doing this in SQL Server? If not can I have a separate MS Access Jet with linked tables which I can then link into
my SQL Server as an OLEDB Linked server?
3. If going for the Linked Table in Jet solution where can I store it so that my MS Access Web App will have access to it?

Hi gkounis,
I don't think it support link MS Access Jet with linked tables in SQL Server.
Can you share some info about your MS Access Web App?
Regards,
Black

Is it possible to have different authentication mode for SQL Server Database Engine and corresponding SQL Server instance?

Hi,
I have installed the x64 SQL Server 2008 R2 Express with default settings and run MBSA 2.3 (using default settings too). It shows three SQL Server instances: MSSQL10_50.SQLEXPRESS, SQLEXPRESS and SQLEXPRESS (32-bit). For the first, authentication
mode is Windows, for the rest two - mixed. Here https://social.msdn.microsoft.com/Forums/sqlserver/en-US/03e470dc-874d-476d-849b-c805acf5b24d/sql-mbsa-question-on-folder-permission?forum=sqlsecurity question
about such multiple instances was asked and the answer is that "MSSQL10.TEST_DB
is the instance ID for the SQL Server Database Engine of the instance, TEST_DB", so in my case, it seems that MSSQL10_50.SQLEXPRESS is the instance ID for SQL Server Database Engine of the SQLEXPRESS instance.
I have two questions:
1) How can it be that SQL Server DB Engine instance has different authentication mode than corresponding SQL Server Instance?
2) Why 32-bit instance reported although I installed only 64-bit version?
Also, this https://social.technet.microsoft.com/Forums/security/en-US/6b12c019-eaf0-402c-ab40-51d31dce968f/mbsa-23-reporting-sql-32bt-instance-is-running-in-mixed-mode-when-it-is-set-to-integrated?forum=MBSA question seems to be related to this
issue, but there is no answer :(.
Upd: Tried on clean Windows 8 installation and Windows 7 with the same result.

Because I DO NOT want the three people who will be having access to the production SQL Server to also have access to the primary host ProductionA. Since I have to allow them to RDC into the box to manage the SQL Server, I figure why not create
a separate VM for each one of them and they can RDC into those instead.
Does this make any sense?
Any tips are greatly appreciated. The main reason for doing this is because the three people who will be accessing the box, I need to isolate each one of them and at the same time keep them off of the primary ProductionA.
Thanks for your help.
M
Hello M,
Since you dont want the 3 guys to have access to Production machine A.You can install SQL Server client .By client i mean SQL server management studio(SSMS) on there local desktop and then create login for them in SQL Server.Open port on which your SQL server
is running for three of the machines so that they can connct.Now with SSMS installed on each machine each can connect to SQL server from there own machine.
I would also like you to be cautious with giving Sysadmin privilege to all three of them ,first please note down what task they would do and then decide what rights to be provided.
Your option will also work but you need to create 3 VM for that .Which is more tedious task.
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Full Database Backup in DB13 for MS SQL Server databases

Hello,
We have some SAP systems using the MS SQL Server database. I want to know if it is possible to setup the Full Database Backup option in transaction DB13 to store the files in a hard disk space.
I already did this type of configuration in SAP systems in Oracle databases and for this I used the init<SID>.sap where we can put all the configuration, for instance the disk path where we want to save the backup files! But for MS SQL Server databases, in DB13, I don´t know how to do that, when I add the "Full Database Backup" option in DB13, this show me some options but only for tape, but I don´t want to store the backup files in tapes, I want to store/save the files on the server disk itself or else to an external disk but I don´t see where I can set this way of storage!
This is what you see in DB13 (when using a MS SQL Server database) in "Full Database Backup" and as you see I only have options for TAPE not for a disk or other type of storage! How can I do that? (if that is possible):
Can you help me please?
Kind regards,
samid raif

Hello Raja
Sorry for the delay of my answer! Many thanks for that tip, it helps a lot and it solve the last error/problem that I reported here, in fact, the problem was we had named the device with two words containing a space. So we removed that space from the backup device (in SQL management studio) with one word only and the job runs successfully without any errors!
It works in Development and Quality systems but in our Production system (AM1) the Full backup option in DB13 stopped with the following error, in fact the error is on verification of backup, it means that the Full backup finished with success, but when it does the backup verification, the job in DB13 stops with an error, the following one:
***************************** SQL Job information   ******************************
Jobname:    SAP CCMS Full DB Backup of AM1 [20140417103726-4-103726]
Type:       TSQL
DB-Name:    AM1
For Run:    20140417 10:37:26
**************************** Job history information *****************************
Stepname:   CCMS-step 1
Command:    declare @exeStmt nvarchar(2000) exec am1.sap_backup_databases @dbList=
            "AM1",@r3Db="AM1",@bDev="fullprd",@expDays= 27,@jobName= "SAP CCMS Ful
            l DB Backup of AM1 [20140417103726-4-103726]",@bkupChecksum="Y",@bkupT
            ype="F",@nativeBkup="N",@exeDate = "20140417103726",@bkupSim = "N",@fo
            rmat = 0,@init = 0,@bkupDb = "AM1",@unload = 0,@exeStmt = @exeStmt OUT
            PUT
Status:     (success)
Message:    3014
Severity:                                                                                                                                                                                                                                                    0
Duration:   4 hours(s) 41 min(s) 22 sec(s)
Last msg:   Executed as user: am1. Processed 7434328 pages for database 'AM1', fil
            e 'A01DATA1' on file 1. [SQLSTATE 01000] (Message 4035) Processed 315
            1504 pages for database 'AM1', file 'A01DATA2' on file 1. [SQLSTATE 01
            000] (Message 4035) Processed 4574152 pages for database 'AM1', file
            'A01DATA3' on file 1. [SQLSTATE 01000] (Message 4035) Processed 44363
            92 pages for database 'AM1', file 'A01DATA4' on file 1. [SQLSTATE 0100
            0] (Message 4035) Processed 25598 pages for database 'AM1', file 'A01
            LOG1' on file 1. [SQLSTATE 01000] (Message 4035) BACKUP DATABASE succ
            essfully processed 19621974 pages in 16881.638 seconds (9.521 MB/sec).
             [SQLSTATE 01000] (Message 3014). The step succeeded.
                    <------------- End of Job Step History --------------->
Stepname:   CCMS-step 2
Command:    declare @exeStmt nvarchar(2000) exec am1.sap_verify_backups @nativeBku
            p = "N",@bkupSim = "N",@bDev = "fullprd",@bkupChecksum = "Y",@exeDate
            = "20140417103726",@unload = 1,@dbCnt =1,@exeStmt = @exeStmt OUTPUT
Status:     (failure)
Message:    3201
Severity:                                                                                                                                                                                                                                                   16
Duration:   0 hours(s) 8 min(s) 30 sec(s)
Last msg:   Executed as user: am1. Cannot open backup device 'fullprd(\\10.0.0.45\
            backupsap\prd\prdfullqua.bak)'. Operating system error 1265(error not
            found). [SQLSTATE 42000] (Error 3201). The step failed.
                    <------------- End of Job Step History --------------->
**************************** Job history information *****************************
Can you help me please with this one!? Can you tell me why in verification it stops with that error?
Kind regards,
samid raif

Convert SQL server database into SAP readable (encrypted) XML for SAP tool?

Could anyone kindly let me know what is the procedure to convert SQL server database into SAP readable (encrypted) XML for SAP Authoring tool???

So If I understood it correctly there an existing propriertory question bank with SQL server. You are looking at an option to migrate all the tests and questions from the existing system to the LSO system. Right ?
I am still not clear on the xml conversion. Have you guys found a solution which could be achieved through a xml file ?
am not aware of a way through which you could import only a xml file and create tests/questions. If you have a sample xml file then forward me so that I could do some testing on my end.As per my knowledge you could do one of the following. I
1. Create the tests and questions manually in Authoring Environment. It will be a time consuming task. Based on the number of questions you have you might have to assemble a team of content developers to acheive this.
2. Alternatively, you could create a Adobe Flash based assessment. The Flash component would be the front-end and will read from a xml file to display the questions and to drive the funcationality. This would be a easier and less time consuming than creating the assessments manually in authoring environment. However, you might miss out some of the functionality available in the Test Author of Authoring Environment unless you have all the functionality replicated inside Flash. This would require one time effort in creating the Flash template and the xml file structure. Once that is created you could create multiple assessments by just replacing the xml file. If you select this approach then you would have to ensure the data from SQL is converted in the desired xml format required by your Flash component.
Please let me know if you require any further guidance or clarification regarding this.
Regards,
Ravi Sekhar

SQL Developer 2.1.0.63 - Export Data menu missing for SQL Server databases

Hi
The Export Data menu only appears for Oracle databases in this version, it does not appear for SQL server databases.
To demonstrate:
Press F9 to run query
Right click on Query Result data
For Oracle an Export Data sub menu appears
For SQL server no Export Data sub menu appears
This worked in previous versions.
Is this functionality going to reappear?
Thanks
Dave

Hi,
Looks like this is exactly the same problem for third party connections as I have the exact same issue for mySQL.
I had to apply 1.5.5 version to fix it.
Hope we're going to have this solved !
Thanks,
JP

Code for connecting to a Microsoft SQL server database

Hi
What is the code for connection to a Microsoft SQL server database using JSP? I know the structure of the code but i do not know the driver name. Any importing required besides java.sql?
Thanks

Back up there. JSP's should never contain any
database code. You should write a bean to handle
database transactions and call that from your JSP.I agree wholeheartedly with that.
Why didn't you consult google to help you with your
problem? The answer is on the MS website.
http://support.microsoft.com/default.aspx?scid=kb;en-u
s;313100This is correct, too. Isn't Google installed on your machine?
%

Free JDBC 4.0 driver for Microsoft Sql Server database

Is there any free JDBC 4.0 driver for Microsoft Sql Server database? The jTDS driver is JDBC 3.0 driver. http://jtds.sourceforge.net/

Sooooooo...
what's wrong with the driver provided by Microsoft themselves? Which is JDBC 4. And free.

SharePoint 2013 SQL Server Edition for BI Features - must be on SharePoint SQL Server?

I need to install SQL Server 2012 for a new SharePoint 2013 installation.
Let's say I want to use the BI features of SharePoint 2013 like PowerView.
I already have a separate SQL Server running SQL Server 2012 BI Edition that is used as the database server for our data warehouse and some apps. But this SQL Server will not be used to house the SharePoint 2013 databases.
Do I need to install SQL Server 2013 BI Edition on the SharePoint 2013 SQL Server (where the SharePoint 2013 databases will be housed) or can I used SQL Server 2013 Standard Edition on that server and utilize the BI Edition on the data warehouse server to
use the BI features of SharePoint?

Yes, BI or Enterprise must be installed on the SharePoint server in order to integrate SSRS. PowerPivot can be on a separate server with just a download (http://www.microsoft.com/en-us/download/details.aspx?id=35577) for certain components residing on
the SharePoint server. This will give you PowerView, as well.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Migrating SQL Server database to Oracle 8i - any known issues

Hi,
I am in the process of migrating SQL Server database to Oracle 8i for testing purpose.
When I do migrate SQL Server database to Oracle 8i, am I doing any harm to the exiting
SQL Server database? Would the users be able to use SQL Server database as usual?? Are
there any known issues in this regard?
Please reply.
Thanks.
Ramesh

Hi,
I am in the process of migrating SQL Server database to Oracle 8i for testing purpose.
When I do migrate SQL Server database to Oracle 8i, am I doing any harm to the exiting
SQL Server database? Would the users be able to use SQL Server database as usual?? Are
there any known issues in this regard?
Please reply.
Thanks.
Ramesh Hi Ramesh!
The Migration Workbench does not make any modifications to the SQL Server database. It only reads information from it. Your users should be able to use the SQL Server database as usual.
Please note however that if you migrate the data over to Oracle using the Migration Workbench and your users continue to enter/update data in the exiting SQL Server database then you may need to move all that data over again in order to have the most up to date data in the Oracle database.
thanks
- Garry

Migrating OBIEE Repfrom Oracle database to SQL server database in Solaris.

Hi,
I need inputs in how we would migrate our connections in Repository from Oracle database to SQL server database in Sloaris server.
Is there a complication here.
Regards,
Bhavik

Well that makes more sense, you probably have phrased your question better. Microsoft SQL Server Connectivity Components are not supported in any other operating system than Windows. So you will not be able to use the SQL Server native drivers to connect to your SQL Server. ODBC it's an option but there aren't many ODBC drivers for Unix systems. Luckily for you OBIEE includes the DataDirect ODBC drivers and supports using them to connect to a SQL Server. Check [the documentation|http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/e10416/general_101331.htm#sthref9] on how to use them. Having said that I would say that whoever is pushing to move your DWH to SQL Server should consider also moving OBIEE to a Windows server to be able to use the SQL Server native drivers to connect to SQL Server.
PS: No needs to post 3 times. :-)

My Experiences re: Migrating SQL Server Database to Oracle

I am using SQL Developer EA4 for thsi conversion, best attempt yet.
I had numerous problems with this conversion.
1. The wizard asked me to specify the new Oracle database; instead it just ignored this information and created an Oracle database similarly named as the SQL Server database. I also noticed a file name "Migration.out" was produced; it contained errors such as:
Error starting at line 3 in command:
CREATE USER Emulation IDENTIFIED BY Emulation DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP
Error at Command Line:3 Column:36
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges" and
Error starting at line 4 in command:
GRANT CREATE SESSION, RESOURCE, CREATE VIEW, CREATE MATERIALIZED VIEW, CREATE SYNONYM,CREATE PUBLIC SYNONYM TO Emulation
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges" and
Error starting at line 7 in command:
CREATE USER dbo_COREv13 IDENTIFIED BY dbo_COREv13 DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP
Error at Command Line:7 Column:38
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges" and
Error starting at line 8 in command:
GRANT CREATE SESSION, RESOURCE, CREATE VIEW, CREATE MATERIALIZED VIEW, CREATE SYNONYM TO dbo_COREv13
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges".
I followed all of the steps listed in the "Help" section re: Migrations but still ended up with these errors.
2. My schema consists of 1000+ tables; approximately 10 tables were NOT created. When I copied the SQL from Migration.sql making NO changes and pasted it into the new Oracle database it created without issues.
3. While the conversion is taking place, different objects (constraints, indexes, foreign keys, etc) are shown to be copied; their appears to be ordering of these items. Shouln't a dependancy tree be established, and object converted based on this?
4. Several tables, in my case about 250 tables did NOT get any data copied across. No reasons given.
5. A log of all activities should be produced for review and completeness.
6. I tried to use the "Migrate select tables" option but met with no success. Apparently, it makes an assumption that both the "source" and "target" databases wil be of the same type (ie both SQL Server or both Oracle); this does not make any sense to me since the point of the exercise is to migrate data from one database vendor to another. Obviously, different database vendors use differing datatypes for similar data (ie dates).
7. I noticed in the "Migration" sql that the "Connect" statements are not correct; they were missing the "instance name" portion.
8. Also, when I looked in the "MIGRATION" sql, I could not find any entries for the last step of the conversion - the movement of data from SQL Server to Oracle. Is this intentional or an oversight.
I dont want to appear negative on this Migration; I have used SQL Developer since it inception; in my opinion this is the best attempt to date.
Murray Sobol

Hi Murray,
Thanks for this feedback.
There is a lot of questions here, I think some of it boils down to misunderstandings, which we should clarify in the doc.
Hopefully Ill get a video of a migration online soon as well.
But here is a brief break down.
*1.*
"The wizard asked me to specify the new Oracle database; instead it just ignored this information and created an Oracle database similarly named as the SQL Server database."
So this relates to Step 7 of the Migration Wizard. Where you can select the target connection.
SQL Developer doesn't ignore the Target Connection you selected, It just uses it to connect to the target database , not the target schema.
SQL Developer generates a new target schema for the migrated objects. It standard approach is not to generate objects directly into an existing Schema.
The Target Connection is used to create all the migrated objects (including new Oracle Schemas) in your target oracle database. So you should choose an Oracle Target Connection which has enough privileges to create new Schemas and Objects.
But as you have found, it doesn't generate the migrate objects , like tables, ... , directly into your chosen Target Connection.
From the errors you encountered it doesn't sound like the Target Connection (and the underling Oracle Schema) doesn't have the privileges to create other Schemas.
If you use something like a connection to the SYSTEM schema on your target database, it should run OK.
It wont create any objects in SYSTEM, rather it will use SYSTEM privileges to create a new schema (ex: dbo_Northwind) and populate it.
You don't have to use SYSTEM, but you do need a schema with enough privileges to create other schemas.
That is the straight forward way. But if you really need to generate into an existing schema the following steps can be taken.
a)rename the schema under the Converted Database Objects
b)Right click "Converted Databases Objects" and choose generate. it will kick off the Migration Wizard in the correct place
*2.*
My schema consists of 1000+ tables; approximately 10 tables were NOT created. When I copied the SQL from Migration.sql making NO changes and pasted it into the new Oracle database it created without issues.
When you say Migration.sql , is the entire generation file , which can be found in your <outputspecified>/generated/<projectname.modelname>.sql ?
When your say "pasted it into the new Oracle database" , are you running it in SQL Developers SQL Worksheet using the Target Connection.
Basically your migration is all out of shape once the target Schemas are not created. So the above issues (insufficient privileges) has to be resolved first.
Please post back if it is still an issue.
*3.*
While the conversion is taking place, different objects (constraints, indexes, foreign keys, etc) are shown to be copied; their appears to be ordering of these items. Shouln't a dependancy tree be established, and object converted based on this?
Objects are converted in a particular order and their dependencies are persisted so that they can be generated in the correct order.
Are you seeing an issue?
*4.*
Several tables, in my case about 250 tables did NOT get any data copied across. No reasons given.
I'm surprised any tables were populated with data due to the target schema not being created.
The online data move is pretty simple and it does not report or recover very well from issues.
If you are having difficulties once item 1. is resolved, please post an example of the source table and I will give it a go.
For better control of the data move with much more powerful tweaking, error handling, reporting and performance try the offline data move.
SQL Developer can created a suite of scripts which use SQL Servers BCP tool to dump out the data to dat files, and Oracle SQL*Loader tool to insert the data in the dat file into Oracle.
*5.*
A log of all activities should be produced for review and completeness.
The output/generated/<projectname.modelname>.out provides the output of running the generation script.
The migration reports http://dermotoneill.blogspot.com/2010/11/migration-reports-30.html outline what happens during the migration.
Apart from online data move issues, is there any other data missing?
*6.*
I tried to use the "Migrate select tables" option but met with no success. Apparently, it makes an assumption that both the "source" and "target" databases wil be of the same type (ie both SQL Server or both Oracle); this does not make any sense to me since the point of the exercise is to migrate data from one database vendor to another. Obviously, different database vendors use differing datatypes for similar data (ie dates).
Do you mean "Copy To Oracle" ? This option is intended to migrate tables from non Oracle databases like SQL Server to Oracle.
Can you give more details on what issue you are seeing.
*7.*
I noticed in the "Migration" sql that the "Connect" statements are not correct; they were missing the "instance name" portion.
The generation script is meant to be run using SQL Developers SQL Worksheet. I think you only get this "instance name" issue if running from SQL*Plus.
Can you confirm
8. Also, when I looked in the "MIGRATION" sql, I could not find any entries for the last step of the conversion - the movement of data from SQL Server to Oracle. Is this intentional or an oversight.
The online data move is performed separately from creating the objects. It is not script based, it uses JDBC to pump the data from the source database to the target database.
In summary , I would
a) Create a connection to your Target database using your SYSTEM schema
b) Right click on your "Converted Database Objects" and choose "Generate Target"
c) Choose your new "System" connection as the Target Connection
d) Follow the Migration Wizard to the end.
You will end up with a new target Schema and the migrated objects in it.
Check the .out file to see the errors
and the migration reports http://dermotoneill.blogspot.com/2010/11/migration-reports-30.html
Regards,
Dermot
SQL Developer Team.

Move SQL Server database for App Controller

Similar Messages

Maybe you are looking for