March 24, 2016 at 2:01 pm
mw112009 (3/24/2016)
Ed:I agree, But I do not know how to connect. I mean I know how to open SSMS and then connect to other servers, run sql statements.
In this case what would I use as the server name ? ( See attached pic )
I am not sure what the instance name would be ?
You could use "(local)" or a period "." without the double quotes. If you want to use the instance name, use the computer's name.
March 24, 2016 at 2:11 pm
Luis:
See attached.
I tried "local", "." and my Computer Name.
I think its a right issue. What am I missing here ? What should I tell the help desk folks to do ?
March 24, 2016 at 2:33 pm
mw112009 (3/24/2016)
Luis:See attached.
I tried "local", "." and my Computer Name.
I think its a right issue. What am I missing here ? What should I tell the help desk folks to do ?
You don't have a connection problem. You have an Authentication problem.
Your account has no rights to access SQL Server.
I'm not sure if being a local Admin would override the security.
March 24, 2016 at 2:48 pm
My understanding is some Administrator has to give me the rights ? Correct ?
Who can that be ?
So you are saying I do have SQL sever locally installed and out of the 3 pics I sent what would be the correct server name ?
March 24, 2016 at 5:16 pm
If you have SQL Server installed on a server, then the DBA has to give you permission to it. They'll also probably have to be the one to created the AdventureWorks database for you.
If you have it installed on your local machine, it probably isn't being administered by your DBA. It was likely installed either by you or the person who had your workstation before you. The person who installed it would know how to connect to the instance. If your DBA or network team don't know anything about it and you don't have anyone else who can help you with it, then you're probably going to end up uninstalling it and doing a fresh installation.
If I could offer a piece of advice, it sounds like you're just learning SQL Server, so have someone help you with the installation. Your DBA who's done it before would be the first choice, but anyone who has experience doing it would be beneficial.
March 25, 2016 at 4:22 am
At this point, you might be better served by uninstalling and reinstalling SQL Server. Go slow. Understand each step, especially when you get to the naming of the instances and security. Be sure you understand the choices at these steps. Coming out the other end, you should be all set.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 25, 2016 at 5:39 am
When I joined here SQL server , SSMS was already installed.
I don't get any rights to install anything on my PC.
Unfortunately, the HelpDesk staff is not that helpful (
Honestly they installed it but had no idea whether SQLSever
could be installed locally ).
I asked the same questions from them but did not get a
satisfactory answer. So here I am asking you and trying to
fix the pieces.
I am not a DBA.
Question: Do I have to be an administrator in my local machine
to overcome those messages ( The images I had attached previously
that show login failures )
March 25, 2016 at 5:46 am
When SQL is installed, it generally asks for the accounts of the local sysadmin. If SQL was installed on the machine before you got it, then it is likely no one added your account to the sysadmin for the system. You have a few options:
1) Do as Grant suggested and install a new version of SQL on your machine, making sure your account is added for sysadmin. This means you'll only be administrator for your local instance (not any others unless someone grants you that permission later). But it'll be enough to run Adventure Works.
2) Ask your help desk to identify the sysadmin on the instance installed so you can contact that person(s) and ask your login to be added to the permissions. Depending on what server-level permissions they give you, you may not be able to add Adventure Works to the instance.
3) Find your local DBA team on your own and talk to them about how to get the issue fixed.
March 25, 2016 at 6:18 am
I think it's likely that you're going to need some admin privileges to get things worked out. You won't need them permanently, but I don't think you have enough currently to either fix the problematic installation or do a new install.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 22, 2016 at 7:07 am
The person sitting next to me has access to his local machine.
I think the issue is because I have the STANDARD edition.
The person next to me updated his to the DEVELOPER edition and I asked him to try and connect to his local instance ( he used his PC name as the server name ) and was able to connect.
I will try upgrading to the DEVELOPER edition and let you know how it goes...
April 22, 2016 at 10:18 am
mw112009 (4/22/2016)
The person sitting next to me has access to his local machine.I think the issue is because I have the STANDARD edition.
The person next to me updated his to the DEVELOPER edition and I asked him to try and connect to his local instance ( he used his PC name as the server name ) and was able to connect.
I will try upgrading to the DEVELOPER edition and let you know how it goes...
Hopefully that will do it.
April 22, 2016 at 11:55 am
Yep It did that !
See attached,
The instance that has the name starting with WSJ.. is my local PC name. However I also tried Connect ( from menu ) and then typed a period and it connected to anoyther database. So I am not sure what exactly is going on then
I thought it would only allow me to have one local instance.
Anyhow.. That's another thread
Thanks, issue resolved, so the answer is the STANDARD EDITION did not allow but the developer edition does allow you to have a local instance.
April 22, 2016 at 12:13 pm
Good to know! Glad you got it working too.
April 22, 2016 at 1:09 pm
mw112009 (4/22/2016)
Yep It did that !See attached,
The instance that has the name starting with WSJ.. is my local PC name. However I also tried Connect ( from menu ) and then typed a period and it connected to anoyther database. So I am not sure what exactly is going on then
I thought it would only allow me to have one local instance.
Anyhow.. That's another thread
You might want to check that, they might be the same instance (your local machine) but with a different connection.
April 22, 2016 at 1:31 pm
How would I check that ?
Create a table in one instance and then if both of them are the same the table should appear in both instances right ?
I checked that , YEP, they are the same.. Thanks for pointing out ( See attached )
I just created a Db by the name of KAT and it appeared in both.
Viewing 15 posts - 16 through 29 (of 29 total)
You must be logged in to reply to this topic. Login to reply