I just setup two new SQL 2005 Stnd x64bit servers for a customer. The
original two servers running the same SQL version have been running
fine for 3 weeks now. The mian production database is attached and SQL
seems to be working fine. When I try to create a new Maintenance Plan
or use the Maint Plan wizard, I get an error message.
The error message:
TITLE: Microsoft SQL Server Management Studio
--
The action you attempted to perform on a remote instance of SQL Server
has failed because the action requires a SQL Server component that is
not installed on the remote computer. To proceed, install SQL Server
2005 Management Tools on the remote computer, and then try again. For
more information, see "How to: Install SQL Server 2005 (Setup)" in SQL
Server 2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
----
I did run SCW on the new servers just like I did on the two original
servers.
Any thoughts? ThanksHi,
I get the exact same error - have you found a solution for your problem
yet?
My setup is a 2 node cluster with SQL 2005 SP1
Regards
Jon skrev:
> I just setup two new SQL 2005 Stnd x64bit servers for a customer. The
> original two servers running the same SQL version have been running
> fine for 3 weeks now. The mian production database is attached and SQL
> seems to be working fine. When I try to create a new Maintenance Plan
> or use the Maint Plan wizard, I get an error message.
> The error message:
> TITLE: Microsoft SQL Server Management Studio
> --
> The action you attempted to perform on a remote instance of SQL Server
> has failed because the action requires a SQL Server component that is
> not installed on the remote computer. To proceed, install SQL Server
> 2005 Management Tools on the remote computer, and then try again. For
> more information, see "How to: Install SQL Server 2005 (Setup)" in SQL
> Server 2005 Books Online, or find the article on MSDN at
> http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
> For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
> ----
> I did run SCW on the new servers just like I did on the two original
> servers.
> Any thoughts? Thanks
Showing posts with label version. Show all posts
Showing posts with label version. Show all posts
Sunday, March 25, 2012
Can not create Maintenance Plan - getting error message
I just setup two new SQL 2005 Stnd x64bit servers for a customer. The
original two servers running the same SQL version have been running
fine for 3 weeks now. The mian production database is attached and SQL
seems to be working fine. When I try to create a new Maintenance Plan
or use the Maint Plan wizard, I get an error message.
The error message:
TITLE: Microsoft SQL Server Management Studio
--
The action you attempted to perform on a remote instance of SQL Server
has failed because the action requires a SQL Server component that is
not installed on the remote computer. To proceed, install SQL Server
2005 Management Tools on the remote computer, and then try again. For
more information, see "How to: Install SQL Server 2005 (Setup)" in SQL
Server 2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
----
--
I did run SCW on the new servers just like I did on the two original
servers.
Any thoughts? ThanksHi,
I get the exact same error - have you found a solution for your problem
yet?
My setup is a 2 node cluster with SQL 2005 SP1
Regards
Jon skrev:
> I just setup two new SQL 2005 Stnd x64bit servers for a customer. The
> original two servers running the same SQL version have been running
> fine for 3 weeks now. The mian production database is attached and SQL
> seems to be working fine. When I try to create a new Maintenance Plan
> or use the Maint Plan wizard, I get an error message.
> The error message:
> TITLE: Microsoft SQL Server Management Studio
> --
> The action you attempted to perform on a remote instance of SQL Server
> has failed because the action requires a SQL Server component that is
> not installed on the remote computer. To proceed, install SQL Server
> 2005 Management Tools on the remote computer, and then try again. For
> more information, see "How to: Install SQL Server 2005 (Setup)" in SQL
> Server 2005 Books Online, or find the article on MSDN at
> http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
> For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
> ----
--
> I did run SCW on the new servers just like I did on the two original
> servers.
> Any thoughts? Thanks
original two servers running the same SQL version have been running
fine for 3 weeks now. The mian production database is attached and SQL
seems to be working fine. When I try to create a new Maintenance Plan
or use the Maint Plan wizard, I get an error message.
The error message:
TITLE: Microsoft SQL Server Management Studio
--
The action you attempted to perform on a remote instance of SQL Server
has failed because the action requires a SQL Server component that is
not installed on the remote computer. To proceed, install SQL Server
2005 Management Tools on the remote computer, and then try again. For
more information, see "How to: Install SQL Server 2005 (Setup)" in SQL
Server 2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
----
--
I did run SCW on the new servers just like I did on the two original
servers.
Any thoughts? ThanksHi,
I get the exact same error - have you found a solution for your problem
yet?
My setup is a 2 node cluster with SQL 2005 SP1
Regards
Jon skrev:
> I just setup two new SQL 2005 Stnd x64bit servers for a customer. The
> original two servers running the same SQL version have been running
> fine for 3 weeks now. The mian production database is attached and SQL
> seems to be working fine. When I try to create a new Maintenance Plan
> or use the Maint Plan wizard, I get an error message.
> The error message:
> TITLE: Microsoft SQL Server Management Studio
> --
> The action you attempted to perform on a remote instance of SQL Server
> has failed because the action requires a SQL Server component that is
> not installed on the remote computer. To proceed, install SQL Server
> 2005 Management Tools on the remote computer, and then try again. For
> more information, see "How to: Install SQL Server 2005 (Setup)" in SQL
> Server 2005 Books Online, or find the article on MSDN at
> http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
> For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
> ----
--
> I did run SCW on the new servers just like I did on the two original
> servers.
> Any thoughts? Thanks
Tuesday, March 20, 2012
Can not connect remote SqlServer
I can not connect a SqlServer (version 2005) in remote.
I have checked there are no firewall problems, and the server have been set
to allow remote connection.
How can I do?I got the following from another post in SQLServer Setup community.
The Allow Remote Conections is not the correct setting (it controls the
ability for remote servers to execute stored procedures on the local server
via a linked server) The easiest thing to do is on the server go to
Start>Programs>Microsoft SQL Server 2005>Configuration Tools>SQL Surface
Area Configuration and click on Surface Area Configuration for Services And
Connections. Under the Database Engine section on the left select Remote
Connections and select the Local and remote connections radio burron and
select Using both TCP/ip and named pipes and click Apply.
"ad" wrote:
> I can not connect a SqlServer (version 2005) in remote.
> I have checked there are no firewall problems, and the server have been se
t
> to allow remote connection.
> How can I do?
>
>
I have checked there are no firewall problems, and the server have been set
to allow remote connection.
How can I do?I got the following from another post in SQLServer Setup community.
The Allow Remote Conections is not the correct setting (it controls the
ability for remote servers to execute stored procedures on the local server
via a linked server) The easiest thing to do is on the server go to
Start>Programs>Microsoft SQL Server 2005>Configuration Tools>SQL Surface
Area Configuration and click on Surface Area Configuration for Services And
Connections. Under the Database Engine section on the left select Remote
Connections and select the Local and remote connections radio burron and
select Using both TCP/ip and named pipes and click Apply.
"ad" wrote:
> I can not connect a SqlServer (version 2005) in remote.
> I have checked there are no firewall problems, and the server have been se
t
> to allow remote connection.
> How can I do?
>
>
Can not connect remote SqlServer
I can not connect a SqlServer (version 2005) in remote.
I have checked there are no firewall problems, and the server have been set
to allow remote connection.
How can I do?I got the following from another post in SQLServer Setup community.
The Allow Remote Conections is not the correct setting (it controls the
ability for remote servers to execute stored procedures on the local server
via a linked server) The easiest thing to do is on the server go to
Start>Programs>Microsoft SQL Server 2005>Configuration Tools>SQL Surface
Area Configuration and click on Surface Area Configuration for Services And
Connections. Under the Database Engine section on the left select Remote
Connections and select the Local and remote connections radio burron and
select Using both TCP/ip and named pipes and click Apply.
"ad" wrote:
> I can not connect a SqlServer (version 2005) in remote.
> I have checked there are no firewall problems, and the server have been set
> to allow remote connection.
> How can I do?
>
>
I have checked there are no firewall problems, and the server have been set
to allow remote connection.
How can I do?I got the following from another post in SQLServer Setup community.
The Allow Remote Conections is not the correct setting (it controls the
ability for remote servers to execute stored procedures on the local server
via a linked server) The easiest thing to do is on the server go to
Start>Programs>Microsoft SQL Server 2005>Configuration Tools>SQL Surface
Area Configuration and click on Surface Area Configuration for Services And
Connections. Under the Database Engine section on the left select Remote
Connections and select the Local and remote connections radio burron and
select Using both TCP/ip and named pipes and click Apply.
"ad" wrote:
> I can not connect a SqlServer (version 2005) in remote.
> I have checked there are no firewall problems, and the server have been set
> to allow remote connection.
> How can I do?
>
>
Can not connect remote SqlServer
I can not connect a SqlServer (version 2005) in remote.
I have checked there are no firewall problems, and the server have been set
to allow remote connection.
How can I do?
I got the following from another post in SQLServer Setup community.
The Allow Remote Conections is not the correct setting (it controls the
ability for remote servers to execute stored procedures on the local server
via a linked server) The easiest thing to do is on the server go to
Start>Programs>Microsoft SQL Server 2005>Configuration Tools>SQL Surface
Area Configuration and click on Surface Area Configuration for Services And
Connections. Under the Database Engine section on the left select Remote
Connections and select the Local and remote connections radio burron and
select Using both TCP/ip and named pipes and click Apply.
"ad" wrote:
> I can not connect a SqlServer (version 2005) in remote.
> I have checked there are no firewall problems, and the server have been set
> to allow remote connection.
> How can I do?
>
>
I have checked there are no firewall problems, and the server have been set
to allow remote connection.
How can I do?
I got the following from another post in SQLServer Setup community.
The Allow Remote Conections is not the correct setting (it controls the
ability for remote servers to execute stored procedures on the local server
via a linked server) The easiest thing to do is on the server go to
Start>Programs>Microsoft SQL Server 2005>Configuration Tools>SQL Surface
Area Configuration and click on Surface Area Configuration for Services And
Connections. Under the Database Engine section on the left select Remote
Connections and select the Local and remote connections radio burron and
select Using both TCP/ip and named pipes and click Apply.
"ad" wrote:
> I can not connect a SqlServer (version 2005) in remote.
> I have checked there are no firewall problems, and the server have been set
> to allow remote connection.
> How can I do?
>
>
Monday, March 19, 2012
can MSRS 2000 run with .NET 2.0
Can MSRS 2000 run with .NET 2.0 . If not then is there any plan for a MSRS version which is compatible with MSRS 2000?No. RS 2000 is not .Net2.0 compatible.
Reporting Services 2005 is .Net 2.0 compatible. RS 2005 is being released with SQL Server 2005.
Reporting Services 2005 is .Net 2.0 compatible. RS 2005 is being released with SQL Server 2005.
Thursday, March 8, 2012
Can I work with abril ctp and migrate later to an express version?
Hello
The final customers of my application should have sql server express. Can I work with sql abril ctp and then when the final version of sql express has been released install it and migrate the database?
You should use June CTP (build 1187), not April CTP.
June CTP to RTM (Release) migration is a supported scenario. However, since you will be downgrading the SKU (e.g. Developer SKU to Express SKU) certain features may/will be unavailable. Some of this is transparent to the app (e.g. you won't get AWE support), but some may impact functionality (e.g. feature functionality is limited). It depends on what your application uses.
If you are concerned about databases only, upgrade should work fine from June CTP.
Regards,
Boris.
And when the final version of sql express and vs 2005 had been released it should work? I guess i only have to make a backup of the sql june ctp database, uninstall june ctp, uninstall vs 2005 june ctp, and then install vs 2005 profesional or team system , and then install final version of sql express and restore the database and it should work?
Am I missing something?|||
Yes, what you describe should work.
There are two parts to your question:
1. Going from June CTP to RTM – this should be just fine
2. Going from Developer SKU to Express SKU – this has caveats as outlined below
Caveat: if you use a feature that is available only on Dev/Enterprise SKU, once you migrate to Express you may run into problems. Most notable features that may create problems are database mirroring, database snapshot, failover clustering and table partitioning.
At release time there will be a document describing upgrade/downgrade process.
HTH,
Boris.
can i using linked Server in mssql server 64 bit version?
hi,
i always set the error when i used linked server to query data from other
server(32 bit) to my main server (64bit)
"Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to complete
this operation could not be found on the server (they were supplied with the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
returned 0x80004005: ]."
do i miss something or i can using linked server in 64 bit edition?
thanks,
Suwito Kurniawan
Hi
Make sure that you have MDAC 2.8 on the 32 bit machine.
You can also run a Profiler trace to see what is being sent though.
SQL Server 64 and 32 can be linked to each other, in both directions,
without any problems.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Suwito Kurniawan" <suwito@.adira.co.id> wrote in message
news:#neP7OiLFHA.2764@.tk2msftngp13.phx.gbl...
> hi,
> i always set the error when i used linked server to query data from other
> server(32 bit) to my main server (64bit)
> "Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'SQLOLEDB' reported an error.
> [OLE/DB provider returned message: Unspecified error]
> [OLE/DB provider returned message: The stored procedure required to
complete
> this operation could not be found on the server (they were supplied with
the
> ODBC setup disk for the SQL Server driver). Please contact your system
> administrator.]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
> returned 0x80004005: ]."
> do i miss something or i can using linked server in 64 bit edition?
>
> thanks,
> Suwito Kurniawan
>
i always set the error when i used linked server to query data from other
server(32 bit) to my main server (64bit)
"Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to complete
this operation could not be found on the server (they were supplied with the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
returned 0x80004005: ]."
do i miss something or i can using linked server in 64 bit edition?
thanks,
Suwito Kurniawan
Hi
Make sure that you have MDAC 2.8 on the 32 bit machine.
You can also run a Profiler trace to see what is being sent though.
SQL Server 64 and 32 can be linked to each other, in both directions,
without any problems.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Suwito Kurniawan" <suwito@.adira.co.id> wrote in message
news:#neP7OiLFHA.2764@.tk2msftngp13.phx.gbl...
> hi,
> i always set the error when i used linked server to query data from other
> server(32 bit) to my main server (64bit)
> "Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'SQLOLEDB' reported an error.
> [OLE/DB provider returned message: Unspecified error]
> [OLE/DB provider returned message: The stored procedure required to
complete
> this operation could not be found on the server (they were supplied with
the
> ODBC setup disk for the SQL Server driver). Please contact your system
> administrator.]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
> returned 0x80004005: ]."
> do i miss something or i can using linked server in 64 bit edition?
>
> thanks,
> Suwito Kurniawan
>
can i using linked Server in mssql server 64 bit version?
hi,
i always set the error when i used linked server to query data from other
server(32 bit) to my main server (64bit)
"Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to comp
lete
this operation could not be found on the server (they were supplied with the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowse
t
returned 0x80004005: ]."
do i miss something or i can using linked server in 64 bit edition?
thanks,
Suwito KurniawanHi
Make sure that you have MDAC 2.8 on the 32 bit machine.
You can also run a Profiler trace to see what is being sent though.
SQL Server 64 and 32 can be linked to each other, in both directions,
without any problems.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Suwito Kurniawan" <suwito@.adira.co.id> wrote in message
news:#neP7OiLFHA.2764@.tk2msftngp13.phx.gbl...
> hi,
> i always set the error when i used linked server to query data from other
> server(32 bit) to my main server (64bit)
> "Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'SQLOLEDB' reported an error.
> [OLE/DB provider returned message: Unspecified error]
> [OLE/DB provider returned message: The stored procedure required to
complete
> this operation could not be found on the server (they were supplied with
the
> ODBC setup disk for the SQL Server driver). Please contact your system
> administrator.]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRow
set
> returned 0x80004005: ]."
> do i miss something or i can using linked server in 64 bit edition?
>
> thanks,
> Suwito Kurniawan
>
i always set the error when i used linked server to query data from other
server(32 bit) to my main server (64bit)
"Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to comp
lete
this operation could not be found on the server (they were supplied with the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowse
t
returned 0x80004005: ]."
do i miss something or i can using linked server in 64 bit edition?
thanks,
Suwito KurniawanHi
Make sure that you have MDAC 2.8 on the 32 bit machine.
You can also run a Profiler trace to see what is being sent though.
SQL Server 64 and 32 can be linked to each other, in both directions,
without any problems.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Suwito Kurniawan" <suwito@.adira.co.id> wrote in message
news:#neP7OiLFHA.2764@.tk2msftngp13.phx.gbl...
> hi,
> i always set the error when i used linked server to query data from other
> server(32 bit) to my main server (64bit)
> "Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'SQLOLEDB' reported an error.
> [OLE/DB provider returned message: Unspecified error]
> [OLE/DB provider returned message: The stored procedure required to
complete
> this operation could not be found on the server (they were supplied with
the
> ODBC setup disk for the SQL Server driver). Please contact your system
> administrator.]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRow
set
> returned 0x80004005: ]."
> do i miss something or i can using linked server in 64 bit edition?
>
> thanks,
> Suwito Kurniawan
>
can i using linked Server in mssql server 64 bit version?
hi,
i always set the error when i used linked server to query data from other
server(32 bit) to my main server (64bit)
"Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to complete
this operation could not be found on the server (they were supplied with the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
returned 0x80004005: ]."
do i miss something or i can using linked server in 64 bit edition?
thanks,
Suwito KurniawanHi
Make sure that you have MDAC 2.8 on the 32 bit machine.
You can also run a Profiler trace to see what is being sent though.
SQL Server 64 and 32 can be linked to each other, in both directions,
without any problems.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Suwito Kurniawan" <suwito@.adira.co.id> wrote in message
news:#neP7OiLFHA.2764@.tk2msftngp13.phx.gbl...
> hi,
> i always set the error when i used linked server to query data from other
> server(32 bit) to my main server (64bit)
> "Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'SQLOLEDB' reported an error.
> [OLE/DB provider returned message: Unspecified error]
> [OLE/DB provider returned message: The stored procedure required to
complete
> this operation could not be found on the server (they were supplied with
the
> ODBC setup disk for the SQL Server driver). Please contact your system
> administrator.]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
> returned 0x80004005: ]."
> do i miss something or i can using linked server in 64 bit edition?
>
> thanks,
> Suwito Kurniawan
>
i always set the error when i used linked server to query data from other
server(32 bit) to my main server (64bit)
"Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to complete
this operation could not be found on the server (they were supplied with the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
returned 0x80004005: ]."
do i miss something or i can using linked server in 64 bit edition?
thanks,
Suwito KurniawanHi
Make sure that you have MDAC 2.8 on the 32 bit machine.
You can also run a Profiler trace to see what is being sent though.
SQL Server 64 and 32 can be linked to each other, in both directions,
without any problems.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Suwito Kurniawan" <suwito@.adira.co.id> wrote in message
news:#neP7OiLFHA.2764@.tk2msftngp13.phx.gbl...
> hi,
> i always set the error when i used linked server to query data from other
> server(32 bit) to my main server (64bit)
> "Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'SQLOLEDB' reported an error.
> [OLE/DB provider returned message: Unspecified error]
> [OLE/DB provider returned message: The stored procedure required to
complete
> this operation could not be found on the server (they were supplied with
the
> ODBC setup disk for the SQL Server driver). Please contact your system
> administrator.]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
> returned 0x80004005: ]."
> do i miss something or i can using linked server in 64 bit edition?
>
> thanks,
> Suwito Kurniawan
>
Can I use Visual Studio 2005 to deploy a report to a SQL Server 2000 Reporting Services Ve
Can I use Visual Studio 2005 to deploy a report to a SQL Server 2000
Reporting Services Version 8.00.1038.00 server?Nope.
At that point it would be a RS 2005 report and a RS 2005 cannot be hosted in
RS 2000.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Andy" <andy.ritting@.gmail.com> wrote in message
news:1170433821.332059.216190@.k78g2000cwa.googlegroups.com...
> Can I use Visual Studio 2005 to deploy a report to a SQL Server 2000
> Reporting Services Version 8.00.1038.00 server?
>
Reporting Services Version 8.00.1038.00 server?Nope.
At that point it would be a RS 2005 report and a RS 2005 cannot be hosted in
RS 2000.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Andy" <andy.ritting@.gmail.com> wrote in message
news:1170433821.332059.216190@.k78g2000cwa.googlegroups.com...
> Can I use Visual Studio 2005 to deploy a report to a SQL Server 2000
> Reporting Services Version 8.00.1038.00 server?
>
Saturday, February 25, 2012
Can I use data drive subscription on a remote sql standard version
I would like to upgrade our report server to sql 2000 enterprise
edition to be able to use the DD subscriptions.. if I do do upgrade the
server, will I be able to connect to a sql server on another box with
the standard version and continue to use DD subscriptions on that
remote server.
or is there another way to get around this issue by way of stored
procedures.. thanks.What specifically do you mean by "continue to use DD susbscriptions no that
remote server"? Do you mean the remote server is the source of data that
drives the DD subscription? In that case, yes.
-Tim
"Joaquin" <joaquin.pineda@.gmail.com> wrote in message
news:1147897141.934976.263120@.38g2000cwa.googlegroups.com...
>I would like to upgrade our report server to sql 2000 enterprise
> edition to be able to use the DD subscriptions.. if I do do upgrade the
> server, will I be able to connect to a sql server on another box with
> the standard version and continue to use DD subscriptions on that
> remote server.
> or is there another way to get around this issue by way of stored
> procedures.. thanks.
>|||Tim Dot NoSpam wrote:
> What specifically do you mean by "continue to use DD susbscriptions no that
> remote server"? Do you mean the remote server is the source of data that
> drives the DD subscription? In that case, yes.
>
Tim, you got it, that's what I wanted to know. also, do you know if its
possible to simulate dd subscriptions, let say by way of stored proc?
on standard version of sql. thanks.
edition to be able to use the DD subscriptions.. if I do do upgrade the
server, will I be able to connect to a sql server on another box with
the standard version and continue to use DD subscriptions on that
remote server.
or is there another way to get around this issue by way of stored
procedures.. thanks.What specifically do you mean by "continue to use DD susbscriptions no that
remote server"? Do you mean the remote server is the source of data that
drives the DD subscription? In that case, yes.
-Tim
"Joaquin" <joaquin.pineda@.gmail.com> wrote in message
news:1147897141.934976.263120@.38g2000cwa.googlegroups.com...
>I would like to upgrade our report server to sql 2000 enterprise
> edition to be able to use the DD subscriptions.. if I do do upgrade the
> server, will I be able to connect to a sql server on another box with
> the standard version and continue to use DD subscriptions on that
> remote server.
> or is there another way to get around this issue by way of stored
> procedures.. thanks.
>|||Tim Dot NoSpam wrote:
> What specifically do you mean by "continue to use DD susbscriptions no that
> remote server"? Do you mean the remote server is the source of data that
> drives the DD subscription? In that case, yes.
>
Tim, you got it, that's what I wanted to know. also, do you know if its
possible to simulate dd subscriptions, let say by way of stored proc?
on standard version of sql. thanks.
Sunday, February 19, 2012
Can I run SQL2000Dev and SQL2005Exp Side By Side?
Have an asp.net 2.0 application that I want to enable a "demo" version of with the required tables. The tables currently exist in SQL2000Dev on a server. I have installed SQLEXP on a clean box and restored the database to it no problem. Now I want to install SQLEXP on my dev pc side-by-side with the SQLDEV instance. I could not find any reference to this ability other than some warnings about the pre-release versions. Can it be done safely?
Thanks, Paul
Absolutly. Install them to different instance names and it will work just fine.
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
Tuesday, February 14, 2012
Can I register my evaluation copy to full blown version using product key?
I installed the evaluation copy remotely and wish to register the product by entering its product key, would that possible since I don't have the cd in the box.
Matt
Unfortunately you cannot just enter the new product key. The upgrade in edition is treated as a product upgrade.
This blog should answer all your questions about this upgrade - http://blogs.msdn.com/sqlblog/archive/2006/09/17/upgrade-eval-edtion-to-full-blow-sql-2005-editions.aspx
Thanks,
Sam Lester (MSFT)
Sunday, February 12, 2012
Can I manage SQL Server 2000 with Mangement Studio Express 2005?
Hi Folks,
I'm new to the MS SQL Server world. Couple quick questions:
1) Can I use the current version of Mangement Studio Express (MSE) to
create/update/delete fields/tables on an existing SQL Server 2000?
2) How do I get connected over the 'Net? I have created an ODBC system
DSN which passes the connection test, but I don't see anywhere in MSE where
I can select from a list of system DSNs
3) If MSE is not the correct db administration client for SQL Server
2000, what is?
Your help is appreciated.
> 1) Can I use the current version of Mangement Studio Express (MSE) to
> create/update/delete fields/tables on an existing SQL Server 2000?
SQLMSE has the same "engine" (SMO) like the big brother. But there are
still some limitations:
http://msdn2.microsoft.com/en-us/library/ms365247.aspx
> 2) How do I get connected over the 'Net? I have created an ODBC syst=
em
> DSN which passes the connection test, but I don't see anywhere in MSE whe=
re
> I can select from a list of system DSNs
You don=B4t need DSNs. They should be wiped out DNSless connections. All
you need is a connecting string to the server, which will be created
behind the scenes after registring a server in the management Studio.
> 3) If MSE is not the correct db administration client for SQL Server
> 2000, what is?
Well, that depends. Depends on how much you want to achieve and want to
administer. make sure that the knockout limitations mentioned in 1)
will not affect your daily work.
HTH, Jens K. Suessmeyer,
http://www.sqlserver2005.de
I'm new to the MS SQL Server world. Couple quick questions:
1) Can I use the current version of Mangement Studio Express (MSE) to
create/update/delete fields/tables on an existing SQL Server 2000?
2) How do I get connected over the 'Net? I have created an ODBC system
DSN which passes the connection test, but I don't see anywhere in MSE where
I can select from a list of system DSNs
3) If MSE is not the correct db administration client for SQL Server
2000, what is?
Your help is appreciated.
> 1) Can I use the current version of Mangement Studio Express (MSE) to
> create/update/delete fields/tables on an existing SQL Server 2000?
SQLMSE has the same "engine" (SMO) like the big brother. But there are
still some limitations:
http://msdn2.microsoft.com/en-us/library/ms365247.aspx
> 2) How do I get connected over the 'Net? I have created an ODBC syst=
em
> DSN which passes the connection test, but I don't see anywhere in MSE whe=
re
> I can select from a list of system DSNs
You don=B4t need DSNs. They should be wiped out DNSless connections. All
you need is a connecting string to the server, which will be created
behind the scenes after registring a server in the management Studio.
> 3) If MSE is not the correct db administration client for SQL Server
> 2000, what is?
Well, that depends. Depends on how much you want to achieve and want to
administer. make sure that the knockout limitations mentioned in 1)
will not affect your daily work.
HTH, Jens K. Suessmeyer,
http://www.sqlserver2005.de
Can I manage SQL Server 2000 with Mangement Studio Express 2005?
Hi Folks,
I'm new to the MS SQL Server world. Couple quick questions:
1) Can I use the current version of Mangement Studio Express (MSE) to
create/update/delete fields/tables on an existing SQL Server 2000?
2) How do I get connected over the 'Net? I have created an ODBC system
DSN which passes the connection test, but I don't see anywhere in MSE where
I can select from a list of system DSNs
3) If MSE is not the correct db administration client for SQL Server
2000, what is?
Your help is appreciated.> 1) Can I use the current version of Mangement Studio Express (MSE) to
> create/update/delete fields/tables on an existing SQL Server 2000?
SQLMSE has the same "engine" (SMO) like the big brother. But there are
still some limitations:
http://msdn2.microsoft.com/en-us/library/ms365247.aspx
> 2) How do I get connected over the 'Net? I have created an ODBC syst=
em
> DSN which passes the connection test, but I don't see anywhere in MSE whe=
re
> I can select from a list of system DSNs
You don=B4t need DSNs. They should be wiped out DNSless connections. All
you need is a connecting string to the server, which will be created
behind the scenes after registring a server in the management Studio.
> 3) If MSE is not the correct db administration client for SQL Server
> 2000, what is?
Well, that depends. Depends on how much you want to achieve and want to
administer. make sure that the knockout limitations mentioned in 1)
will not affect your daily work.
HTH, Jens K. Suessmeyer,
http://www.sqlserver2005.de
--
I'm new to the MS SQL Server world. Couple quick questions:
1) Can I use the current version of Mangement Studio Express (MSE) to
create/update/delete fields/tables on an existing SQL Server 2000?
2) How do I get connected over the 'Net? I have created an ODBC system
DSN which passes the connection test, but I don't see anywhere in MSE where
I can select from a list of system DSNs
3) If MSE is not the correct db administration client for SQL Server
2000, what is?
Your help is appreciated.> 1) Can I use the current version of Mangement Studio Express (MSE) to
> create/update/delete fields/tables on an existing SQL Server 2000?
SQLMSE has the same "engine" (SMO) like the big brother. But there are
still some limitations:
http://msdn2.microsoft.com/en-us/library/ms365247.aspx
> 2) How do I get connected over the 'Net? I have created an ODBC syst=
em
> DSN which passes the connection test, but I don't see anywhere in MSE whe=
re
> I can select from a list of system DSNs
You don=B4t need DSNs. They should be wiped out DNSless connections. All
you need is a connecting string to the server, which will be created
behind the scenes after registring a server in the management Studio.
> 3) If MSE is not the correct db administration client for SQL Server
> 2000, what is?
Well, that depends. Depends on how much you want to achieve and want to
administer. make sure that the knockout limitations mentioned in 1)
will not affect your daily work.
HTH, Jens K. Suessmeyer,
http://www.sqlserver2005.de
--
Friday, February 10, 2012
Can I link to tables in an instance of MSDE from Access 2003?
I have a small program that linked to ACT! version 6 dbf files. I now have
ACT!7 SQL version. This uses MSDE. I need to link to the ACT! tables in the
MSDE instance. Any hints? ACT! technical help says I can not link. I
thought I would ask the real MSDE experts instead.
hi Scott,
Scott wrote:
> I have a small program that linked to ACT! version 6 dbf files. I
> now have ACT!7 SQL version. This uses MSDE. I need to link to the
> ACT! tables in the MSDE instance. Any hints? ACT! technical help
> says I can not link. I thought I would ask the real MSDE experts
> instead.
what do you mean by "link"?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Access/JET supports linked tables as does SQL Server itself. This is mostly
a matter of setting up the links from within Access. I have not done this in
years so I can't help with the current versions, but I don't see a reason
why it can't be done unless the ACT! database rights have been tuned to
prevent this.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:D75B4CED-FF49-4CFC-BAB6-DE4538CBF476@.microsoft.com...
>I have a small program that linked to ACT! version 6 dbf files. I now have
> ACT!7 SQL version. This uses MSDE. I need to link to the ACT! tables in
> the
> MSDE instance. Any hints? ACT! technical help says I can not link. I
> thought I would ask the real MSDE experts instead.
ACT!7 SQL version. This uses MSDE. I need to link to the ACT! tables in the
MSDE instance. Any hints? ACT! technical help says I can not link. I
thought I would ask the real MSDE experts instead.
hi Scott,
Scott wrote:
> I have a small program that linked to ACT! version 6 dbf files. I
> now have ACT!7 SQL version. This uses MSDE. I need to link to the
> ACT! tables in the MSDE instance. Any hints? ACT! technical help
> says I can not link. I thought I would ask the real MSDE experts
> instead.
what do you mean by "link"?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Access/JET supports linked tables as does SQL Server itself. This is mostly
a matter of setting up the links from within Access. I have not done this in
years so I can't help with the current versions, but I don't see a reason
why it can't be done unless the ACT! database rights have been tuned to
prevent this.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:D75B4CED-FF49-4CFC-BAB6-DE4538CBF476@.microsoft.com...
>I have a small program that linked to ACT! version 6 dbf files. I now have
> ACT!7 SQL version. This uses MSDE. I need to link to the ACT! tables in
> the
> MSDE instance. Any hints? ACT! technical help says I can not link. I
> thought I would ask the real MSDE experts instead.
Can I install SQL Server 2005 on machine which already have SQL Server 2000 ?
I need SQL server 2000 for one application and 2005 version for another.
Does SQL Server support multiple versions of software Install on the same windows server ?
Yes just install 2000 as a named instance, just make sure you have enough memory to keep all instances running. Hope this helps.|||thanks..
Can I install SQL Server 2005 on machine which already have SQL Server 2000 ?
|||Yep just make it a named instance, the 2005 installer is much better because Microsoft reads my posts about installation. You may not run into issues if you need to use Reporting services you must have IIS installed and configured, this is important because Win2003 comes with IIS not installed and when you install it, it comes locked down. So if you need Reporting services post again and I will walk you through IIS configurations you need. Hope this helps.|||Yeah its possible to install..If you installed sql2000 as default instance then you can install sql 2005 as named instance.
If you installed sql2000 as named instance then you can install sql 2005 as default instance.|||
Do you see any Microsoft paper or URLs about this kind of installation? Is it supported by Microsoft?
Also, can I have SQL 2000, SQL 2000 SP3, SQL 2000 SP4, SQL 2005 and SQL 7.0 on one server?
Thanks a lot.
Po-Shan.
MSN Messenger ID: poshanchang@.hotmail.com
Email: poshanchang@.yahoo.com
|||If you installed sql2000 as default instance then you can install sql 2005 as named instance.
If you installed sql2000 as named instance then you can install sql 2005 as default instance.
Good.Are you sure about this ?
|||Another Question:
What are changes we as DBA & Developer have to do when we migrate databases from default instance to Named Instance ?
Thanks
|||The only thing for developers is to change the connection string to point to the other instance, e.g. instead of Data Source=SomeServer it has to be Data Source=SomeServer\SomeInstanceName. Administrators have to (beside their normal work) make sure that the clients will reach the non default port (if configured as this) of the SQL Server service.Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Wondering why need different port numbers for each instance?
I thought the databases can be with the same port number, say 1433, and there could be many instances with this port on the same server, right?
As example,
SameServer\
SameServer\InstanceOne
SameServer\InstanceTwo
the three instances are all using 1433, right?
|||Yeah you can keep the default port for all the instances you install. By changing the port the app will easily detect its respective server and it will increase the security since hackers will first try for default port only.Can I install SQL Server 2000 on machine which already have SQL Server 2000 ?
I need SQL server 2000 for one application and 2005 version for another.
Does SQL Server support multiple versions of software Install on the same windows server ?
Yes just install 2000 as a named instance, just make sure you have enough memory to keep all instances running. Hope this helps.|||thanks..
Can I install SQL Server 2005 on machine which already have SQL Server 2000 ?
|||Yep just make it a named instance, the 2005 installer is much better because Microsoft reads my posts about installation. You may not run into issues if you need to use Reporting services you must have IIS installed and configured, this is important because Win2003 comes with IIS not installed and when you install it, it comes locked down. So if you need Reporting services post again and I will walk you through IIS configurations you need. Hope this helps.|||Yeah its possible to install..If you installed sql2000 as default instance then you can install sql 2005 as named instance.
If you installed sql2000 as named instance then you can install sql 2005 as default instance.|||
Do you see any Microsoft paper or URLs about this kind of installation? Is it supported by Microsoft?
Also, can I have SQL 2000, SQL 2000 SP3, SQL 2000 SP4, SQL 2005 and SQL 7.0 on one server?
Thanks a lot.
Po-Shan.
MSN Messenger ID: poshanchang@.hotmail.com
Email: poshanchang@.yahoo.com
|||If you installed sql2000 as default instance then you can install sql 2005 as named instance.
If you installed sql2000 as named instance then you can install sql 2005 as default instance.
Good.Are you sure about this ?
|||Another Question:
What are changes we as DBA & Developer have to do when we migrate databases from default instance to Named Instance ?
Thanks
|||The only thing for developers is to change the connection string to point to the other instance, e.g. instead of Data Source=SomeServer it has to be Data Source=SomeServer\SomeInstanceName. Administrators have to (beside their normal work) make sure that the clients will reach the non default port (if configured as this) of the SQL Server service.Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Wondering why need different port numbers for each instance?
I thought the databases can be with the same port number, say 1433, and there could be many instances with this port on the same server, right?
As example,
SameServer\
SameServer\InstanceOne
SameServer\InstanceTwo
the three instances are all using 1433, right?
|||Yeah you can keep the default port for all the instances you install. By changing the port the app will easily detect its respective server and it will increase the security since hackers will first try for default port only.Can I install SQL Server 2000 on machine which already have SQL Server 2000 ?
I need SQL server 2000 for one application and 2005 version for another.
Does SQL Server support multiple versions of software Install on the same windows server ?
Yes just install 2000 as a named instance, just make sure you have enough memory to keep all instances running. Hope this helps.|||thanks..
Can I install SQL Server 2005 on machine which already have SQL Server 2000 ?
|||Yep just make it a named instance, the 2005 installer is much better because Microsoft reads my posts about installation. You may not run into issues if you need to use Reporting services you must have IIS installed and configured, this is important because Win2003 comes with IIS not installed and when you install it, it comes locked down. So if you need Reporting services post again and I will walk you through IIS configurations you need. Hope this helps.|||Yeah its possible to install..If you installed sql2000 as default instance then you can install sql 2005 as named instance.
If you installed sql2000 as named instance then you can install sql 2005 as default instance.|||
Do you see any Microsoft paper or URLs about this kind of installation? Is it supported by Microsoft?
Also, can I have SQL 2000, SQL 2000 SP3, SQL 2000 SP4, SQL 2005 and SQL 7.0 on one server?
Thanks a lot.
Po-Shan.
MSN Messenger ID: poshanchang@.hotmail.com
Email: poshanchang@.yahoo.com
|||If you installed sql2000 as default instance then you can install sql 2005 as named instance.
If you installed sql2000 as named instance then you can install sql 2005 as default instance.
Good.Are you sure about this ?
|||Another Question:
What are changes we as DBA & Developer have to do when we migrate databases from default instance to Named Instance ?
Thanks
|||The only thing for developers is to change the connection string to point to the other instance, e.g. instead of Data Source=SomeServer it has to be Data Source=SomeServer\SomeInstanceName. Administrators have to (beside their normal work) make sure that the clients will reach the non default port (if configured as this) of the SQL Server service.Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Wondering why need different port numbers for each instance?
I thought the databases can be with the same port number, say 1433, and there could be many instances with this port on the same server, right?
As example,
SameServer\
SameServer\InstanceOne
SameServer\InstanceTwo
the three instances are all using 1433, right?
|||Yeah you can keep the default port for all the instances you install. By changing the port the app will easily detect its respective server and it will increase the security since hackers will first try for default port only.
Subscribe to:
Posts (Atom)