Search results for query: *

yeah, that's what i meant, that doesn't work...

how do you spawn a dqy file? _spawnlp(P_NOWAIT, "dqyfile.dqy", "dqyfile.dqy", NULL) gives an error -1. Thanks in advance.

help with spawning a dqy file? _spawnlp(P_NOWAIT, "dqyfile.dqy", "dqyfile.dqy", NULL) gives an error -1. Thanks in advance.

Can someone help with spawning a dqy file? _spawnlp(P_NOWAIT, "dqyfile.dqy", "dqyfile.dqy", NULL) gives an error -1. Thanks in advance.

Arles thank you, that was a good idea. Unfortunately the SQL code creates the create table without the server specified! Ugh! The databases are on different servers...

I am still getting the following error: Server: Msg 117, Level 15, State 1, Line 3 The object name 'server.db.dbo.' contains more than the maximum number of prefixes. The maximum is 2. help please!

nope, i got an incorrect sytax near '\' any other ideas?

I need to do this programmatically.............

Well I am able to create a table on a database on a linked server by using that without the server specified. The problem occurs when there is a database on each server with the same name and it uses the database on the current server instead of the linked. So it is possible to create a table...

I need to create a table on a database on a linked server... I get the following error when specifying the server: create table server.db.dbo.test_table ( col_test char(10) ) Server: Msg 117, Level 15, State 1, Line 2 The object name 'server.db.dbo.' contains more than the maximum number of...

help please!?

how can i create a table on another server?

please help!

I am trying to create a table in another database, why am i getting this error and how can I avoid it? Thanks! create table dbsrv.db.dbo.table_name ( col_test char(10) ) The object name 'dbsrv.db.dbo.table_name.' contains more than the maximum number of prefixes. The maximum is 2.

Ok it seems that adding 'WITH ROLLBACK IMMEDIATE' gets it to work correctly? So I have another question.... this statement will only work with SQL 2000, what to use for SQL 7? sp_dboption will not kill current users and you cannot use it if more than one user is in the system at that time...

The following should kill all SQL users and allow only a single user: ALTER DATABASE db SET SINGLE_USER For some reason this runs forever and ever and does not seem to stop and I have no idea why. ALTER DATABASE db SET MULTI_USER only takes a second to run. I need this to work on SQL7 and...

I get this error: Database state cannot be changed while other users are using the database 'db'

so does setting to SET_SINGLE_USER autmatically kill all other user connections?

thanks, i looked at this but it is more involved than what i am looking for. is there a simple command to kill all users on a database?

How can you programatically kill all SQL user connections using SQL?