Is there a query that you can run in SQL that will tell you which database (if any) has a bad path to its data

Question

My backup software keeps telling me that I have a bad path to one of the databases on one of my servers, but I can't see it when I check it manually. I'm sure that I am just missing it, but I have no idea how to tell where it is. Is there a stored procedure or query that I can run that can tell me if there is a bad path and where it is?

Turns out that there was an extra "/" in the path of one of my sql databases. Although this does not effect MS SQL, it effects Symantec backup exec. I ended up having to go through the properties of every database on the server to find it.

Very annoying...

Answer 1

No, because the two things aren't related.

You haven't said what RDBMS you are using, but the physical path to where one of your actual database files is located should be available from your DB's management console or similar setup program.

Your backup program is claiming that it can't find a DB file where it should be, so it makes sense that if you look at the place it says the file isn't, the file won't be there.

You probably need to rebuild your backup set, more than hunt down what that program considers a "missing" DB file.

Answer 2

First verify to work out which you have indexes you may hit and then hint them interior the sq. statements. confirm you you're committing the place a danger and keeping off locks between scripts/sp's. whilst turning out to be a member of tables, clear out rows the place you may so it is utilising much less information. Cursors are sluggish, discover and replace the place you may. some human beings can not think of the thank you to jot down for blocks of code so as that they use cursors to step by whilst no longer mandatory. make beneficial the database is tuned for the code you're working too. yet it is an entire 'nother question ;-)