When I want to expand database tables in SQL Server but not to see because it's taking more time to expand
I'm migrating tables and views from Oracle to SQL Server using SSMA. I have a number of tables that have columns with SDO_GEOMETRY datatype, SQL Server does not work with that.
How could I map SDO_GEOMETRY to SQL Server? If it's not possible, then what should be done using SSMA?
And is it possible to work out this issue without editing anything in the Oracle database (just using SSMA or SQL Server)?
Oracle use an internal specific Oracle format of geo data that is non standard... Convert it to WKB or WKT and it should works.
I have Oracle database 11 g in which I have many tables. I want to replicate few of these tables in SQL server so whenever a new record is inserted in oracle table I also want to update in SQL server table. I have created linked server but don't know what to do next. Kindly guide me how can I replicate changes on SQL server side.
Use Goldengate (An Oracle tool) that can do bi-directional replication from Oracle to Sql Server. See this:
http://www.oracle.com/us/products/middleware/data-integration/goldengate/using-gg11g-for-sql-server-1489372.pdf
When querying sql server view data (it does work when I query a table), I receive only the header but no rows. In sql server profiler I can see that the sql statement looks correct (and I get data from the view when I execute the statement in sql server management studio) but the read and cpu counters are minimal compared to a direct query. There are no linked servers involved, username in profiler is the same for both access methods.
One of the subviews was filtering using for APP_NAME()... which is "Microsoft Office 2013" when one queries from Excel and "Microsoft SQL Server Management Studio" when using SSMS. This cleary explains why Excel did not get any rows...sorry for bothering.
Are there any tools to convert SQL Server 2014 database to 2012?
I tried Generate Script but the generated script with data is too large and SQL Server Management Studio did not execute it, I need to have both schema and data.
To my knowledge, there are basically three two options for migrating a database to a lower version of SQL Server, without using 3rd party tools:
Generate Scripts (not really suitable for large amounts of data)
Custom Scripting and BCP or Import/Export Wizard
SQL Server Integration Services (Transfer Database Task)
First option is not suitable in your case, as noted.
Second option is to simply script the structure of the database, and then use the Import/Export Wizard to copy the data, one table at a time. Note, that if you have foreign key constraints in your database, you might want to disable the constraints until after you have populated all your tables with data. This blog post explains in details how this can be done.
Third option uses the SISS Transfer Database Task which basically uses SMO to create the objects on the destination server and then transfers the data. This is the recommended way of migrating a database between SQL Server instances of different versions. SSIS requires that you have installed SQL Server Data Tools - Business Intelligence (SSDT-BI) for Visual Studio. Before SQL Server 2012, this was called Business Intelligence Development Studio (BIDS). You can download these here:
Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013
Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012
If you don't have Visual Studio, SSDT-BI / BIDS is included in the SQL Server installation.
Use the script, but instead of executing it trough Management Studio, use the lightweight sqlcmd utility.
http://msdn.microsoft.com/es-es/library/ms162773.aspx
Oh well, Dan's second option does not work: after installing SSDT-BI for VS2013 and configuring the Database Transfer Task it says that the version of the source database instance has to be lower or equal to the version of the destination database instance: so, a migration from 2014 to 2012 (or in my case 2008R2) is not possible.