Is there any way of adding an OBDC connection to multiple computers without
going to each system. I need to push out a new SQL Server connection, does
anyone know an easy way.
Thanks!
Use a DSN-less connection.
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"HenryG" <HenryG@.discussions.microsoft.com> wrote in message
news:49B3EF04-D325-462C-9FFC-A79600D0CAD9@.microsoft.com...
> Is there any way of adding an OBDC connection to multiple computers
> without
> going to each system. I need to push out a new SQL Server connection,
> does
> anyone know an easy way.
> Thanks!
sql
Showing posts with label link. Show all posts
Showing posts with label link. Show all posts
Thursday, March 29, 2012
Tuesday, March 27, 2012
Adding a new parameter to a subreport
Each time we add a new parameter to a subreport and we link the main report's fields to be the value's to the parameters for the subreport, we get an error message stating that the parameter for the subreport has not been specified. If we physically REBOOT the computer and then reload the project, the error seems to clear up.
Is this a bug in Reporting Services or is there some other explaination.
Thanks for the information.
Actually the problem was that the developer added a parameter, but did not convert the value into an integer (cint). Sorry for the incorrect post.sqlThursday, March 8, 2012
Add Parameters!
Please visit
http://msdn.microsoft.com/library/e...tegrity_topic05
& click the link 'Implementing Cascading Operations Using Stored
Procedures'. Please refer to the sub-topic titled 'Inserting a Row into
the Primary Table'. There are 2 scripts under this sub-topic. Both the
scripts create a stored procedure named usp_OrdersInsert. After the
second script, (which creates the procedure usp_OrdersInsert using
defaults), it is stated that:
---
If the default values for the columns had been expressions, such as a
system function like GETDATE(), this modification wouldn't have been so
simple, because a default value for a stored procedure's parameter can
only be a constant. In such a situation, you need to add parameters to
indicate that a default value is desired for a column and then issue
the INSERT using the DEFAULT keyword instead of using a specific value
for the column.
---
I couldn't exactly follow the last line in the above paragraph (which
starts with "In such a situation...."). Can someone explain me this
preferably with an example?
Sorry for the inconvenience caused in navigating to the article in the
above-mentioned URL.
Thanks,
ArpanLet's assume you want to execute a stored proc omitting one of its
parameters (thereby using the parameter default value, assuming it was
specified). If you want that parameter to be variable (such as the
SYSTEM_USER function) then you couldn't use the parameter default value
because a stored proc parameter can only be a constant.
The way you'd do it would be to define an additional parameter to the
proc to indicate this scenario (or perhaps use a special value for the
existing parameter, such as NULL, if you're sure it has no other meaning
in the context). The T-SQL in your proc would then check this
additional parameter and if it has a particular value it would execute
the INSERT statement slightly differently (using the DEFAULT keyword in
the insert statement).
Let me explain with an example...
create proc MyProc
(
@.Param1 int
@.Param2 varchar(128) = 'zzz'
)
as
insert into MyTable (col1, col2)
values (@.Param1, @.Param2)
go
exec MyProc @.Param1=7, @.Param2='abc'
exec MyProc @.Param1=8
OK, everything is fine. The 2nd call would use the value 'zzz' for
@.Param2 because we omitted that parameter when we called MyProc the 2nd
time. But what if we wanted a variable value for @.Param2 instead of
'zzz', like the result of the SYSTEM_USER function for instance? The
proc would look like:
create proc MyProc
(
@.Param1 int
@.Param2 varchar(128) = SYSTEM_USER
)
as
insert into MyTable (col1, col2)
values (@.Param1, @.Param2)
go
But that's invalid syntax! The proc won't even compile. There are a
couple ways to get around that. They both require that the default
value be specified at the table constraint level, so that the DDL for
MyTable looks like:
create table MyTable
(
col1 int,
col2 varchar(128) *DEFAULT SYSTEM_USER*
)
Then you could either use a special value (eg. NULL) for @.Param2 like this:
create proc MyProc
(
@.Param1 int,
@.Param2 varchar(128) = null
)
as
if (@.Param2 is null)
insert into MyTable (col1, col2)
values (@.Param1, *DEFAULT*) -- Use the table default for col2
else
insert into MyTable (col1, col2)
values (@.Param1, @.Param2)
go
which would force SQL Server to use the default defined at the table
constraint level when the insert statement was called. Alternately, if
NULL was a valid value that you wanted to allow for @.Param2, you could
have a 3rd parameter to the proc that would represent this condition,
like this:
create proc MyProc
(
@.Param1 int,
@.Param2 varchar(128) = null,
@.UseDefaultValue bit = 0
)
as
if (@.UseDefaultValue = 1)
insert into MyTable (col1, col2)
values (@.Param1, *DEFAULT*) -- Use the table default for col2
else
insert into MyTable (col1, col2)
values (@.Param1, @.Param2)
go
This would do the same as in the previous schema for MyProc except that
it would also allow MyTable.col2 to be NULL. For example
exec MyProc @.Param1=7, @.Param2='abc' -- MyTable.col2 would be 'abc'
exec MyProc @.Param1=8 -- MyTable.col2 would be NULL
exec MyProc @.Param1=9, @.UseDefaultValue=1 -- MyTable.col2 would be
the result of the SYSTEM_USER function
I hope this make it a little clearer and that I haven't just
you even more.
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Arpan wrote:
>Please visit
>http://msdn.microsoft.com/library/e...tegrity_topic05
>& click the link 'Implementing Cascading Operations Using Stored
>Procedures'. Please refer to the sub-topic titled 'Inserting a Row into
>the Primary Table'. There are 2 scripts under this sub-topic. Both the
>scripts create a stored procedure named usp_OrdersInsert. After the
>second script, (which creates the procedure usp_OrdersInsert using
>defaults), it is stated that:
>---
>If the default values for the columns had been expressions, such as a
>system function like GETDATE(), this modification wouldn't have been so
>simple, because a default value for a stored procedure's parameter can
>only be a constant. In such a situation, you need to add parameters to
>indicate that a default value is desired for a column and then issue
>the INSERT using the DEFAULT keyword instead of using a specific value
>for the column.
>---
>I couldn't exactly follow the last line in the above paragraph (which
>starts with "In such a situation...."). Can someone explain me this
>preferably with an example?
>Sorry for the inconvenience caused in navigating to the article in the
>above-mentioned URL.
>Thanks,
>Arpan
>
>|||Thank you very much, Mike, for your input & for devoting your precious
time in helping me out. Your explanation with the appropriate examples
has really made things clearer. I doubt if anyone else could have
clarified my doubts in a better way.
Thanks once again,
Regards,
Arpan
http://msdn.microsoft.com/library/e...tegrity_topic05
& click the link 'Implementing Cascading Operations Using Stored
Procedures'. Please refer to the sub-topic titled 'Inserting a Row into
the Primary Table'. There are 2 scripts under this sub-topic. Both the
scripts create a stored procedure named usp_OrdersInsert. After the
second script, (which creates the procedure usp_OrdersInsert using
defaults), it is stated that:
---
If the default values for the columns had been expressions, such as a
system function like GETDATE(), this modification wouldn't have been so
simple, because a default value for a stored procedure's parameter can
only be a constant. In such a situation, you need to add parameters to
indicate that a default value is desired for a column and then issue
the INSERT using the DEFAULT keyword instead of using a specific value
for the column.
---
I couldn't exactly follow the last line in the above paragraph (which
starts with "In such a situation...."). Can someone explain me this
preferably with an example?
Sorry for the inconvenience caused in navigating to the article in the
above-mentioned URL.
Thanks,
ArpanLet's assume you want to execute a stored proc omitting one of its
parameters (thereby using the parameter default value, assuming it was
specified). If you want that parameter to be variable (such as the
SYSTEM_USER function) then you couldn't use the parameter default value
because a stored proc parameter can only be a constant.
The way you'd do it would be to define an additional parameter to the
proc to indicate this scenario (or perhaps use a special value for the
existing parameter, such as NULL, if you're sure it has no other meaning
in the context). The T-SQL in your proc would then check this
additional parameter and if it has a particular value it would execute
the INSERT statement slightly differently (using the DEFAULT keyword in
the insert statement).
Let me explain with an example...
create proc MyProc
(
@.Param1 int
@.Param2 varchar(128) = 'zzz'
)
as
insert into MyTable (col1, col2)
values (@.Param1, @.Param2)
go
exec MyProc @.Param1=7, @.Param2='abc'
exec MyProc @.Param1=8
OK, everything is fine. The 2nd call would use the value 'zzz' for
@.Param2 because we omitted that parameter when we called MyProc the 2nd
time. But what if we wanted a variable value for @.Param2 instead of
'zzz', like the result of the SYSTEM_USER function for instance? The
proc would look like:
create proc MyProc
(
@.Param1 int
@.Param2 varchar(128) = SYSTEM_USER
)
as
insert into MyTable (col1, col2)
values (@.Param1, @.Param2)
go
But that's invalid syntax! The proc won't even compile. There are a
couple ways to get around that. They both require that the default
value be specified at the table constraint level, so that the DDL for
MyTable looks like:
create table MyTable
(
col1 int,
col2 varchar(128) *DEFAULT SYSTEM_USER*
)
Then you could either use a special value (eg. NULL) for @.Param2 like this:
create proc MyProc
(
@.Param1 int,
@.Param2 varchar(128) = null
)
as
if (@.Param2 is null)
insert into MyTable (col1, col2)
values (@.Param1, *DEFAULT*) -- Use the table default for col2
else
insert into MyTable (col1, col2)
values (@.Param1, @.Param2)
go
which would force SQL Server to use the default defined at the table
constraint level when the insert statement was called. Alternately, if
NULL was a valid value that you wanted to allow for @.Param2, you could
have a 3rd parameter to the proc that would represent this condition,
like this:
create proc MyProc
(
@.Param1 int,
@.Param2 varchar(128) = null,
@.UseDefaultValue bit = 0
)
as
if (@.UseDefaultValue = 1)
insert into MyTable (col1, col2)
values (@.Param1, *DEFAULT*) -- Use the table default for col2
else
insert into MyTable (col1, col2)
values (@.Param1, @.Param2)
go
This would do the same as in the previous schema for MyProc except that
it would also allow MyTable.col2 to be NULL. For example
exec MyProc @.Param1=7, @.Param2='abc' -- MyTable.col2 would be 'abc'
exec MyProc @.Param1=8 -- MyTable.col2 would be NULL
exec MyProc @.Param1=9, @.UseDefaultValue=1 -- MyTable.col2 would be
the result of the SYSTEM_USER function
I hope this make it a little clearer and that I haven't just
you even more.
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Arpan wrote:
>Please visit
>http://msdn.microsoft.com/library/e...tegrity_topic05
>& click the link 'Implementing Cascading Operations Using Stored
>Procedures'. Please refer to the sub-topic titled 'Inserting a Row into
>the Primary Table'. There are 2 scripts under this sub-topic. Both the
>scripts create a stored procedure named usp_OrdersInsert. After the
>second script, (which creates the procedure usp_OrdersInsert using
>defaults), it is stated that:
>---
>If the default values for the columns had been expressions, such as a
>system function like GETDATE(), this modification wouldn't have been so
>simple, because a default value for a stored procedure's parameter can
>only be a constant. In such a situation, you need to add parameters to
>indicate that a default value is desired for a column and then issue
>the INSERT using the DEFAULT keyword instead of using a specific value
>for the column.
>---
>I couldn't exactly follow the last line in the above paragraph (which
>starts with "In such a situation...."). Can someone explain me this
>preferably with an example?
>Sorry for the inconvenience caused in navigating to the article in the
>above-mentioned URL.
>Thanks,
>Arpan
>
>|||Thank you very much, Mike, for your input & for devoting your precious
time in helping me out. Your explanation with the appropriate examples
has really made things clearer. I doubt if anyone else could have
clarified my doubts in a better way.
Thanks once again,
Regards,
Arpan
Tuesday, March 6, 2012
Add Linked Server Failed
hi,
i have added a link server but it fails when i try to retrieve data.
SQL server in on the same machine
i have created the another SQL server instance
Main Server: SERVER1
Instance: SERVER1/NewServer
EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL Server'
EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
when i try to run the above query it gives me the error
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near '/'.
anyone have suggestion??
Aditry this
select * from [SERVER1/NewServer].db1.dbo.tbl_Prouduct|||i try this too but its still not working
i have added a link server but it fails when i try to retrieve data.
SQL server in on the same machine
i have created the another SQL server instance
Main Server: SERVER1
Instance: SERVER1/NewServer
EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL Server'
EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
when i try to run the above query it gives me the error
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near '/'.
anyone have suggestion??
Aditry this
select * from [SERVER1/NewServer].db1.dbo.tbl_Prouduct|||i try this too but its still not working
Add Linked Server Failed
hi,
i have added a link server but it fails when i try to retrieve data.
SQL server in on the same machine
i have created the another SQL server instance
Main Server: SERVER1
Instance: SERVER1/NewServer
EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL
Server'
EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
when i try to run the above query it gives me the error
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near '/'.
anyone have suggestion?
Adi
This was just dicussed this week. The "/" is a special character not
normally allowed in an identifier. Either give the linked server a
"regular" name or delimit the name with brackets - [SERVER1/NewServer]. BOL
uses this same situation as an example.
"Adeel Ahmed" <adeel.ahmed@.pk.softechww.com> wrote in message
news:O0qoJPu0EHA.2876@.TK2MSFTNGP12.phx.gbl...
> hi,
> i have added a link server but it fails when i try to retrieve data.
> SQL server in on the same machine
> i have created the another SQL server instance
> Main Server: SERVER1
> Instance: SERVER1/NewServer
> EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL
> Server'
> EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
> select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
> when i try to run the above query it gives me the error
> Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near '/'.
>
> anyone have suggestion?
> Adi
>
|||Thanks,
i had resolve the problem.
actually i try this too
select * from [Server1/Newserver].dbo.db1.tbl_product
but its still not work
but when i used back slash "\" to register new linked server and
retrieve records like that
select * from [Server1\Newserver].dbo.db1.tbl_product
its work fine
thanks
Adi
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Yeah, smart. Look it up. And do us a favor and don't multipost. I just answered this question in another thread just to come to find out the it was "discovered" or answered in another.
Don't waste people's time like that.
Sincerely,
Anthony Thomas
"Adeel Ahmed" <itsmeadeel@.hotmail.com> wrote in message news:ekkVr1G1EHA.1452@.TK2MSFTNGP11.phx.gbl...
Thanks,
i had resolve the problem.
actually i try this too
select * from [Server1/Newserver].dbo.db1.tbl_product
but its still not work
but when i used back slash "\" to register new linked server and
retrieve records like that
select * from [Server1\Newserver].dbo.db1.tbl_product
its work fine
thanks
Adi
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
i have added a link server but it fails when i try to retrieve data.
SQL server in on the same machine
i have created the another SQL server instance
Main Server: SERVER1
Instance: SERVER1/NewServer
EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL
Server'
EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
when i try to run the above query it gives me the error
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near '/'.
anyone have suggestion?
Adi
This was just dicussed this week. The "/" is a special character not
normally allowed in an identifier. Either give the linked server a
"regular" name or delimit the name with brackets - [SERVER1/NewServer]. BOL
uses this same situation as an example.
"Adeel Ahmed" <adeel.ahmed@.pk.softechww.com> wrote in message
news:O0qoJPu0EHA.2876@.TK2MSFTNGP12.phx.gbl...
> hi,
> i have added a link server but it fails when i try to retrieve data.
> SQL server in on the same machine
> i have created the another SQL server instance
> Main Server: SERVER1
> Instance: SERVER1/NewServer
> EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL
> Server'
> EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
> select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
> when i try to run the above query it gives me the error
> Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near '/'.
>
> anyone have suggestion?
> Adi
>
|||Thanks,
i had resolve the problem.
actually i try this too
select * from [Server1/Newserver].dbo.db1.tbl_product
but its still not work
but when i used back slash "\" to register new linked server and
retrieve records like that
select * from [Server1\Newserver].dbo.db1.tbl_product
its work fine
thanks
Adi
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Yeah, smart. Look it up. And do us a favor and don't multipost. I just answered this question in another thread just to come to find out the it was "discovered" or answered in another.
Don't waste people's time like that.
Sincerely,
Anthony Thomas
"Adeel Ahmed" <itsmeadeel@.hotmail.com> wrote in message news:ekkVr1G1EHA.1452@.TK2MSFTNGP11.phx.gbl...
Thanks,
i had resolve the problem.
actually i try this too
select * from [Server1/Newserver].dbo.db1.tbl_product
but its still not work
but when i used back slash "\" to register new linked server and
retrieve records like that
select * from [Server1\Newserver].dbo.db1.tbl_product
its work fine
thanks
Adi
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Add Linked Server Failed
hi,
i have added a link server but it fails when i try to retrieve data.
SQL server in on the same machine
i have created the another SQL server instance
Main Server: SERVER1
Instance: SERVER1/NewServer
EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL
Server'
EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
when i try to run the above query it gives me the error
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near '/'.
anyone have suggestion'
AdiThis was just dicussed this week. The "/" is a special character not
normally allowed in an identifier. Either give the linked server a
"regular" name or delimit the name with brackets - [SERVER1/NewServer]. BOL
uses this same situation as an example.
"Adeel Ahmed" <adeel.ahmed@.pk.softechww.com> wrote in message
news:O0qoJPu0EHA.2876@.TK2MSFTNGP12.phx.gbl...
> hi,
> i have added a link server but it fails when i try to retrieve data.
> SQL server in on the same machine
> i have created the another SQL server instance
> Main Server: SERVER1
> Instance: SERVER1/NewServer
> EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL
> Server'
> EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
> select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
> when i try to run the above query it gives me the error
> Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near '/'.
>
> anyone have suggestion'
> Adi
>
i have added a link server but it fails when i try to retrieve data.
SQL server in on the same machine
i have created the another SQL server instance
Main Server: SERVER1
Instance: SERVER1/NewServer
EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL
Server'
EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
when i try to run the above query it gives me the error
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near '/'.
anyone have suggestion'
AdiThis was just dicussed this week. The "/" is a special character not
normally allowed in an identifier. Either give the linked server a
"regular" name or delimit the name with brackets - [SERVER1/NewServer]. BOL
uses this same situation as an example.
"Adeel Ahmed" <adeel.ahmed@.pk.softechww.com> wrote in message
news:O0qoJPu0EHA.2876@.TK2MSFTNGP12.phx.gbl...
> hi,
> i have added a link server but it fails when i try to retrieve data.
> SQL server in on the same machine
> i have created the another SQL server instance
> Main Server: SERVER1
> Instance: SERVER1/NewServer
> EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL
> Server'
> EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
> select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
> when i try to run the above query it gives me the error
> Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near '/'.
>
> anyone have suggestion'
> Adi
>
Add Linked Server Failed
hi,
i have added a link server but it fails when i try to retrieve data.
SQL server in on the same machine
i have created the another SQL server instance
Main Server: SERVER1
Instance: SERVER1/NewServer
EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL
Server'
EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
when i try to run the above query it gives me the error
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near '/'.
anyone have suggestion'
AdiThis was just dicussed this week. The "/" is a special character not
normally allowed in an identifier. Either give the linked server a
"regular" name or delimit the name with brackets - [SERVER1/NewServer].
BOL
uses this same situation as an example.
"Adeel Ahmed" <adeel.ahmed@.pk.softechww.com> wrote in message
news:O0qoJPu0EHA.2876@.TK2MSFTNGP12.phx.gbl...
> hi,
> i have added a link server but it fails when i try to retrieve data.
> SQL server in on the same machine
> i have created the another SQL server instance
> Main Server: SERVER1
> Instance: SERVER1/NewServer
> EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL
> Server'
> EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
> select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
> when i try to run the above query it gives me the error
> Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near '/'.
>
> anyone have suggestion'
> Adi
>|||Thanks,
i had resolve the problem.
actually i try this too
select * from [Server1/Newserver].dbo.db1.tbl_product
but its still not work
but when i used back slash "\" to register new linked server and
retrieve records like that
select * from [Server1\Newserver].dbo.db1.tbl_product
its work fine
thanks
Adi
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Yeah, smart. Look it up. And do us a favor and don't multipost. I just an
swered this question in another thread just to come to find out the it was "
discovered" or answered in another.
Don't waste people's time like that.
Sincerely,
Anthony Thomas
--
"Adeel Ahmed" <itsmeadeel@.hotmail.com> wrote in message news:ekkVr1G1EHA.1
452@.TK2MSFTNGP11.phx.gbl...
Thanks,
i had resolve the problem.
actually i try this too
select * from [Server1/Newserver].dbo.db1.tbl_product
but its still not work
but when i used back slash "\" to register new linked server and
retrieve records like that
select * from [Server1\Newserver].dbo.db1.tbl_product
its work fine
thanks
Adi
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
i have added a link server but it fails when i try to retrieve data.
SQL server in on the same machine
i have created the another SQL server instance
Main Server: SERVER1
Instance: SERVER1/NewServer
EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL
Server'
EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
when i try to run the above query it gives me the error
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near '/'.
anyone have suggestion'
AdiThis was just dicussed this week. The "/" is a special character not
normally allowed in an identifier. Either give the linked server a
"regular" name or delimit the name with brackets - [SERVER1/NewServer].
BOL
uses this same situation as an example.
"Adeel Ahmed" <adeel.ahmed@.pk.softechww.com> wrote in message
news:O0qoJPu0EHA.2876@.TK2MSFTNGP12.phx.gbl...
> hi,
> i have added a link server but it fails when i try to retrieve data.
> SQL server in on the same machine
> i have created the another SQL server instance
> Main Server: SERVER1
> Instance: SERVER1/NewServer
> EXEC sp_addlinkedserver @.server = SERVER1/NewServer, @.srvproduct = 'SQL
> Server'
> EXEC sp_addlinkedsrvlogin 'SERVER1/NewServer', false, NULL, 'sa', 'test'
> select * from SERVER1/NewServer.db1.dbo.tbl_Prouduct
> when i try to run the above query it gives me the error
> Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near '/'.
>
> anyone have suggestion'
> Adi
>|||Thanks,
i had resolve the problem.
actually i try this too
select * from [Server1/Newserver].dbo.db1.tbl_product
but its still not work
but when i used back slash "\" to register new linked server and
retrieve records like that
select * from [Server1\Newserver].dbo.db1.tbl_product
its work fine
thanks
Adi
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Yeah, smart. Look it up. And do us a favor and don't multipost. I just an
swered this question in another thread just to come to find out the it was "
discovered" or answered in another.
Don't waste people's time like that.
Sincerely,
Anthony Thomas
--
"Adeel Ahmed" <itsmeadeel@.hotmail.com> wrote in message news:ekkVr1G1EHA.1
452@.TK2MSFTNGP11.phx.gbl...
Thanks,
i had resolve the problem.
actually i try this too
select * from [Server1/Newserver].dbo.db1.tbl_product
but its still not work
but when i used back slash "\" to register new linked server and
retrieve records like that
select * from [Server1\Newserver].dbo.db1.tbl_product
its work fine
thanks
Adi
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Thursday, February 16, 2012
add a pramater.value to the jump to url link
I need to open a aspx page from a report jump to ulr action. but I need to pass in a prameter value. see example
http://ktec_inet/gco/productionreports/prod_asp/pcba_station_detail.asp?processname=335ICT×tampw=999999999&userid=WeeklyYieldPCBA&queryflag= Parameters!prod_cls.Value
--
Message posted via http://www.sqlmonster.comUse the expression
="http://ktec_inet/gco/productionreports/prod_asp/pcba_station_detail.asp?
processname=335ICT×tampw=999999999&userid=WeeklyYieldPCBA&queryflag=" &
Parameters!prod_cls.Value
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lee Hopkins via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:4b989eb2a43e487a8a731afd19e27357@.SQLMonster.com...
>I need to open a aspx page from a report jump to ulr action. but I need to
>pass in a prameter value. see example
> http://ktec_inet/gco/productionreports/prod_asp/pcba_station_detail.asp?processname=335ICT×tampw=999999999&userid=WeeklyYieldPCBA&queryflag=
> Parameters!prod_cls.Value
> --
> Message posted via http://www.sqlmonster.com
http://ktec_inet/gco/productionreports/prod_asp/pcba_station_detail.asp?processname=335ICT×tampw=999999999&userid=WeeklyYieldPCBA&queryflag= Parameters!prod_cls.Value
--
Message posted via http://www.sqlmonster.comUse the expression
="http://ktec_inet/gco/productionreports/prod_asp/pcba_station_detail.asp?
processname=335ICT×tampw=999999999&userid=WeeklyYieldPCBA&queryflag=" &
Parameters!prod_cls.Value
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lee Hopkins via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:4b989eb2a43e487a8a731afd19e27357@.SQLMonster.com...
>I need to open a aspx page from a report jump to ulr action. but I need to
>pass in a prameter value. see example
> http://ktec_inet/gco/productionreports/prod_asp/pcba_station_detail.asp?processname=335ICT×tampw=999999999&userid=WeeklyYieldPCBA&queryflag=
> Parameters!prod_cls.Value
> --
> Message posted via http://www.sqlmonster.com
Monday, February 13, 2012
Adam rocks..
Adam,
This link http://www.sql-server-performance.c...ing_indexes.asp
was exactly what I needed. Thank you.
Sincerely
PatrickGlad to help.
Have a good Thanksgiving, if you're in the US...
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"news.microsoft.com" <Patrick@.hotmail.com> wrote in message
news:u6GSykG8FHA.4036@.TK2MSFTNGP11.phx.gbl...
> Adam,
> This link http://www.sql-server-performance.c...ing_indexes.asp
> was exactly what I needed. Thank you.
> Sincerely
> Patrick
>|||Does that mean you can't have a good thanksgiving if you're not in the US?
;-)
No, I guess not; "WHERE Country = 'USA'" does not imply what occurs
"WHERE Country != 'USA'"...but I think I'll have a good 4th Thursday in
November anyway (well, I'll try at least)...hey, that's today!
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Adam Machanic wrote:
>Glad to help.
>Have a good Thanksgiving, if you're in the US...
>
>|||Have a good Thursday, no matter where you are :)
--
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message news:e0M
mZOI8FHA.3636@.TK2MSFTNGP09.phx.gbl...
Does that mean you can't have a good thanksgiving if you're not in the US?
;-)
No, I guess not; "WHERE Country = 'USA'" does not imply what occurs "WHERE C
ountry != 'USA'"...but I think I'll have a good 4th Thursday in November any
way (well, I'll try at least)...hey, that's today!
--
mike hodgson
blog: http://sqlnerd.blogspot.com
Adam Machanic wrote:
Glad to help.
Have a good Thanksgiving, if you're in the US...
This link http://www.sql-server-performance.c...ing_indexes.asp
was exactly what I needed. Thank you.
Sincerely
PatrickGlad to help.
Have a good Thanksgiving, if you're in the US...
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"news.microsoft.com" <Patrick@.hotmail.com> wrote in message
news:u6GSykG8FHA.4036@.TK2MSFTNGP11.phx.gbl...
> Adam,
> This link http://www.sql-server-performance.c...ing_indexes.asp
> was exactly what I needed. Thank you.
> Sincerely
> Patrick
>|||Does that mean you can't have a good thanksgiving if you're not in the US?
;-)
No, I guess not; "WHERE Country = 'USA'" does not imply what occurs
"WHERE Country != 'USA'"...but I think I'll have a good 4th Thursday in
November anyway (well, I'll try at least)...hey, that's today!
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Adam Machanic wrote:
>Glad to help.
>Have a good Thanksgiving, if you're in the US...
>
>|||Have a good Thursday, no matter where you are :)
--
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message news:e0M
mZOI8FHA.3636@.TK2MSFTNGP09.phx.gbl...
Does that mean you can't have a good thanksgiving if you're not in the US?
;-)
No, I guess not; "WHERE Country = 'USA'" does not imply what occurs "WHERE C
ountry != 'USA'"...but I think I'll have a good 4th Thursday in November any
way (well, I'll try at least)...hey, that's today!
--
mike hodgson
blog: http://sqlnerd.blogspot.com
Adam Machanic wrote:
Glad to help.
Have a good Thanksgiving, if you're in the US...
Adam - FYI
I clicked your link in your signature and got this
Using Maxthon Browser
.Text - Application Error!
Details
ArgumentException
The SqlParameter with ParameterName '@.ItemCount' is already contained by
another SqlParameterCollection.
Return to site
Simon Worth
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:eaAJLU$IFHA.3336@.TK2MSFTNGP10.phx.gbl...
> This is the first I've ever heard of that SQL-NS... Strange, because MS
> documentation on Notification Services uses SQL-NS as well -- you'd think
> they would have used a different acronym they hadn't already used!
> Anyway, maybe the .clients or .tools groups can offer more help... I have
> never seen mention of this technology in this group in the last year and a
> half that I've been paying close attention.
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.sqljunkies.com/weblog/amachanic
> --
>
> <Eric> wrote in message news:Oyk1kH$IFHA.1248@.TK2MSFTNGP10.phx.gbl...
> SQL-NS
news:%23sKzqR5IFHA.3568@.TK2MSFTNGP10.phx.gbl...
to
Naturally,
SQL-DMO
>Yeah, that's the site -- hit refresh a couple of times and it goes away.
Been happening for months, unfortunately. The admin claims it
will -finally- be fixed within the next two days when he upgrades to a more
recent version of the blog software...
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"Simon Worth" <REMOVEFIRST_simon.worth@.gmail.com> wrote in message
news:%235HhxW$IFHA.2744@.TK2MSFTNGP15.phx.gbl...
> I clicked your link in your signature and got this
> Using Maxthon Browser
> .Text - Application Error!
> Details
> ArgumentException
> The SqlParameter with ParameterName '@.ItemCount' is already contained by
> another SqlParameterCollection.
>
> Return to site
>
> --
> Simon Worth
>
> "Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
> news:eaAJLU$IFHA.3336@.TK2MSFTNGP10.phx.gbl...
think
have
a
automate
message
> news:%23sKzqR5IFHA.3568@.TK2MSFTNGP10.phx.gbl...
easy
> to
> Naturally,
publication-subscription
when
> SQL-DMO
>|||Cool, just wanted you to know in case the error was new.
It's all good.
Simon Worth
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:uAyK5b$IFHA.3928@.TK2MSFTNGP09.phx.gbl...
> Yeah, that's the site -- hit refresh a couple of times and it goes away.
> Been happening for months, unfortunately. The admin claims it
> will -finally- be fixed within the next two days when he upgrades to a
more
> recent version of the blog software...
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.sqljunkies.com/weblog/amachanic
> --
>
> "Simon Worth" <REMOVEFIRST_simon.worth@.gmail.com> wrote in message
> news:%235HhxW$IFHA.2744@.TK2MSFTNGP15.phx.gbl...
MS
> think
> have
and
> a
I'm
> automate
but
> message
> easy
(Notification
> publication-subscription
> when
>
Using Maxthon Browser
.Text - Application Error!
Details
ArgumentException
The SqlParameter with ParameterName '@.ItemCount' is already contained by
another SqlParameterCollection.
Return to site
Simon Worth
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:eaAJLU$IFHA.3336@.TK2MSFTNGP10.phx.gbl...
> This is the first I've ever heard of that SQL-NS... Strange, because MS
> documentation on Notification Services uses SQL-NS as well -- you'd think
> they would have used a different acronym they hadn't already used!
> Anyway, maybe the .clients or .tools groups can offer more help... I have
> never seen mention of this technology in this group in the last year and a
> half that I've been paying close attention.
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.sqljunkies.com/weblog/amachanic
> --
>
> <Eric> wrote in message news:Oyk1kH$IFHA.1248@.TK2MSFTNGP10.phx.gbl...
> SQL-NS
news:%23sKzqR5IFHA.3568@.TK2MSFTNGP10.phx.gbl...
to
Naturally,
SQL-DMO
>Yeah, that's the site -- hit refresh a couple of times and it goes away.
Been happening for months, unfortunately. The admin claims it
will -finally- be fixed within the next two days when he upgrades to a more
recent version of the blog software...
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"Simon Worth" <REMOVEFIRST_simon.worth@.gmail.com> wrote in message
news:%235HhxW$IFHA.2744@.TK2MSFTNGP15.phx.gbl...
> I clicked your link in your signature and got this
> Using Maxthon Browser
> .Text - Application Error!
> Details
> ArgumentException
> The SqlParameter with ParameterName '@.ItemCount' is already contained by
> another SqlParameterCollection.
>
> Return to site
>
> --
> Simon Worth
>
> "Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
> news:eaAJLU$IFHA.3336@.TK2MSFTNGP10.phx.gbl...
think
have
a
automate
message
> news:%23sKzqR5IFHA.3568@.TK2MSFTNGP10.phx.gbl...
easy
> to
> Naturally,
publication-subscription
when
> SQL-DMO
>|||Cool, just wanted you to know in case the error was new.
It's all good.
Simon Worth
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:uAyK5b$IFHA.3928@.TK2MSFTNGP09.phx.gbl...
> Yeah, that's the site -- hit refresh a couple of times and it goes away.
> Been happening for months, unfortunately. The admin claims it
> will -finally- be fixed within the next two days when he upgrades to a
more
> recent version of the blog software...
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.sqljunkies.com/weblog/amachanic
> --
>
> "Simon Worth" <REMOVEFIRST_simon.worth@.gmail.com> wrote in message
> news:%235HhxW$IFHA.2744@.TK2MSFTNGP15.phx.gbl...
MS
> think
> have
and
> a
I'm
> automate
but
> message
> easy
(Notification
> publication-subscription
> when
>
Subscribe to:
Posts (Atom)