title: Best Practices on naming Views
body: <p>I have for example a table name of Cars_Import</p>
  
  <p>I need a view that will be called that grabs the data to be imported and that view is run and does the work to import the data into the Cars_Import table.</p>
  
  <p>My problem is, I can't name the view the same, I have to differentiate it because I guess SQL server look at same name objects as a conflict no matter what type of object it is.</p>
  
  <p>So for best practices in naming conventions that are generally accepted, when you have 2 objects that really relate to each other, and I know it's not good practice to append stuff like tbl, vw for view, etc. in the name, what would you suggest here as the view name related to Cars_Import?</p>
  
  <p>I wouldn't want the view to have it for example switched around which would work but just seems messy to me such as Import_Cars</p>
  
  <p>So what's the advice here on naming the table and its related view which will grab all data from that table that we need?  There is no business logic, it's just grabbing the data and we're gonna import it into a data warehouse, all the data as is initially.</p>