We have integrated system , what we are doing in the integration process is our invoices data is going to insert in the oracle ebs R12 (oracle database 12c) through SQL Server linked Server using ODBC driver but when this process starts on the sql server with the help of sql server agent service, then process shows preemptive_com_getdata wait type and the sql server consume all the available RAM on the server and then OS start hanging even task manager takes time to open and then finally sql server services restart automatically
This issue occurring after upgraded on the Oracle 12c but there is no any complaint from the Oracle database side
Second thing is that we observed that ping from sql server to oracle 12c database is giving sometime request time out
SQL Server 2008 R2 with SP3 on Windows Server 2008 R2,Oracle Database 12c (12.1.0.1) on IBM AIX 6.1 TL9,Oracle Driver version (12.2) ,
What was the reason behind this ?
I took a backup of a database in SQL Server 2008 R2 via SSMS backup utility and restored the same backup in SQL Server 2014 via SSMS backup utility and the database restore. It was successful but am not seeing any tables in SQL Server 2014 after restoring the database. Can someone help me to restore the SQL Server 2008 R2 database backup (.bak) in 2014?
The sql 2008 r2 database backup file should be completely compatible on sql 2014. you can try to restore the database on sql 2008 r2 at first, and check if the table was deleted before the backing up.
I have been using this connection string with no problem on a number of databases and MS operating systems. Windows Server 2003, 2008 R2 and 2012 R2 Eval, all Express versions.
I am now trying to deploy to a new Windows Server 2012 R2 installation and I am getting some errors. I have the SQL Server 2008 R2 installation on the Windows Server 2012 R2 machine.
My con string:
connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\myDB.mdf;Integrated Security=True;User Instance=False" ProviderName="System.Data.SqlClient"
I think this must have something to do with the installation sequence of the components on the new server.
I have in the past been able to simply copy myDB.mdf to basically any web server and open or access the DB tables. This DB includes an ASP membership for the web site that it is tied to.
Here is the error:
CREATE DATABASE permission denied in database 'master'. An attempt to
attach an auto-named database for file
C:\inetpub\techTran\App_Data\myDB.mdf failed. A database with
the same name exists, or specified file cannot be opened, or it is
located on UNC share.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: CREATE
DATABASE permission denied in database 'master'.
I thought I understood what this error was. I have checked permissions and they match the other servers where this database has been deployed. My SQL Server installations are basically all the same. The only difference here is that this is Windows Server 2012 R2 on a VM. Or I did not install the SQL Server 2008 R2 the same way I have done in the past 5 servers I have set up. (Which I am guessing is probably the case.)
UPDATE: Uninstalled and reinstalled SQL Server and SSMS.
I know there is only one database name on the server called myDB.mdf, so I don't believe the "same name" portion of error. I have added security to the db so that it can be opened and I even installed Visual Studio 2012 on the server to be certain that the db could be opened. I can run the full app on the localhost (server 2012) but I can not access it over a web connection.
I believe the specific error message relating to
CREATE DATABASE permission denied in database 'master'
is the issue.
I have never seen this error before.
I typically assign NETWORK SERVICE account to the database to allow access and this is how this one is set up as well. I also thought this might be a connection string issue. But this same string has worked on 4 different servers now with no changes. Server 2003, 2008 R2, and 2012 (demo platform)(all Express versions), now in production this is failing.
The home page loads and then the login throws the above error.
Your connection string says AttachDbFilename=|DataDirectory|\myDB.mdf. Well, your path must have changed in one place (SQL Server) and not the other (app configuration). AttachDbFilename will try to create a new DB if it can't find that file. That's probably your error.
As an aside, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 all have differences, especially with security and in particular with how SQL Server behaves, but you keep using them interchangeably. That makes it very confusing to tell what's going on. Also, your connection string says Data Source=.\SQLEXPRESS. Is this SQL Server Express? Because that has important differences with most other editions of SQL Server, too. More recent editions are very similar to Standard edition, but the older the edition, the more quirks it has. They're generally considered different beasts.
SOLVED: I am not sure how this happened or perhaps why it didn't happen. But for some reason the installation of SQL did not add the NETWORK SERVICE account to the sysadmin Server Role. I cross referenced this with the SERVER 2003 installation where SQL 2008 R2 is also running, and discovered that the sysadmin SQL Server Role included NETWORK SERVICE in my correctly functioning environment. So once I added the user account to this role, everything came up fine.
I believe this might have been an issue during the installation of SQL 2008 R2. I did specify NETWORK SERVICE, but for some reason it was not provided the role.
we are planning to move biztalk database from one place to another as well as upgrade the sql server.
the initial database is in sql server 2008 R2 and target is sql server 2012.
but the thing is that we have to set up database on another system,
i tried to search it on msdn but they are providing reference to upgrade from 2005 to 2008 , or moving database from one server to another.
do you think that will work in my case !!
i found this article.http://msdn.microsoft.com/en-us/library/ee378547%28v=bts.10%29.aspx
relating to upgrading as well as moving..
but this is quite older one.
how can i upgrade as well as move biztalk database from sql server 2008 R2 to sql server 2012 on a different system (side by side upgrade).
do i have to follow same steps as upgrading a normal database from sql server 2008R2 to sql server 2012 or some other one ??
As long as the SQL Server edition (2012 in your case) you are migrating to is supported by your BizTalk Server edition, you can follow the procedure to move BizTalk databases.
You can check the version compatibility here.
I need to backup Oracle 10g Database from Windows Server 2003 R2 where command line is disabled by some virus problem. RMAN and other graphical utilities are also not working. Only possible thing is that I could take OS file backup of the running database (it can't be stopped also). I do have a trace control file of the database. Please provide some solution so that I could restore the database to a new server.
You can create a backup using Oracle DataPump through SQL:
http://docs.oracle.com/cd/B19306_01/appdev.102/b14258/d_datpmp.htm
Here are some examples how to use it:
http://psoug.org/reference/dbms_datapump.html
http://jhdba.wordpress.com/2009/05/06/237/