Object Doesn't Exist Or You Lack Permissions In SQL Server (Naming)
Check out the solution in the video Cannot find the object sp_Name because it does not exist or you do not have permission (naming). While this error should rarely appear, it serves as a reminder to avoid using built-in Microsoft naming convention for your objects. It's not that it won't work, it's that you may see bugs in your code (like this case).
Some quick notes that you'll want to keep in mind:
- Consider the platform that's being discussed
- If you see this issue, it may take some time to resolve because it's counter-intuitive
- Avoid overanalysis of naming, but be consistent
For mastering data transformation from one form to another form, check out the highest-rated Automating ETL course on Udemy. For a coupon to the course, check out the trailer video on the channel SQL In Six Minutes.
Naming convention gets people to argue because everyone feels like they have input. A mentor once shared with me that when people don't feel like they're an expert (or good) in an area, they love to argue about minutia because they can provide input on things that don't matter. As we see in this case, sometimes what appears to be minutia matters - sometimes, it doesn't.
One regular point I like to remind my audience, especially as of recent: we can often solve the same problem with a variety of techniques. While we look at one or two ways to solve the problem, these aren't the only ways we can approach this problem. The most appropriate solution to a problem is one in which you can troubleshoot quickly in the future and one in which you understand. Be careful about applying solutions that solve a problem, but introduce new problems in the future.
A great re-occuring example of this is my discussion on alerting best practices. There are a variety of alerts everywhere for everything in today's development environments, but many of these alerts cause more issues than they solve (one of which is creating a distraction). Be careful about "easy" solutions which introduce bigger problems. Know your environment and where to apply the best solution. Of course, all these being written, it is helpful to learn new techniques to solve problems because they may be useful in the future.
SQL In Six Minutes | Automating ETL | T-SQL In 2 Hours | Consumer Guide To Digital Security