2012-10-04：
SQL Server 2008 Management Studio has intellisense, and it is very helpful, but it is case-sensitive.
For example, I have 3 tables:
Gy_Customer_Email
Gy_Customer_Para
gy_customertemp
Here's how intellisense behaves:
select * from gy_customer -- My input
gy_customertemp -- Intellisense suggestion
select * from Gy_Customer -- My input
Gy_Customer_Email -- Intellisense suggestion
Gy_Customer_Para -- Intellisense suggestion
I want to Intellisense to display all 3 options, regardless of case. How can I do that?
2012-10-08：
Thanks for Ashley Ross!
I had installed Service Pack 1 for SQL Server Management Studio according to your reference point, but the issue is still not resolved.
What should I do next?
My SQL Server Management Studio's option:
My SQL Server Management Studio's version
This issue has been reported at least two times on Microsoft Connect:
http://connect.microsoft.com/SQLServer/feedback/details/672196/t-sql-is-not-case-sensitive-but-t-sql-intellisense-is
http://connect.microsoft.com/SQLServer/feedback/details/402225/ssms-intellisense-make-text-matching-case-insensitive
Both issues are closed, and the problem has apparently been fixed in SQL Server 2008 R2 SP1 and in SQL Server 2012.
You should be able to install the updated SQL Server Management Studio on your development PC to resolve the problem you're having, without having to upgrade your database server.
Related
I have used the wizard from http://sqlazuremw.codeplex.com/ to move my database from:
Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64)
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM)
to
Microsoft SQL Azure (RTM) - 11.0.9164.122
Which worked great, but there was a table with over a gigabyte of rubbish data. So I stopped the process. Now it copied a table structure, but forgot to fill the content. I will have to fix this manually with query:
-- when connected to the azure db
select into azureDb.dbo.tablename select * onPremisesServer.onPremisesDb.dbo.tablename
But when I execute it, I get:
Msg 40515, Level 15, State 1, Line 16
Reference to database and/or server name in 'onPremisesServer.onPremisesDb.dbo.tablename' is not supported in this version of SQL Server.
I have found Cannot get Linked Servers to work in Sql Azure and it says that it is client related. So I looked up my version of SSMS:
Microsoft SQL Server Management Studio 11.0.3128.0
So that cannot cause this. I have also had troubles with the 'onPremisesServer' being just an ip address and had to execute select name from sys.servers to find a server alias instead of using [ipadres] for onPremisesServer. Still cannot get it to work. The tables have exactly the same schema.
edit as DeicLone123 mentioned, I used import and export data. I have renamed the table to tablename-old on azure and ran the wizard and got:
I used the 3.x again from http://sqlazuremw.codeplex.com/ to migrate just that last table. Easy as that! Manually transferring the data, column types etc. is a real pain.. So this open source migration tool is really recommended!
I would like to use the Visual Studio 2012 LINQ to SQL Classes feature. I installed the MySQL Connector/Net version 6.6.4. In VS I was able to add a connection to the MySQL database. I then added a new item, "Linq to SQL Classes". It opened the workspace. I dragged the MySQL table to the workspace and received the following error: "The selected object(s) use an unsupported data provider". In my connection it states that the following provider is being used, ".NET Framework Data Provider for MySQL.
I use the same procedure with MSSQL and it works perfect every time.
It is correct that the Oracle/MySQL Connector/Net version 6.6.4 (which is the latest) does not support VS 2012 LINQ to SQL Classes? Note that I don't want to use LINQ to Entity.
Thanks! Todd
Microsoft does not provide "Linq to SQL" for non-Microsoft RDBMS. But others do. Check out
devart (Ukraine) and Mindspeed (New Zealand).
Neither is free, but both have free versions for up to 8 or 10 entity types (not 8 tables!) respectively.
I am trying to open DTS packages in SQL Server 2008 R2. But I'm getting this following error
sql server 2000 DTS Designer components are required to editDTS
Packages.install the special web download, " sql serevr 200 DTS
Designer Components" to use this feature
.(microsoft.sqlserver.dtsobjectexplorerUI)
Anybody help how to make it work?
As I already installed the SQLServer2005_BC.msi & SQLServer2005_DTS.msi
Your question subject says SQL Server 2008, the error message says SQL Server 2000, and you installed SQL Server 2005's MSI. You have three different versions of SQL Server in the three items.
You're trying to install something that either isn't the right version for the SQL Server version you're using (2008), or is no longer available or required for SQL Server 2008. You need to find the proper means of editing DTS files for SQL Server 2008, or research what replaced them in SQL Server 2008.
I was trying to use TRY..CATCH feature in SQL Server 2005's Stored Procedure but it didn't worked. I checked my version using ##VERSION, it displayed "MS SQL Server 2000 - 8.00.194 (Intel X86) " but when I clicked on Help->About, it displayed "9.00.1399.00" which clearly specifies that I have SQL Server 2005 installed.
I know that TRY..CATCH can only be used on SQL server 2005 or above..
My system might be using Sql Server 2000 as source database or something like that, I might be wrong in describing. How to change it then..
After re-reading your question, you clearly have SQL Server 2005 client tools (SSMS) installed, and have your database on a SQL Server 2000 server, so you cannot use TRY..CATCH. Period.
Assuming you really do have a SQL Server 2005 server, have you ensured the specific database has its compatibility level set to 90 (SQL Server 2005)?
Right click database->Properties->Compatibility level
This can happen if you upgrade the server and forget to upgrade the database compatibility level.
help..about gives you the version of the client tools (SSMS)
SELECT ##VERSION gives you server version
If the server version is 8.x then you have SQL Server 2000 which does not support TRY/CATCH. No amount of fiddling with Compatibility level will fix this.
You have 3 practical options
Don't use TRY/CATCH
Upgrade your server version
Install a names SQL Server 2005 instance on the same box
I have an old version of Microsoft Content Management System (MCMS-2002). I have a request to update our database server from sql2005 to sql2008. I can migrate the cms database just fine from 2005 to 2008, and I can set the compatibility mode to 2005.
However, when I use the Database Configuration Application (from MCMS) to point at the sql2008 server I get the following error:
Unable to use selected SQL Server. The
server must be SQL Server 2000 Service
Pack 2 or better.
I find it ironic, but frustrating, that it doesn't recognize the newer version of sql server. I have found some indications that MCMS queries the database for its version number but only accepts a single digit version number.
So SQL2000 -> version 8
SQL2005 -> version 9
SQL2008 -> version 10 : but MCMS only gets Version 1 and thinks it is a VERY old version.
Has anyone else experienced this issue and found a solution?
This problem is similar to the MCMS' J# version problem where setup is asking for version 3.0 which does not even exist.
I hope somebody does find a workaround as we are about the face the same problem soon.