Viewing 15 posts - 286 through 300 (of 1,335 total)
You need not need to do this if yopu have your client configuration referring to the particular port in the application server. I will create an alais of the server...
November 2, 2007 at 12:19 am
Other possible reason could be yur firewall blocking that port which sql listens.
November 2, 2007 at 12:18 am
Check for orphan users and resolve if any. Also you need to give execute permissions if they are not given.
November 2, 2007 at 12:16 am
Check if the below script helps.
/* Script by Sugesh */
/*posted @ sqlarticles.com */
set nocount on
Print 'Column Level Privileges to the User:'
select 'grant '+privilege_type+' on '+table_schema+'.'+table_name+' ('+column_name+') to ['+grantee+']'+case IS_GRANTABLE...
November 2, 2007 at 12:14 am
You need to cahnge either your sql server or windows server collation.
November 2, 2007 at 12:12 am
Yes you need to do a reindex of the table after a bulk insert.
November 2, 2007 at 12:08 am
Yes there is no way a table within sql server can have owner changed by itself there is a possibility that same table is reffered by 2 users.
November 2, 2007 at 12:03 am
cpuld you please post us the name of the extended procedure that is returning in the error message.
November 2, 2007 at 12:02 am
use the SET ISOLATION LEVEL TSQL to change the isolation level property to the one you desire.
November 1, 2007 at 11:52 pm
In the database in SQL 2000 check if there is a column which has a 'space' in it. the error looks there is such a column and is failing out...
November 1, 2007 at 11:51 pm
The best option is to do this in a non-production time. disable the replication do the reindexing.
November 1, 2007 at 11:49 pm
Possibly no. You need to reinstall the server with the right collation.
November 1, 2007 at 11:40 pm
Viewing 15 posts - 286 through 300 (of 1,335 total)