What are the challenges you face when working across database platforms? Take the survey

Force candidate list to use schema instead of database?

tkdennistkdennis Posts: 114
edited December 1, 2008 7:16AM in SQL Prompt Previous Versions
I've got a schema in database A that is the same name as a different database. Both databases are in the cache, I have query windows open in each, I use cross-database references so Cross-database support is checked on. When I am in database A and type the schema name or pick it from the candidate list, then type . and get the candidate list again, it always shows the schema list for the database but never the table list for the schema. I've changing the Filters ("Filter candidate list by owner/schema prefix", "Enable case-sensitive filtering of candidates"), starting to type the table name, but nothing will change the cadidate list to include the tables in the schema. Is there anyway to force it to use the schema within the database besides turning off cross-database support?


SQL Prompt, SSMS 2008, SQL 2005 database

To reproduce:
USE some_other_database_besides_northwind


CREATE TABLE northwind.table1 (col1 int)

-- refresh cache here

select *
from northwind.


  • Options
    Hi Traci,

    Unfortunately you have run into a bug with SQL Prompt.

    I have recreated this my end and unfortunately the only way to get this working correctly is to disable cross-database support.

    I have added this to our bug tracking system.

    Thank you for pointing this out to us.
    Matthew Flatt
    Redgate Foundry
Sign In or Register to comment.