What are known error/issues from SQL Server 2008 to SQL Server 2017 version up gradation at procedure/database object level to comply/fix/recode at application level.
Also, I need to know whether my current environment (SQL Server 2008) procedures, functions, trigger, jobs scripts will be compatible with SQL Server 2017 or if not, what part/features need to be rewritten?
i am trying to restore bacpac file to sql server MANAGED INSTANCE, HAVING THE SSMS ON MY LOCAL COMPUTER,
AND ITS THROWING THIS ERROR
k
We are migrating to a new upgraded hardware/software from Sql 2008 R2 to SQL 2017. What is the best, most efficient way to migrate sql agent jobs?
Script out each job and runt the script on new server
OR
backup and restore system databases?
Thanks.
Hi,
On prem SQL Server DB have File Stream enabled Files\DB to read through SSIS packages, How to migrate File Stream enabled DB's SQL Managed Instance or is there any possible Work Arounds ?
Thanks in Advance,
Krish
Hello Bros,
I'm new to Hadoop and i'm planning to connect Hadoop to PDW-APS, my Hadoop is Cloudera from Oracle and i have Infiniband switches on both platforms.
does anybody have any instructions or steps or configurations must be applied to do this?
Regards
I want to move three large databases form old servers to new servers. I an concerned the restore will take a long time, and hoping that detach and attache would be faster. please let me know if my assumption is correct. Also let me know if that will create all the users and roles on the new server as they were on the old server.
I am aware that I will have to migrate SSIS and SQL agent jobs manually, but, Is there anything else I need to be concerned about if I use detach / attach method.
Thanks.
DMA v3 (January 2017)
After running assessment, reports could be exported in csv or json formats.
I would like to know if there is an option to open previously running assessment in DMA itself. There is no option as Save Assessment.
May be I am missing something, but we create a Progject, then there is an option Open... so I suppose to have some saved project for opening...
However when I try to close DMA, the message appear:
can I open json file in DMA? or is it normal to run the report and then lose it. I would like to have an option to easily open it in DMA...
What I am missing?
Thanks.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis
Hello,
After I installed SP2 and CU1 update on SQL Server 2016, I'm receiving and error related like "Change Tracking autocleanup is blocked...". I googled but, there is no resolution.
Could you please help me?
Change Tracking autocleanup is blocked on side table of "xxx". If the failure persists, check if the table "xxx" is blocked by any process .
Error: 22123, Severity: 16, State: 1.
I am converting my Access 2007 backend database to SS2k5. Been doing it for a long time. I've now gotten to the point where I'd like to refresh the SS2k5 data periodically during the day so testing goes smoothly. I figured out how to use SSMA GUI with a saved already-executed project to migrate the tables only. (I'm migrating about 95 of the 100 tables.) I'd like to cast that process into a command line so I can schedule it to run a couple times a day automatically.
You SSMA experts.... What are the basic steps?
HI guys,
I'm looking for hours now to find a good solution, but I can not find any answer.
I have an MS Access DB with a lot of forms, reports, etc...
Now I always worked offline on the MS Access DB, but now I we are 2 people that must work on that DB.
So I decided to convert the Access DB to SQL server 2014.
With the tool SSMA, it's quit simple to convert all my tables and export them to the sql server, and then relink all forms, reports to the new linked tables. So far so good, all works.
but every time we startup the MS access, we must enter the username and password to the sql server, this is not what we want, we just want to work with one of these 2 options:
1. we store the password while migrating the db to sql
2. after conversion we want to use a DNS ODBC connection that is allready made on our computer.
if we change the tables to search for new connection and we do choose our DNS ODBC connection,(since there we can say to store the password in it), then all is okey, we delete the old linked table, rename the new one to the same name of the old table, and it works... only we lose a lot of settings, like if we use the old linked table then dates are fine showed in our forms like DD/MM/YYYY, but if we relink the table with the new ODBC DNS connection, then dates are messed up.
is there any way we can solve this, since very very enoying to have all setup mixed up.
and then 2nd question, if I give the MS access file to my partner, on his computer, without he has any ssma software on his computer, will he be able to open the DB,work in it and will it work if we have both on our computer this open?
thx for any clue or tip, after 6 hours search, I must say I didn't found any solution/answer.
Thanks -NK
I used SQL Server Migration Assistant to asses what changes might be needed in our databases, before we migrate those from SQL 2008 R2 to SQL 2017. The tool is showing several stored procs that use order by 1,2,3 type of syntax.
" <proc name> uses ORDER BY clause specifiying ordinal column numbers as sort columns, this is not supported in database compatibility level 90 and higher. ..."
I created a test stored Proc on SQL 2017 database that uses the following code: SELECT * FROM [AdventureWorks].[dbo].<tablename>
order by 1,2,3
When I run this SP, I was expecting to see an error because the migration assistant tool suggested that ordinal numbers in sort columns is not supported, but, to my surprise, it worked and also did the sorting as expected. Why doe SQL server migration assistant suggest that it is not supported for compatibility level 90 or higher. I tested on a database with compatibility level 140 and it still worked.
Thanks, in advance.
Hello,
I am looking to lift and shit current setups to Azure but I am coming across a road block. Currently in our environment we use SQL and multiple instances for our database tables that are all assigned ips. I can drop this ip into the nic of the vm and its accessible but we are using windows clustering to control sql clusters and the ip wont follow to the other vm when we fail over. I read that a load balancer can help with this scenario however, when using the load balancer and i put in the ip of the instance the health check will not return clean so that the traffic can route. I have the frontend ip setup as the instance ip(not the cluster ip) and it forwards to the backend servers on the port that was specified for the individual instance. Any help would be appreciated. Thanks
We have a very old set of Sybase databases (version 11.9.2) that we’re planning to convert to SQL Server 2008. I’ve therefore downloaded the Microsoft SQL Server Migration Assistant for Sybase, but it is unable to find the Sybase drivers. Within the SSMA, when I attempt to connect to the Sybase server via ODBC, I get this message: “Unable to find specified provider. Sybase Data Access Connectivity libraries were not found on the machine. You can install them from Sybase product media or download it from Sybase web site”.
If I try to connect using OLEDB, I simply get “Cannot connect to data source”.
Trying to use ADO.Net gives me “Unable to find ADO.Net Provider files ‘Sybase.AdoNet2.AseClient.dll’ or ‘Sybase.Data.AseClient.dll’.You can install them from Sybase product media or download it from Sybase web site.”
The problem is that I do have the full Sybase client tools installed (I have both Sybase Central and SQL Advantage), so I would have expected the connection to work. In addition, I use Visual Studio 2010 and am able to connect to Sybase easily using the System.Data.Common.DbProviderFactory classes.
I’ve tried looking on the Sybase website but can’t find any relevant drivers anywhere – they don’t seem to be specifically listed. Does anyone know exactly what I would need to download or install in order to get this working? I’m using an old XP machine (one of the reasons I’m keen on this conversion is so that we can fully move up to Windows 7/8).
Thanks in advance for any help you can give me.
Is Australia Azure Gov. support Azure SQL Database?
My Email: Kevin.z@konnech.com
Please reply me ASAP.
Hello.
Recently I discoverd SSMA to assis in data migration from Oracle to SQL Server. But since I started studying and experimenting with it I had terrible performances issues. I'm not talking about data migration poor performance, but in fact even connecting
with the target and source databases is painful.
The first connection to the source database takes about 30 minutes. Half an hour just to past connect to Oracle. I inspected the Oracle activity and I saw that SSMA bombs it with a series of queries on the system tables like all_columns, all_constraints, all_objects FOR EACH SCHEMA. That's seems nonsense to since I connect directly to a specific user/schema, why does the thing needs to through every single schema on the database?
The connection to the target database is not better either, taking also about 30 minutes. Once again, I gave the database name to connect, why the heck does it need to go through every other database on the server?
Then it comes the migration phase. Note that I have precreated all the tables on the target database, so no conversions is being done here, just a data copy. Before effectivelly migrating the data I got several generic messages of "Object passed as parameter table", one for each table. The problem here is that it takes about one minute on each table. At the moment I have a sample of 220 tables (the schemas have about 600 or 700), so I expect more than 3 hours just to pass these tables as parameters? Really?
Once again, inspecting the Oracle side I see this same querie for each table being analyzed:
ELECT Ctrs.owner , Ctrs.constraint_name , Ctrs.constraint_type , Rcts.table_name AS r_table_name , Ctrs.delete_rule , Ctrs.search_condition , Ctrs.status , Ctrs.last_change , Ctrs.r_owner , Ctrs.r_constraint_name
FROM sys.all_constraints Ctrs ,
(SELECT DISTINCT Rcts.table_name , Rcts.owner , Rcts.constraint_name
FROM sys.all_constraints Rcts , sys.all_constraints Ctrs
WHERE Ctrs.owner = 'VIE2016' AND Ctrs.table_name = 'BI_COLUMN' AND Ctrs.r_owner = Rcts.owner AND Ctrs.r_constraint_name = Rcts.constraint_name) Rcts
WHERE Ctrs.r_owner = Rcts.owner (+) AND Ctrs.r_constraint_name = Rcts.constraint_name (+) AND Ctrs.owner = 'VIE2016' AND Ctrs.table_name = 'BI_COLUMN' AND Ctrs.constraint_type IN ('P', 'R', 'U', 'C')
So, what's the deal here? Didn't SSMA alread went through every object in every schema on the first connection? Why does it need to re-read each simple table for its constraints? Moreover, why query the ALL views? Of course it will take forever, why don't it go to the simple USER views? It would be way faster.
I tested a data migration with fewer tables but it was also disconcerting: 220 MB copied in about 30 minutes - excluding the connection and parameter passing time. Although I think I can tweak some
options like fetch size and threading to help this part, but still the overall performance of the tool really dissapointed me.
So, is there a way to improve this? Are there some options to avoid having to re-read all the objects over and over again? A friend once told me about a technique consisting in creating a view on the Oracle schema to fool SSMA into thinking its
accessing the ALL views, but I didn't get it right, specially because I see it prefixing whith the SYS schema.
Could somebody give me some advice or hints?
Oh, also worthing noting that I'm using the console version since I have to script the migration process. But even with the graphical version the performance was similar terrible.
Thenaks in advance for your help.
Hi Team,
I am trying to take a backup of master key in Azure SQL Server(DBaaS/PaaS) and SQL Data warehouse. since we do not have access in hardware in Azure platform(DBaaS/PaaS) hence getting following error while taking backup in default location.
Msg 40510, Level 16, State 1, Line 11
Statement 'BACKUP MASTER KEY' is not supported in this version of SQL Server.
My queries:
1. Does Microsoft take a backup of Master Key in DBaaS/PaaS Platform?
2. IF yes then , What is retaliation Policy of Master Key backup?
3. how can we restore Master key in DBaaS/PaaS Platform?
4. Do we have Microsoft Doc for Azure SQL Server for these detail?
Thank you,
Victor Rodniansky
Some of the servers are still using 2008r2 and there are more than 30 databases per server and about 30+ logins and 20+ sqlserver integration packages as well as several applications. Will log shipping be the most accurate process to move database on the new server. We also use VMware and can copy data from all drives from one server to another.
Since there are lot of unknown in the servers do you suggest in place migration? We are using Sql Server 2008R2 Standard edition