Solved

SQL Server 2012 Auditing

Posted on 2013-02-01
4
292 Views
Last Modified: 2013-02-09
I am trying to see what is causing an application connection to switch databases once connected. The custom app I have is to write to any database that I type into it with the designated credentials. When I connect to the SQL Server instance, I have a db1 and a db1_dev. I want to write to the db1_dev when connecting with the app, and the app does successfully connect, but then it writes to table1. I tested the app by entering a database name that doesn't exist and then it doesn't connect....so that indicates to me that the app is initially passing in the database name value that I am giving it, however somewhere in SQLServer 2012, it is defaulting back to db1. What can be done to troubleshoot the SQL Server to see what is causing the issue?
0
Comment
Question by:DB-aha
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 51

Accepted Solution

by:
Mark Wills earned 250 total points
ID: 38846065
Sounds a bit like the remnants of a previous connection has become hard coded.

What language are you using and we can add those Topic Areas to your question and get some developer help.
0
 
LVL 25

Assisted Solution

by:TempDBA
TempDBA earned 250 total points
ID: 38847515
Check the code what you are using for writing into the table, but not the connection string. I think in the insert statement, you have older database name hardcoded. Or if you are trying to insert via a view\stored procedure which inturn is pointing to the old database.
0
 
LVL 1

Assisted Solution

by:DB-aha
DB-aha earned 0 total points
ID: 38852644
Thanks for the advice, however I had no access to the application to be able to review it myself, I simply had only access to the database. What was required on my end was to open SQL Profiler and view the queries sent by the application. When doing so I was able to identify that the insert statement contained what appeared to be hard coded database. The application developer then looked at the queries and changed the database name in the application into a variable.
0
 
LVL 1

Author Closing Comment

by:DB-aha
ID: 38870834
My comment contains what was actually done to troubleshoot. While the other comments provided did not provide ant SQL Troubleshooting techniques.
0

Featured Post

Three Reasons Why Backup is Strategic

Backup is strategic to your business because your data is strategic to your business. Without backup, your business will fail. This white paper explains why it is vital for you to design and immediately execute a backup strategy to protect 100 percent of your data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

There have been several questions about Large Transaction Log Files in SQL Server 2008, and how to get rid of them when disk space has become critical. This article will explain how to disable full recovery and implement simple recovery that carries…
Occasionally there is a need to clean table columns, especially if you have inherited legacy data. There are obviously many ways to accomplish that, including elaborate UPDATE queries with anywhere from one to numerous REPLACE functions (even within…
In a recent question (https://www.experts-exchange.com/questions/29004105/Run-AutoHotkey-script-directly-from-Notepad.html) here at Experts Exchange, a member asked how to run an AutoHotkey script (.AHK) directly from Notepad++ (aka NPP). This video…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question