problem while creating index for temporary table...

Hi,

i have created index for a temporary table and this script should used by multiusers.So when second user connecting to it is giving index i mean object already exists.

So what i need is when the second user connected the script should create one more index on temporary table.Will sql server provide any random way of creating indexes if the index exists already with that name?

Thank You,

Seeing the actual script will be helpful.

What advantage do you think you get from creating multiple (identical) indices on the same table?

|||

Nope..

SQL Server is cleaver enough to handel this situation.

When you create a index or constraint on the Temp Table, eventhough the index name is duplicate it will allow.

But it only possible on temp tables (prefixed with single #).

To Test this,

Open Two window,

Execute the below window on the opened 2 window..

create table #test

(

id int

);

Insert Into #test values(1);

Insert Into #test values(2);

Create clustered index testindex on #test(id)

Now you wont get any error on any of the window. Rite?

To fetch the created index details, execute the below code on any one of the window..

select * from sysindexes where name like '%test%'

Now you can see the 2 rows with same indexname but refereing with different table. Yes. all the temp tables (#) will be suffixed with unique number to avoid the object already found error while multiple users connects.

Problem when failing over to second Node

I recently moved a cluster out of a one domain to the
next. Worked through all the issues and I am still having
a problem I can not seem to resolve.
When I try to fail over to the second node, I see that
SQL Network Name(virtualnamegiven)in cluster
administrator fails. When I look in event viewr I get
multiple errors all containing this error, Cluster
resource 'SQL Network Name(virtualnamegiven)' failed.
Has anyone ever seen this or know how to troubleshoot
this problem. Any help would be appreciated. Please email
me at tim.johnson@.instinet.com.
Thanks
When you bring a "name" resource on line we are trying to register the DSN
name with Active Directory. YOu need to find put what is preventing the
Name from coming online on the network.
Try PING by the "name" while it is off-line. You should NOT get a
response.
Also, wee if there is a HOST entry with the name, but with the old IP
address.
Chris Skorlinski
Microsoft SQL Server Support
Please reply directly to the thread with any updates.
This posting is provided "as is" with no warranties and confers no rights.

Problem when connecting to a named sql 2000 instance

Hi,
I have a problem when connecting to a named sql 2000 instance . The instance
is running in a 2 node cluster configuration. The second instance on the
other node works fine.
When I try to connect with a client on another pc, the connection only works
when I set the correct (static) port number.
But if I leave it to dynamically determine ports it is not able to connect.
There is no firewall between the client pc and the database server
and udp port 1434 is listening.
Stranger is that this problem also occurs on the server itself. When i
connect to the servernode where the instance of sql is running,
i have to set an alias with the portnumber to be able to connect to the
instance. Without this the connection fails.
Anybody any idea(s)?
Regards,
CihatUnfortunately no response. Here my response so that others with same problem
maybe solve it more quickly. When this happens and all checks appear okey,
you have to failover the group and reboot the server where this problem
occur. After the reboot it worked fine for me. Still dont know the cause, bu
t
it works now.
"Cihat" wrote:

> Hi,
> I have a problem when connecting to a named sql 2000 instance . The instan
ce
> is running in a 2 node cluster configuration. The second instance on the
> other node works fine.
> When I try to connect with a client on another pc, the connection only wor
ks
> when I set the correct (static) port number.
> But if I leave it to dynamically determine ports it is not able to connect
.
> There is no firewall between the client pc and the database server
> and udp port 1434 is listening.
> Stranger is that this problem also occurs on the server itself. When i
> connect to the servernode where the instance of sql is running,
> i have to set an alias with the portnumber to be able to connect to the
> instance. Without this the connection fails.
> Anybody any idea(s)?
> Regards,
> Cihat
>

Problem using the Jump to report with a Parameter in a chart repor

I created a chart report and then created a second report which has a table
in it. The second report has a report parameter called DealStatus. I went to
the Chart report and edited the action tab on the edit chart values and
select the Jump to report and selected my report and clicked on the
Parameters button.
Entered DealStatus for the Paremeter Name and =Fields!value.Value for the
Prameter Value. First I had no default value and I was getting an
rsReadOnlyReportParameter error so I added a default value for DealStatus,
and now the chart report jumps to the second report but always uses the
default value.
MikeI found the problem I forgot to add the @.DealStatus to the Dataset query
"Hotwheels" wrote:
> I created a chart report and then created a second report which has a table
> in it. The second report has a report parameter called DealStatus. I went to
> the Chart report and edited the action tab on the edit chart values and
> select the Jump to report and selected my report and clicked on the
> Parameters button.
> Entered DealStatus for the Paremeter Name and =Fields!value.Value for the
> Prameter Value. First I had no default value and I was getting an
> rsReadOnlyReportParameter error so I added a default value for DealStatus,
> and now the chart report jumps to the second report but always uses the
> default value.
> Mike
>