machine and Management Studio or Enterprise Manager is not present. Do
i need to perform extra task or did i do sth wrong when installing this.
Thanks for your attention.
It's more likely that you did not install the client components
When you setup program, at one stage wou have choice to check the components you want to install
Client components are grouped under the name orf workstation or something similar (Sorry I don't remeber the exact name))
Most likely, the client tools were not installed. I don't think that they are installed in a default installation on a Server OS.
Put in your installation media, and select client tools.
We have set up Mirroring with a witness server and everything works fine when we failover from the SQL Management console.
However, if we failover when our Maccola client is connected, the client blows up - clearly because it can no longer connect to the database.
The ODBC DSN used by the Maccola client shows a checkbox for the 'select a failover server' but the checkbox is grayed out.
Also the summary of settings for the DSN at the end of the wizard reveals that the failover to server (y/N) option is set to N.
The default setting for this DSN is 'populate the remaining values by querying the server' but it doesn't appear to be getting the settings for failover from the server or any other interactive DSN settings either. The server is clearly set for mirroring.
Another suspicious item is that the DSN cannot connect to the server with SA permissions, even though the server is set to mixed security and we use the correct authentication.
Is it possible that the client MACHINE is not authenticating with the domain or sql server properly. We are logged into the client with the domain account that is the SQL admin account on the sql server box.
We should be able to interact with the sql server settings through the ODBC DSN on the client shoulnd't we?
Are we missing a service pack on the client?
Thanks,
Kimball
Have you referred to Maccola vendor in this case about the compatibility, I would guess this is to with that drivers.We have set up Mirroring with a witness server and everything works fine when we failover from the SQL Management console.
However, if we failover when our Maccola client is connected, the client blows up - clearly because it can no longer connect to the database.
The ODBC DSN used by the Maccola client shows a checkbox for the 'select a failover server' but the checkbox is grayed out.
Also the summary of settings for the DSN at the end of the wizard reveals that the failover to server (y/N) option is set to N.
The default setting for this DSN is 'populate the remaining values by querying the server' but it doesn't appear to be getting the settings for failover from the server or any other interactive DSN settings either. The server is clearly set for mirroring.
Another suspicious item is that the DSN cannot connect to the server with SA permissions, even though the server is set to mixed security and we use the correct authentication.
Is it possible that the client MACHINE is not authenticating with the domain or sql server properly. We are logged into the client with the domain account that is the SQL admin account on the sql server box.
We should be able to interact with the sql server settings through the ODBC DSN on the client shoulnd't we?
Are we missing a service pack on the client?
Thanks,
Kimball
Have you referred to Maccola vendor in this case about the compatibility, I would guess this is to with that drivers.I'm trying to modify my default value for GUIDs in DB, currently using newid() for default.
In management studio, click on modify and in the table designer for the default value I entered newsequentialid() and got the following error.
Error validating the default for column "xxxx".
I would like to have my tables that are using guids, have newsequentialid as the default value. When read on this new function it says can only be used with default value, but can't get that to work. Any ideas?
thanks
This is a bug in Management Studio. There are two workarounds
1. Create the table by hand in T-SQL.
2. Use newid, then generate a script, and replace the newid with newsequential.
You can file a bug at http://lab.msdn.microsoft.com/productfeedback/
|||I can set the default value OK in management studio if it is a brand new table. I'm trying to upgrade my tables in my DB to have the default to be newsequentialId(). Is there a problem if there is already data in the tables with now changing from newid() to newsequentialid()|||Why on earth is this not fixed yet AND there doesn't seem to be any official Microsoft posting or commment regarding this?
Seriously annoying bug.
|||If we cannot answer a question in the forums in the first month, it generally gets ignored and we do not go back and try to answer it later. Whenever there is a problem with our product, I strongly recommend filing a bug or a suggestion in Microsoft Connect.
SQL Server's portal on Microsoft Connect: http://connect.microsoft.com/SQLServer/
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
I'm trying to modify my default value for GUIDs in DB, currently using newid() for default.
In management studio, click on modify and in the table designer for the default value I entered newsequentialid() and got the following error.
Error validating the default for column "xxxx".
I would like to have my tables that are using guids, have newsequentialid as the default value. When read on this new function it says can only be used with default value, but can't get that to work. Any ideas?
thanks
This is a bug in Management Studio. There are two workarounds
1. Create the table by hand in T-SQL.
2. Use newid, then generate a script, and replace the newid with newsequential.
You can file a bug at http://lab.msdn.microsoft.com/productfeedback/
|||I can set the default value OK in management studio if it is a brand new table. I'm trying to upgrade my tables in my DB to have the default to be newsequentialId(). Is there a problem if there is already data in the tables with now changing from newid() to newsequentialid()|||Why on earth is this not fixed yet AND there doesn't seem to be any official Microsoft posting or commment regarding this?
Seriously annoying bug.
|||If we cannot answer a question in the forums in the first month, it generally gets ignored and we do not go back and try to answer it later. Whenever there is a problem with our product, I strongly recommend filing a bug or a suggestion in Microsoft Connect.
SQL Server's portal on Microsoft Connect: http://connect.microsoft.com/SQLServer/
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
I'm trying to modify my default value for GUIDs in DB, currently using newid() for default.
In management studio, click on modify and in the table designer for the default value I entered newsequentialid() and got the following error.
Error validating the default for column "xxxx".
I would like to have my tables that are using guids, have newsequentialid as the default value. When read on this new function it says can only be used with default value, but can't get that to work. Any ideas?
thanks
This is a bug in Management Studio. There are two workarounds
1. Create the table by hand in T-SQL.
2. Use newid, then generate a script, and replace the newid with newsequential.
You can file a bug at http://lab.msdn.microsoft.com/productfeedback/
|||I can set the default value OK in management studio if it is a brand new table. I'm trying to upgrade my tables in my DB to have the default to be newsequentialId(). Is there a problem if there is already data in the tables with now changing from newid() to newsequentialid()|||Why on earth is this not fixed yet AND there doesn't seem to be any official Microsoft posting or commment regarding this?
Seriously annoying bug.
|||If we cannot answer a question in the forums in the first month, it generally gets ignored and we do not go back and try to answer it later. Whenever there is a problem with our product, I strongly recommend filing a bug or a suggestion in Microsoft Connect.
SQL Server's portal on Microsoft Connect: http://connect.microsoft.com/SQLServer/
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
We're currently converting the database of our asset management system to a SQL2005-database. The SQL2000 database uses an INT32 as the primary key with a clustered index on that column on most tables. Needless to say that the current environment is not ideal for replication, so we're investigating the use of GUIDs as primary keys.
We know the usual recommendations as far as GUIDs are concerned (4 times bigger, slower, not good for clustered indexes, yet better for replication). However, on one of the ascend-program training days one of my colleagues talked to one of the instructors and that person suggested that the use and performance of GUIDs is significantely improved in SQL2005 and that they have become the preferred datatype for primary keys if the database is used in replication.
I have tried to find some information about how GUIDs are improved in SQL2005 but I don't find any documents containing anything relevant. The only thing I've found is the documentation of the NEWSEQUENTIALID function which doesn't really tell me much. It just looks like this function improves the performance during an insert if a GUID is used on a clustered index. I have noticed for example that SharePoint only uses GUIDs for most tables; so the performance should be all that bad.
So I was wondering:
1. has the performance of GUIDs improved?
2. are there new suggestions concerning the datatype of the primary key column if the database might be used in a merge replication environment (all sites can do modifications) on SQL2005?
3. what about the performance of NEWSEQUENTIALID? Is there a bigger chance of running into duplicates using NEWSEQUENTIALID?
Regards,
Michael
NEWSEQUENTIALID is derived based on several hashes, one of which is the network card. Since no two network cards are identical, duplicates should not occur. However should you remove your network card, there's a slight chance you can get the same value as another machine whose network card has been removed, but this is highly unlikely.
Since NEWSEQUENTIALID values are incrementing as they're created, clustered index performance should improve as they'll be inserted ascending and in sort order. You also have less page splits, thus less fragmentation.
So, is NEWSEQUENTIALID a good candidate for a primary key? NEWSEQUENTIALID can only be used as a default constraint. that means if this is your primary key, and you have to update it, you can only use NEWID as the new value. Or, you can do delete/insert. If you do a lot of updates to your primary key, you'll be doing a lot of page splits introducing fragmentation.
|||How does the program get the NEWSEQUENTIALID value? In other words, the code has:For a parent child relationship, you can do this:
CREATE TABLE Employee(
EmployeeID uniqueidentifier NOT NULL DEFAULT NEWSEQUENTIALID(),
EmployeeName nchar(10) NOT NULL
)
insert Employee (EmployeeName)
output Inserted.EmployeeID
values ('Ima Person')
The OUTPUT clause essentially works like a SELECT statement. You can retrieve multiple values with an OUTPUT clause.
Alternatively, you may wish to use this syntax for CREATE TABLE:
CREATE TABLE Employee(
EmployeeID uniqueidentifier NOT NULL DEFAULT NEWSEQUENTIALID() ROWGUIDCOL,
EmployeeName nchar(10) NOT NULL
)
