Dear Community,<o:p></o:p>
I'm doing a 12 month internship to learn T-SQL and I've been having so much drama with SSMS. Part of my internship is to learn T-sql but on my work laptop, the ssms (Paid for edition) is quite restricted, I:e only SELECT statements. This conflicts a lot with my books and tutorials, as I want to learn the learn the basic principals hands on i:e DELETE, INSERT add a database etc... So I decided to add another instance of sql server with full access so I could play with and install Adventure works and just simply go crazy....<o:p></o:p>
The Setup:<o:p></o:p>
Okay I have a paid for SQL Server 2008 R2 already installed and the network server is somewhere on this globe (Be great if someone could tell me how to find the name of it?) and also at work we have our own Domain Server, which I can connect to via VPN at home. (Before anyone says this again, yes I know I can install express on a different machine but part of my internship is learning this there's no way I'm carrying two laptops, have you commuted through London? Wearing a swim suit could make you too big to get on a tube.) When I connect to the work database my server name is prefixed with an I:P address from the looks, not sure if that's a clue but also this instance is also the default setting.<o:p></o:p>
The Deal:<o:p></o:p>
Okay downloaded sequel server again, by default already, but to double check, it was a 'Named Instance' such as SQLexpress1 and I gave it 'Windows Authentication' (Which means me logging into the computer gives me access right?). I created a bunch of local users (Guided From tutorials but there was mention about not being in a DOMAIN) as I'm hoping to turn my machine into the local server as I don't want this instance connecting to any network. I just want to have the database saved on my laptop and open it up in ssms and start going Chuck Norris with code.<o:p></o:p>
The Problem:<o:p></o:p>
It works! but not for long :( I open up ssms log in using the server name like "UKLONN10532\SQLEXPRESS2" and I have windows authentication set, all great (btw UKLONN10532 is my machine name I think). I can attach a sample database all good but when I log out and go home and access my database I get this error, image down below. Even when I log into VPN and in my own domain is doesn't work, and even if I go back into work it still doesn't work, it seems broken permanently. I've done this 4 times, every time I can create an instance log in and out when at work but when I access at home nothing (Btw I attempted this at home with all internet off and it worked at home and at work for two days then suddenly stopped giving me access but I might have been hibernating my machine not sure) so it seems, however I install it if I cross over from work to home and vice versa once installed problems arise. <o:p></o:p>
The Hunch:<o:p></o:p>
1) I think, that the sql server instance is another instance from my work server, hence all the BS about establishing an connection when my database adventure works is in my C:Drive. 2) like 1 but something to do with my work domain? 3) Administrative rights maybe? I'm sure I have full access to this laptop but my default sql server does have limited access hhmmm... <o:p></o:p>
Even if I can't fix this how do I install another SQL server and have it connect to a sample database saved in my C:Drive without ssms settings interacting with my other database on a network server.<o:p></o:p>
Many Thanks,
Jake