– UNIQUE CONSTRAINT
ALTER TABLE DROP CONSTRAINT

– UNIQUE INDEX
DROP INDEX ON

TITLE: Connect to Server
——————————

Cannot connect to pran-pun-srv-trup.

——————————
ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

go

CREATE VIEW dbo.MadhoIDAccNo WITH SCHEMABINDING AS
SELECT ID, AccNo, COUNT_BIG(*) c
FROM dbo.Madhu
GROUP BY ID, AccNo;

go

CREATE UNIQUE CLUSTERED INDEX OnlyOneAccNoPerID ON dbo.MadhoIDAccNo(ID);

ID, Accno, Type
1 , 1 , 1
1 , 1, 2
1, 1, 3
1 , 2 , 1 it can not be allowed
2 , 1, 1 it can be allowed
how can i create this type of table?
ID cannot be used for any Other Account Number but it can be used multiple times for same Account Number??

Thanks in advance
Madhukumar N

http://social.msdn.microsoft.com/Forums/en/sqldocumentation/thread/fc8f2d2d-0378-4f5f-94bc-033b44842aa7

Having same Oracle –> SQL Server conversion problem. Its only to be maintained for historical reporting so your work around is perfect!
I tried ANSI_PADDING ON (at db level and at table create and insert time) but no luck and gave up.

“My work around is to replace trailing blanks in key fields with ~ character. Again a temporary fix till SQL Server provides a way to have sound string data type comparisons”

A container to hold 6 beers at the same time! BRILLIANT!!

THX
FC Wright

To retrieve “Unique Index”:
select name, type_desc, is_unique, is_primary_key
from sys.indexes
where object_id = object_id(‘MyTable’)

Igor

using System;
using System.Collections;
using System.Data;
using System.Data.OleDb;

namespace namespace_name {
public class class_name {
private string table_name = “tabela_teste”;
private string var_OleDbConnection = “Provider=sqloledb;Data Source=127.0.0.1;Initial Catalog=database_name;User Id=sa;Password=;”;
#region public indices_colunas[] indexes
private indexes_columns[] Indices;
public indexes_columns[] indexes {
get {
if (Indices == null) {
ArrayList ar = new ArrayList();
DataView dv = GetOleDbSchema(System.Data.OleDb.OleDbSchemaGuid.Indexes, new object[] {null, null, null});
for (int i = 0; i < dv.Count; i++) {
if (dv[i]["TABLE_NAME"].ToString().Trim().ToLower() == table_name.ToLower()) {
if (dv[i]["TABLE_NAME"].ToString().Trim().ToLower() == table_name.ToLower()) {
indexes_columns ind = new indexes_columns();
ind.table_name = dv[i]["TABLE_NAME"].ToString();
ind.column_name = dv[i]["COLUMN_NAME"].ToString();
ind.index_name = dv[i]["INDEX_NAME"].ToString();
ind.primary_key = Convert.ToBoolean(dv[i]["PRIMARY_KEY"]);
ind.clustered = Convert.ToBoolean(dv[i]["CLUSTERED"]);
ind.unique = Convert.ToBoolean(dv[i]["UNIQUE"]);
ar.Add(ind);
}
}
}
Indices = new indexes_columns[ar.Count];
ar.CopyTo((indexes_columns[]) Indices);
}
return Indices;
}
}
#endregion
#region public struct indexes_columns
public struct indexes_columns {
public string table_name;
public string column_name;
public bool clustered;
public bool unique;
public bool primary_key;
public string index_name;

}
#endregion
private DataView GetOleDbSchema(Guid SchemaGuid, object[] parametros) {
DataView dv = new DataView();
OleDbConnection myConnection = new OleDbConnection(var_OleDbConnection);
try {
myConnection.Open();
dv = new DataView(myConnection.GetOleDbSchemaTable(SchemaGuid, parametros));
}
catch {
throw;
}
finally {
myConnection.Close();
}
return dv;
}
}
}

thanks

Very interesting!

CREATE TABLE A(A INT UNIQUE);
INSERT INTO A(A) VALUES(1);
INSERT INTO A(A) VALUES(1);
DROP TABLE A;

CREATE TABLE A(A INT);
CREATE UNIQUE INDEX AA ON A(A);
INSERT INTO A(A) VALUES(1);
INSERT INTO A(A) VALUES(1);
DROP TABLE A;

SQL will raise an error with an error code of 2601 when violating a unique index, while it will use error code 2627 for violating a unique constraint.

Minor difference, but while they are very similar, they are NOT the same.