Using SQL Server 2005 and Microsoft SQL Server Management Studio, I connect using windows authentication. On any database I have created or attached (from a previous version of SQL Server), if I try to add a new table or modify an existing table, I get an error. A dialog pops up that says, "The parameter is incorrect." And I realy can't go any further.
I tried to remedy the problem by applying SP1 (x64) to the installation but I still get the same error.
Has anybody got a clue as to why I get this error? This is not SQL Server Express but the standard version of SQL Server. Fabulous software, I just can't get this to work on this new server. SQL Server Express is wonderful on our test machines but we need to get past this issue to fully utilize the server version.
Thanks for any help somebody can give me.
Please file a defect report on http://connect.microsoft.com/sqlserver. Defects reported on the Connect site go directly into our internal issue tracking system.
The error message pop-up should have a button/icon at bottom to show technical details. This includes the detailed exception message and the call stack. This can help us diagnose the problem. Be sure to include the version number of management studio and the engine (use menu Help | About to see the management studio version, and use this T-SQL to get the engine version: select @.@.version) and the call stack from the error dialog in the defect report.
One thing I would check is whether the database you've attached has a valid owner in the new server. If the database doesn't have an owner, you can give it one using the database properties dialog in management studio (connect to the server, right click on the database in Object Explorer, and select Properties. The owner can be set on the Files page.) or by issuing the "ALTER AUTHORIZATION ON DATABASE::{your db} TO {server principal}" statement in sqlcmd or a management studio query window.
You also need fairly high privileges to modify tables. Can you modify tables if you log in as a database owner?
Thanks,
Steve
No comments:
Post a Comment