SQL Server 2008R2 Cannot query linked Server - sql-server

I added a linked server by using SQL Server Management Studio and NT authentification (sa)
I can connect to the server and see databases but I cannot query anymore
The option to data access is set to True
So I don't know what's wrong
EDIT: This morning, after trying again i could execute a query!
So, i can't find why but it's work! \o/

i'm not sure i get the issue because you write 'i cannot query anymore' as if you ever succeeded but if you expect to be able to right click on an object (table or view) accessible through a linked server and get the usual SELECT TOP X or Edit top X menu then you're out of luck: this is a feature that is not available on objects accessed through a linked server.
i just made a test on sql server version 2005, 2008 and 2012 using SSMS 2012 and 2005 and that right click menu is not available when on linked server.

Related

unable to view table design in microsoft sql server management studio

I have microsoft sql server management studio installed for existing databases and I can connect and write queries without a problem. However I experience problems when right clicking on the table to open the design view. I get the following error, has anyone seen this before?
If I click okay on this error message the right click context menu displays, i.e. displaying options for new table, design view, select top 1000 rows, edit top 20 rows etc.. and then I get the following error message (see image 3).
Any help greatly appreciated.
Error message
Version of SQL
If I click design view in the right click context menu
Thanks,
It means your Management Studio's version is not >= the version of SQL Server.
If you, for example, use Management Studio 2008 R2 to connect to SQL Server 2014, you'll get this message.
You'll need to install the latest version of SSMS.
If both versions show 2008, it's still possible you have a different version, because there is SQL Server 2008 and SQL Server 2008 R2.

How to view a list of databases under server in SQL Anywhere like we do in MSSQL

I am very new to SQL Anywhere. I have been working MSSQL for a long time.
So in MSSQL, if we need to see the list of database under server, we can see that under Server Explorer.
How can I do same in SQL Anywhere?
I have just installed SQL Anywhere 16 and have no idea how to find Server name etc.
There should be a program called "SQL Central" (scjview.exe) that was installed with SQLAnywhere server. Run that and you should be able to see the servers.

How do I create an SQL Server?

I have a very fundamental and basic SQL question. Using Microsoft SQL Server Management Studio Express, how do I create my first Server? For that matter, how would I create it using any other required software tool?
I took a look at Sql Server Configuration Manager and I saw SQLEPRESS running as a SQL Server. But when I added that in to the start up widow for MSSM Studio Express, as the server name, it threw an error saying it cannot be found or does not exist. It seems that this is not the right kind of server.
To connect to the local instance of SQLEXPRESS, you will need localhost as the server name.
This is a fairly comprehensive guide on how to create a database once you have connected. All the steps won't apply to using SQL Express, but the gist of it is there.
In Object Explorer, connect to an instance of the SQL Server Database
Engine and then expand that instance.
Right-click Databases, and then
click New Database. In New Database, enter a database name.
To create
the database by accepting all default values, click OK; otherwise,
continue with the following optional steps.
Based on this comment:
Trying .\SQLEXPRESS in SQL Server Management Studio Express throws an error that says that "This version of Microsoft SQL Server Management Studio Express can only be used to connect to SQL Server 2005 servers". So this is the problem, I think.
.\SQLEXPRESS is the correct server name, but you have the wrong version of client tools (SQL Server Management Studio). To find out the version of SQL you are connecting to, there are a number of suggestions here: https://www.mssqltips.com/sqlservertip/1140/how-to-tell-what-sql-server-version-you-are-running/
But since you can't connect yet the easiest thing to do is go searching for sqlserver.exe, right click, properties, version. If you have multiple version you need take note of the folder that it's in and check the SQLExpress one. You can also check in services.
Once you've worked out the version, download and install just the management tools for that version.

MS SQL Server (2008 R2) Error 18452 with Access 2010

I am working on an Access accdb project and I have all my tables linked to MS SQL Server 2008 R2 via ODBC.
I have one screen with a sub form that always gives me this error message when I enter it:
I've done some research and it it supposed to be related to the server's authentication method, but if all my tables are linked the same way, why does it happen?
What's even more weird is that if I refresh my table's connections via the linked table manager, everything works fine for some time, and then I get the same error again. I look through my code to see if I play with any connection string, but I don't.
Any thought/ideas? Any (educated) guess you have will be appreciated :)
Thanks,
Yotam
Go to Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio
Right-click the Server name, select Properties > Security
Under Server Authentication, select SQL Server and Windows Authentication Mode.
The server must be stopped and re-started before this will take effect.

sql 2000 + vs 2008, debugging through sproc?

Hey all. Is it possible to step through a sproc on sql server 2000 server using vs 2008?
When I go through the server explorer and choose to step into the sproc, it asks me to enter the param values and then it gives me the output of the sproc, without stepping into it.
Your steps sound correct for SQL Server 2005/2008. Having said that, I know for SQL Server 2000, it's possible to enumerate the sprocs via Query Analyzer, right click, and then debug from there. Not sure if that's acceptable or not in your current environment, but that should do the trick if using server explorer doesn't pan out.
(Note that this is all from memory, since I don't have SQL Server 2000 installed on my dev box anymore.)

Resources