Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. SQL Server 2012 Express on Network - cannot see attached databases - can see Master, etc.

SQL Server 2012 Express on Network - cannot see attached databases - can see Master, etc.

Scheduled Pinned Locked Moved Database
sysadminsecurityworkspacedatabasesql-server
7 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    PrissySC
    wrote on last edited by
    #1

    I went through security and added. Checked the owners and added sa and admin account. I just can't seem to figure out what I have missed! DBs detached, copied, and moved from test server to actual network server seems to have not included a "setting" or "configuration". Any ideas? Using Windows Authentication. The odd is that I can connect and see the Master, but not the attached databases that were added. And yes, they were attached and brought online. The fact that I can see the master tells me that I have the router rules set correctly. I am open to any suggestions. Throw it at me. I have to have missed something obvious. FIXED! The problem exists in policy, whether group or user I did not explore further. Installed SQL Server as a local machine with local admin. I completely took the server offline for the initial setup. Reconnected using the suggested username/password as well. Not a problem at all.

    M J P 3 Replies Last reply
    0
    • P PrissySC

      I went through security and added. Checked the owners and added sa and admin account. I just can't seem to figure out what I have missed! DBs detached, copied, and moved from test server to actual network server seems to have not included a "setting" or "configuration". Any ideas? Using Windows Authentication. The odd is that I can connect and see the Master, but not the attached databases that were added. And yes, they were attached and brought online. The fact that I can see the master tells me that I have the router rules set correctly. I am open to any suggestions. Throw it at me. I have to have missed something obvious. FIXED! The problem exists in policy, whether group or user I did not explore further. Installed SQL Server as a local machine with local admin. I completely took the server offline for the initial setup. Reconnected using the suggested username/password as well. Not a problem at all.

      M Offline
      M Offline
      Mycroft Holmes
      wrote on last edited by
      #2

      What UI are you using to manage the databases?

      Never underestimate the power of human stupidity RAH

      P 1 Reply Last reply
      0
      • M Mycroft Holmes

        What UI are you using to manage the databases?

        Never underestimate the power of human stupidity RAH

        P Offline
        P Offline
        PrissySC
        wrote on last edited by
        #3

        Server Mgmt Studio

        1 Reply Last reply
        0
        • P PrissySC

          I went through security and added. Checked the owners and added sa and admin account. I just can't seem to figure out what I have missed! DBs detached, copied, and moved from test server to actual network server seems to have not included a "setting" or "configuration". Any ideas? Using Windows Authentication. The odd is that I can connect and see the Master, but not the attached databases that were added. And yes, they were attached and brought online. The fact that I can see the master tells me that I have the router rules set correctly. I am open to any suggestions. Throw it at me. I have to have missed something obvious. FIXED! The problem exists in policy, whether group or user I did not explore further. Installed SQL Server as a local machine with local admin. I completely took the server offline for the initial setup. Reconnected using the suggested username/password as well. Not a problem at all.

          J Offline
          J Offline
          jschell
          wrote on last edited by
          #4

          The following are the only possibilities. - The database has not been attached, - You are not connecting to the database server that you think you are. - The user permissions are wrong.

          PrissySC wrote:

          The fact that I can see the master tells me that I have the router rules set correctly

          If you couldn't route to the database server then you couldn't connect nor log in. It has nothing to do with whether you can see databases.

          P 1 Reply Last reply
          0
          • J jschell

            The following are the only possibilities. - The database has not been attached, - You are not connecting to the database server that you think you are. - The user permissions are wrong.

            PrissySC wrote:

            The fact that I can see the master tells me that I have the router rules set correctly

            If you couldn't route to the database server then you couldn't connect nor log in. It has nothing to do with whether you can see databases.

            P Offline
            P Offline
            PrissySC
            wrote on last edited by
            #5

            See, that is where I am puzzled! I specifically went in and gave public access as well as set the Owner to the account. So then, thinking aloud, I should look at the owner. Should I look at builtin\users or default admin account? I already set the NT. From there, I assume, properties, user mapping. Checked the DB in question and provided membership to owner and public. I will check the server roles and grant status for the user too. Hmmm .... at least you agree with me! Thanks, and if you think of something else, I will check back and keep this thread updated. :)

            M 1 Reply Last reply
            0
            • P PrissySC

              See, that is where I am puzzled! I specifically went in and gave public access as well as set the Owner to the account. So then, thinking aloud, I should look at the owner. Should I look at builtin\users or default admin account? I already set the NT. From there, I assume, properties, user mapping. Checked the DB in question and provided membership to owner and public. I will check the server roles and grant status for the user too. Hmmm .... at least you agree with me! Thanks, and if you think of something else, I will check back and keep this thread updated. :)

              M Offline
              M Offline
              Mycroft Holmes
              wrote on last edited by
              #6

              If you have restored/attached the database from a different server you may need to drop and reapply the user permissions, while the name is the same the id values are different. While I use windows authentication in SSMS I have all my apps have a SQL identity and uses that, so a connection string ALWAYS has a userid and password, never integrated.

              Never underestimate the power of human stupidity RAH

              1 Reply Last reply
              0
              • P PrissySC

                I went through security and added. Checked the owners and added sa and admin account. I just can't seem to figure out what I have missed! DBs detached, copied, and moved from test server to actual network server seems to have not included a "setting" or "configuration". Any ideas? Using Windows Authentication. The odd is that I can connect and see the Master, but not the attached databases that were added. And yes, they were attached and brought online. The fact that I can see the master tells me that I have the router rules set correctly. I am open to any suggestions. Throw it at me. I have to have missed something obvious. FIXED! The problem exists in policy, whether group or user I did not explore further. Installed SQL Server as a local machine with local admin. I completely took the server offline for the initial setup. Reconnected using the suggested username/password as well. Not a problem at all.

                P Offline
                P Offline
                PrissySC
                wrote on last edited by
                #7

                I would have agreed, but I created a new database on the SQL server. I went to a client machine to connect, and once again, the new database does not show in the list. I get the SQL list with master and such. Truly, this is really bothersome. It is almost as if there is a "scope" problem. Could the GPO affect this? It is an Admin of the domain, but what was given to me was that this admin account has full access. I would think to differ only because ... SQL installs with a local machine admin yes? Creator/Owner does have special permissions by default on 2008 ... would any portion of this effect the DATA folder where the database has been relocated for attachment? Lastly, I will try using nonintegrated methods and consider troubleshooting ID values as well per Mycroft Holmes' post.

                1 Reply Last reply
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • World
                • Users
                • Groups