Runtime data source error

Hello

I have a defined data source to an oracle server. I've alredy intalled oracle client, and setup my data source to save the user and password. I'm using .NET provider/OracleClient DataProvider Connection. When I click on "Test Connection" Button, SSIS reports SUCCESS. In Connection Manager TAB I created on connection called "OracleServer" from my oracle data source, described above.

In my package, I defined a DataReaderSource task, I specified "OracleServer" as a connection to it. I can preview data and view oracle's columns name..., so it make me think that everything is fine. But when It execute the task it FAIL and notify logon error and that password can't be blank.

Please help, I need read from the oracle server!!

Thank you.

This may depend on the connection manager, the provider and your ProtectionLevel in the package. Check these.

One of them means you loose the password. If you don't know, between you clicking Execute in the designer and the package running, it is saved, and loaded into a separate execution host. The host then runs the package and passes back the debug messages to BIDS/VS to update the UI with pretty colours for you. So even though the password is there in your current BIDS/VS session, it is probably being lost on the save, prior to being loaded into the execution host. If you close the package in BIDS, and re-open do you still have the password? I would guess not, and this is the issue you see when trying to execute it.

You can play with the various settings, but my favoured approach is to set the package ProtectionLevel to DontSaveSensitive. This means no passwords are ever saved, but you then use a Configuration to set them. Going forward every time the package is loaded, by an execution host or the designer or other tool, it will read the configuration and apply the password or any other configuration you may have set. Problem solved! it may seem like hard work, but if you plan on deploying packages this is really got to be good practise.

|||

Hello,

When I close BIDS and reopen it, I can still see the password. However let me tell you that I already find the solution.

The problem was that my oracle server is 10.1.x and my oracle's drivers installed on SQL Server machine was 10.2.x. Only I unistalled these drivers and install 10.1 version and everything works!.

thanks for your advices.

Hernan.

Running the related program on the save server as the database

Hello Community
I have a question relating to the recommended setup of the sql server. We
use sage with sql backend, both running on the same server. we are
experiencing major performance degradation over the WAN but not on the LAN,
the sage support are blaming the network, i am blaming the server, as when we
reboot the server the performance picks up again over a period of 10 days the
performance dies.
I am asking of there are known issues running the program on the same server
as the database.
Regards
Andy
Andy
In general it is recomended to have a server dedicated to SQL Server only.
"Andy" <Andy@.discussions.microsoft.com> wrote in message
news:71F12DDD-D3D4-4274-AAFB-0AC850B4CC24@.microsoft.com...
> Hello Community
> I have a question relating to the recommended setup of the sql server. We
> use sage with sql backend, both running on the same server. we are
> experiencing major performance degradation over the WAN but not on the
> LAN,
> the sage support are blaming the network, i am blaming the server, as when
> we
> reboot the server the performance picks up again over a period of 10 days
> the
> performance dies.
> I am asking of there are known issues running the program on the same
> server
> as the database.
> Regards
> Andy
|||If you are seeing poor performance over the WAN at the same time the LAN is
performing adequately then Sage is probably correct that you have a network
issue.
As far as running SQL and the application on the same server... I know the
*recommended* practice is to dedicate a server to SQL, but realistically
that costs $$$. As long as the two applications are not bumping into each
other and causing memory, disk, or processor contention then they should be
ok on the same server. The only way to tell is to fire up perfmon and let
it run for a while and see if your server is running short on anything.
"Andy" <Andy@.discussions.microsoft.com> wrote in message
news:71F12DDD-D3D4-4274-AAFB-0AC850B4CC24@.microsoft.com...
> Hello Community
> I have a question relating to the recommended setup of the sql server. We
> use sage with sql backend, both running on the same server. we are
> experiencing major performance degradation over the WAN but not on the
> LAN,
> the sage support are blaming the network, i am blaming the server, as when
> we
> reboot the server the performance picks up again over a period of 10 days
> the
> performance dies.
> I am asking of there are known issues running the program on the same
> server
> as the database.
> Regards
> Andy
sql

Running the related program on the save server as the database

Hello Community
I have a question relating to the recommended setup of the sql server. We
use sage with sql backend, both running on the same server. we are
experiencing major performance degradation over the WAN but not on the LAN,
the sage support are blaming the network, i am blaming the server, as when we
reboot the server the performance picks up again over a period of 10 days the
performance dies.
I am asking of there are known issues running the program on the same server
as the database.
Regards
AndyAndy
In general it is recomended to have a server dedicated to SQL Server only.
"Andy" <Andy@.discussions.microsoft.com> wrote in message
news:71F12DDD-D3D4-4274-AAFB-0AC850B4CC24@.microsoft.com...
> Hello Community
> I have a question relating to the recommended setup of the sql server. We
> use sage with sql backend, both running on the same server. we are
> experiencing major performance degradation over the WAN but not on the
> LAN,
> the sage support are blaming the network, i am blaming the server, as when
> we
> reboot the server the performance picks up again over a period of 10 days
> the
> performance dies.
> I am asking of there are known issues running the program on the same
> server
> as the database.
> Regards
> Andy|||If you are seeing poor performance over the WAN at the same time the LAN is
performing adequately then Sage is probably correct that you have a network
issue.
As far as running SQL and the application on the same server... I know the
*recommended* practice is to dedicate a server to SQL, but realistically
that costs $$$. As long as the two applications are not bumping into each
other and causing memory, disk, or processor contention then they should be
ok on the same server. The only way to tell is to fire up perfmon and let
it run for a while and see if your server is running short on anything.
"Andy" <Andy@.discussions.microsoft.com> wrote in message
news:71F12DDD-D3D4-4274-AAFB-0AC850B4CC24@.microsoft.com...
> Hello Community
> I have a question relating to the recommended setup of the sql server. We
> use sage with sql backend, both running on the same server. we are
> experiencing major performance degradation over the WAN but not on the
> LAN,
> the sage support are blaming the network, i am blaming the server, as when
> we
> reboot the server the performance picks up again over a period of 10 days
> the
> performance dies.
> I am asking of there are known issues running the program on the same
> server
> as the database.
> Regards
> Andy

Running the related program on the save server as the database

Hello Community
I have a question relating to the recommended setup of the sql server. We
use sage with sql backend, both running on the same server. we are
experiencing major performance degradation over the WAN but not on the LAN,
the sage support are blaming the network, i am blaming the server, as when w
e
reboot the server the performance picks up again over a period of 10 days th
e
performance dies.
I am asking of there are known issues running the program on the same server
as the database.
Regards
AndyAndy
In general it is recomended to have a server dedicated to SQL Server only.
"Andy" <Andy@.discussions.microsoft.com> wrote in message
news:71F12DDD-D3D4-4274-AAFB-0AC850B4CC24@.microsoft.com...
> Hello Community
> I have a question relating to the recommended setup of the sql server. We
> use sage with sql backend, both running on the same server. we are
> experiencing major performance degradation over the WAN but not on the
> LAN,
> the sage support are blaming the network, i am blaming the server, as when
> we
> reboot the server the performance picks up again over a period of 10 days
> the
> performance dies.
> I am asking of there are known issues running the program on the same
> server
> as the database.
> Regards
> Andy|||If you are seeing poor performance over the WAN at the same time the LAN is
performing adequately then Sage is probably correct that you have a network
issue.
As far as running SQL and the application on the same server... I know the
*recommended* practice is to dedicate a server to SQL, but realistically
that costs $$$. As long as the two applications are not bumping into each
other and causing memory, disk, or processor contention then they should be
ok on the same server. The only way to tell is to fire up perfmon and let
it run for a while and see if your server is running short on anything.
"Andy" <Andy@.discussions.microsoft.com> wrote in message
news:71F12DDD-D3D4-4274-AAFB-0AC850B4CC24@.microsoft.com...
> Hello Community
> I have a question relating to the recommended setup of the sql server. We
> use sage with sql backend, both running on the same server. we are
> experiencing major performance degradation over the WAN but not on the
> LAN,
> the sage support are blaming the network, i am blaming the server, as when
> we
> reboot the server the performance picks up again over a period of 10 days
> the
> performance dies.
> I am asking of there are known issues running the program on the same
> server
> as the database.
> Regards
> Andy

Running SQL Server 2005 EE on Dual-Core CPU

Hello!
We are planning following setup for our production SQL Server:
OS - Windows 2003 Enterprise Edition
SQL Server 2005 Enterprise Edition
16 GB RAM
4 Dual-Core CPUs 64 bit
I was wondering if anybody is running SQL Server 2005 on Dual-Core 64
bit CPUs. Are there any know issues with this? Would it be better to with
Intel or AMD?
Thank you in advance,
Igor
Hi
We are running SQL Server 2000 on HP 585's, 4 AMD Dual cores. We are very
happy with the performance.
Still awaiting the Intel Dual Core range, so no comparison yet.
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/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23v5j5%23R$FHA.3104@.TK2MSFTNGP15.phx.gbl...
> Hello!
> We are planning following setup for our production SQL Server:
> OS - Windows 2003 Enterprise Edition
> SQL Server 2005 Enterprise Edition
> 16 GB RAM
> 4 Dual-Core CPUs 64 bit
> I was wondering if anybody is running SQL Server 2005 on Dual-Core 64
> bit CPUs. Are there any know issues with this? Would it be better to with
> Intel or AMD?
> Thank you in advance,
> Igor
>
|||I haven't seen any Intel dual cores yet but I have seen several AMD dual
core servers and they work very well. From what I have heard the Intel
units will be a little faster than the AMD's but I don't know if that is
worth waiting for or not.
Andrew J. Kelly SQL MVP
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23v5j5%23R$FHA.3104@.TK2MSFTNGP15.phx.gbl...
> Hello!
> We are planning following setup for our production SQL Server:
> OS - Windows 2003 Enterprise Edition
> SQL Server 2005 Enterprise Edition
> 16 GB RAM
> 4 Dual-Core CPUs 64 bit
> I was wondering if anybody is running SQL Server 2005 on Dual-Core 64
> bit CPUs. Are there any know issues with this? Would it be better to with
> Intel or AMD?
> Thank you in advance,
> Igor
>
|||Mike,
Thanks a lot for your feedback. Since we are planning to run SQL 2005 on
our production env., it is critical for us to know whether SQL 2005/Dual
core CPU is stable enough configuration.
Igor
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:u$js9ES$FHA.3804@.TK2MSFTNGP14.phx.gbl...
> Hi
> We are running SQL Server 2000 on HP 585's, 4 AMD Dual cores. We are very
> happy with the performance.
> Still awaiting the Intel Dual Core range, so no comparison yet.
> 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/
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23v5j5%23R$FHA.3104@.TK2MSFTNGP15.phx.gbl...
>
|||Thanks, Andrew. Would you happen to know if anyone is running SQL 2005/ Dual
core CPU configuration? Is this a stable enough environment?
Igor
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23pR7nOU$FHA.3908@.TK2MSFTNGP10.phx.gbl...
>I haven't seen any Intel dual cores yet but I have seen several AMD dual
>core servers and they work very well. From what I have heard the Intel
>units will be a little faster than the AMD's but I don't know if that is
>worth waiting for or not.
> --
> Andrew J. Kelly SQL MVP
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23v5j5%23R$FHA.3104@.TK2MSFTNGP15.phx.gbl...
>
|||"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:ekH$VRb$FHA.328@.TK2MSFTNGP14.phx.gbl...
> Mike,
> Thanks a lot for your feedback. Since we are planning to run SQL 2005
> on our production env., it is critical for us to know whether SQL
> 2005/Dual core CPU is stable enough configuration.
>
IMO Multi-Core x64 with 2 or 4 sockets is the basic hardware platform for
SQL Server 2005.
Talk to Dell or HP. The Dell PowerEdge 6850 and the HP DL580 or DL585 meet
your specs, and either one of them can help put your mind at ease about
running 64-bit Windows and 64-bit SQL Server 2005 in production.
David
|||I have seen both with no problems on either that I know of.
Andrew J. Kelly SQL MVP
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23xldESb$FHA.1288@.TK2MSFTNGP09.phx.gbl...
> Thanks, Andrew. Would you happen to know if anyone is running SQL 2005/
> Dual core CPU configuration? Is this a stable enough environment?
>
> Igor
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:%23pR7nOU$FHA.3908@.TK2MSFTNGP10.phx.gbl...
>

Running SQL Server 2005 EE on Dual-Core CPU

Hello!
We are planning following setup for our production SQL Server:
OS - Windows 2003 Enterprise Edition
SQL Server 2005 Enterprise Edition
16 GB RAM
4 Dual-Core CPUs 64 bit
I was wondering if anybody is running SQL Server 2005 on Dual-Core 64
bit CPUs. Are there any know issues with this? Would it be better to with
Intel or AMD?
Thank you in advance,
IgorHi
We are running SQL Server 2000 on HP 585's, 4 AMD Dual cores. We are very
happy with the performance.
Still awaiting the Intel Dual Core range, so no comparison yet.
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/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23v5j5%23R$FHA.3104@.TK2MSFTNGP15.phx.gbl...
> Hello!
> We are planning following setup for our production SQL Server:
> OS - Windows 2003 Enterprise Edition
> SQL Server 2005 Enterprise Edition
> 16 GB RAM
> 4 Dual-Core CPUs 64 bit
> I was wondering if anybody is running SQL Server 2005 on Dual-Core 64
> bit CPUs. Are there any know issues with this? Would it be better to with
> Intel or AMD?
> Thank you in advance,
> Igor
>|||I haven't seen any Intel dual cores yet but I have seen several AMD dual
core servers and they work very well. From what I have heard the Intel
units will be a little faster than the AMD's but I don't know if that is
worth waiting for or not.
--
Andrew J. Kelly SQL MVP
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23v5j5%23R$FHA.3104@.TK2MSFTNGP15.phx.gbl...
> Hello!
> We are planning following setup for our production SQL Server:
> OS - Windows 2003 Enterprise Edition
> SQL Server 2005 Enterprise Edition
> 16 GB RAM
> 4 Dual-Core CPUs 64 bit
> I was wondering if anybody is running SQL Server 2005 on Dual-Core 64
> bit CPUs. Are there any know issues with this? Would it be better to with
> Intel or AMD?
> Thank you in advance,
> Igor
>|||Mike,
Thanks a lot for your feedback. Since we are planning to run SQL 2005 on
our production env., it is critical for us to know whether SQL 2005/Dual
core CPU is stable enough configuration.
Igor
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:u$js9ES$FHA.3804@.TK2MSFTNGP14.phx.gbl...
> Hi
> We are running SQL Server 2000 on HP 585's, 4 AMD Dual cores. We are very
> happy with the performance.
> Still awaiting the Intel Dual Core range, so no comparison yet.
> 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/
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23v5j5%23R$FHA.3104@.TK2MSFTNGP15.phx.gbl...
>> Hello!
>> We are planning following setup for our production SQL Server:
>> OS - Windows 2003 Enterprise Edition
>> SQL Server 2005 Enterprise Edition
>> 16 GB RAM
>> 4 Dual-Core CPUs 64 bit
>> I was wondering if anybody is running SQL Server 2005 on Dual-Core 64
>> bit CPUs. Are there any know issues with this? Would it be better to
>> with Intel or AMD?
>> Thank you in advance,
>> Igor
>|||Thanks, Andrew. Would you happen to know if anyone is running SQL 2005/ Dual
core CPU configuration? Is this a stable enough environment?
Igor
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23pR7nOU$FHA.3908@.TK2MSFTNGP10.phx.gbl...
>I haven't seen any Intel dual cores yet but I have seen several AMD dual
>core servers and they work very well. From what I have heard the Intel
>units will be a little faster than the AMD's but I don't know if that is
>worth waiting for or not.
> --
> Andrew J. Kelly SQL MVP
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23v5j5%23R$FHA.3104@.TK2MSFTNGP15.phx.gbl...
>> Hello!
>> We are planning following setup for our production SQL Server:
>> OS - Windows 2003 Enterprise Edition
>> SQL Server 2005 Enterprise Edition
>> 16 GB RAM
>> 4 Dual-Core CPUs 64 bit
>> I was wondering if anybody is running SQL Server 2005 on Dual-Core 64
>> bit CPUs. Are there any know issues with this? Would it be better to
>> with Intel or AMD?
>> Thank you in advance,
>> Igor
>|||"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:ekH$VRb$FHA.328@.TK2MSFTNGP14.phx.gbl...
> Mike,
> Thanks a lot for your feedback. Since we are planning to run SQL 2005
> on our production env., it is critical for us to know whether SQL
> 2005/Dual core CPU is stable enough configuration.
>
IMO Multi-Core x64 with 2 or 4 sockets is the basic hardware platform for
SQL Server 2005.
Talk to Dell or HP. The Dell PowerEdge 6850 and the HP DL580 or DL585 meet
your specs, and either one of them can help put your mind at ease about
running 64-bit Windows and 64-bit SQL Server 2005 in production.
David|||I have seen both with no problems on either that I know of.
--
Andrew J. Kelly SQL MVP
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23xldESb$FHA.1288@.TK2MSFTNGP09.phx.gbl...
> Thanks, Andrew. Would you happen to know if anyone is running SQL 2005/
> Dual core CPU configuration? Is this a stable enough environment?
>
> Igor
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:%23pR7nOU$FHA.3908@.TK2MSFTNGP10.phx.gbl...
>>I haven't seen any Intel dual cores yet but I have seen several AMD dual
>>core servers and they work very well. From what I have heard the Intel
>>units will be a little faster than the AMD's but I don't know if that is
>>worth waiting for or not.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
>> news:%23v5j5%23R$FHA.3104@.TK2MSFTNGP15.phx.gbl...
>> Hello!
>> We are planning following setup for our production SQL Server:
>> OS - Windows 2003 Enterprise Edition
>> SQL Server 2005 Enterprise Edition
>> 16 GB RAM
>> 4 Dual-Core CPUs 64 bit
>> I was wondering if anybody is running SQL Server 2005 on Dual-Core 64
>> bit CPUs. Are there any know issues with this? Would it be better to
>> with Intel or AMD?
>> Thank you in advance,
>> Igor
>>
>

Running SQL Server 2005 EE on Dual-Core CPU

Hello!
We are planning following setup for our production SQL Server:
OS - Windows 2003 Enterprise Edition
SQL Server 2005 Enterprise Edition
16 GB RAM
4 Dual-Core CPUs 64 bit
I was wondering if anybody is running SQL Server 2005 on Dual-Core 64
bit CPUs. Are there any know issues with this? Would it be better to with
Intel or AMD?
Thank you in advance,
IgorHi
We are running SQL Server 2000 on HP 585's, 4 AMD Dual cores. We are very
happy with the performance.
Still awaiting the Intel Dual Core range, so no comparison yet.
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/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23v5j5%23R$FHA.3104@.TK2MSFTNGP15.phx.gbl...
> Hello!
> We are planning following setup for our production SQL Server:
> OS - Windows 2003 Enterprise Edition
> SQL Server 2005 Enterprise Edition
> 16 GB RAM
> 4 Dual-Core CPUs 64 bit
> I was wondering if anybody is running SQL Server 2005 on Dual-Core 64
> bit CPUs. Are there any know issues with this? Would it be better to with
> Intel or AMD?
> Thank you in advance,
> Igor
>|||I haven't seen any Intel dual cores yet but I have seen several AMD dual
core servers and they work very well. From what I have heard the Intel
units will be a little faster than the AMD's but I don't know if that is
worth waiting for or not.
Andrew J. Kelly SQL MVP
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23v5j5%23R$FHA.3104@.TK2MSFTNGP15.phx.gbl...
> Hello!
> We are planning following setup for our production SQL Server:
> OS - Windows 2003 Enterprise Edition
> SQL Server 2005 Enterprise Edition
> 16 GB RAM
> 4 Dual-Core CPUs 64 bit
> I was wondering if anybody is running SQL Server 2005 on Dual-Core 64
> bit CPUs. Are there any know issues with this? Would it be better to with
> Intel or AMD?
> Thank you in advance,
> Igor
>|||Mike,
Thanks a lot for your feedback. Since we are planning to run SQL 2005 on
our production env., it is critical for us to know whether SQL 2005/Dual
core CPU is stable enough configuration.
Igor
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:u$js9ES$FHA.3804@.TK2MSFTNGP14.phx.gbl...
> Hi
> We are running SQL Server 2000 on HP 585's, 4 AMD Dual cores. We are very
> happy with the performance.
> Still awaiting the Intel Dual Core range, so no comparison yet.
> 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/
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23v5j5%23R$FHA.3104@.TK2MSFTNGP15.phx.gbl...
>|||Thanks, Andrew. Would you happen to know if anyone is running SQL 2005/ Dual
core CPU configuration? Is this a stable enough environment?
Igor
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23pR7nOU$FHA.3908@.TK2MSFTNGP10.phx.gbl...
>I haven't seen any Intel dual cores yet but I have seen several AMD dual
>core servers and they work very well. From what I have heard the Intel
>units will be a little faster than the AMD's but I don't know if that is
>worth waiting for or not.
> --
> Andrew J. Kelly SQL MVP
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23v5j5%23R$FHA.3104@.TK2MSFTNGP15.phx.gbl...
>|||"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:ekH$VRb$FHA.328@.TK2MSFTNGP14.phx.gbl...
> Mike,
> Thanks a lot for your feedback. Since we are planning to run SQL 2005
> on our production env., it is critical for us to know whether SQL
> 2005/Dual core CPU is stable enough configuration.
>
IMO Multi-Core x64 with 2 or 4 sockets is the basic hardware platform for
SQL Server 2005.
Talk to Dell or HP. The Dell PowerEdge 6850 and the HP DL580 or DL585 meet
your specs, and either one of them can help put your mind at ease about
running 64-bit Windows and 64-bit SQL Server 2005 in production.
David|||I have seen both with no problems on either that I know of.
Andrew J. Kelly SQL MVP
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23xldESb$FHA.1288@.TK2MSFTNGP09.phx.gbl...
> Thanks, Andrew. Would you happen to know if anyone is running SQL 2005/
> Dual core CPU configuration? Is this a stable enough environment?
>
> Igor
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:%23pR7nOU$FHA.3908@.TK2MSFTNGP10.phx.gbl...
>

Running sql script from Setup deployment .NET

Posted - 04/21/2004 : 09:26:34
----
--
Friends
I want to run sql script for creating of database which
contains tables and stored procedures by setup and deployment project
in VS.NET. I have created customaction and passing the string
containing script to the ExecuteNonQuery() procedure to run the script
The problem is where ever GO statement is there in the script it
is giving problem. I read somewhere that
" Your script must not include any go statements. These are used only by Que
ry Analyzer or the osql.exe utility. If they are present in your script when
using it with ADO.NET (as in this demo), then the ExecuteNonQuery will fail
."
If i remove Go from the script then it is giving exception again
telling that "Incorrect syntax near the keyword Procedure"
where ever create Procedure statement is there
Please help me in this regard.Sudhapec,
from BOL: CREATE DEFAULT, CREATE PROCEDURE, CREATE RULE, CREATE TRIGGER, and
CREATE VIEW statements cannot be combined with other statements in a batch.
Batches are delimited by the keyword GO in a script, hence your problem. I
guess you could create mult
iple scripts - one main one and a separate script for each of the above comm
ands. Another (easier) alternative would be to not use ADO.NET for this step
, but OSQL. You could have a batch file which runs osql with your complete s
cript.
HTH,
Paul Ibison|||Or, read the script, line by line, and each time you encounter GO, execute w
hat you have in the buffer.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:8781168A-8324-4DE5-ACDA-C975D4B21EEF@.microsoft.com...
> Sudhapec,
> from BOL: CREATE DEFAULT, CREATE PROCEDURE, CREATE RULE, CREATE TRIGGER, and CREAT
E VIEW statements cannot
be combined with other statements in a batch. Batches are delimited by the k
eyword GO in a script, hence your
problem. I guess you could create multiple scripts - one main one and a sepa
rate script for each of the above
commands. Another (easier) alternative would be to not use ADO.NET for this
step, but OSQL. You could have a
batch file which runs osql with your complete script.
> HTH,
> Paul Ibison|||Below a link to a VB.Net code example that uses the technique Tibor
mentioned:
<http://groups.google.com/groups?hl=...threadm=mK%252c
.2084%24Cm3.67%40newsread3.news.pas.earthlink.net&rnum=8&prev=/groups%3Fas_
q
%3Dsqlcommand%2520go%26safe%3Dimages%26i
e%3DUTF-8%26oe%3DUTF-8%26as_uauthors
%3DDan%2520Guzman%26lr%3D%26hl%3Den>
Hope this helps.
Dan Guzman
SQL Server MVP
"sudhapec" <sudhapec.153vii@.mail.webservertalk.com> wrote in message
news:sudhapec.153vii@.mail.webservertalk.com...
> Posted - 04/21/2004 : 09:26:34
> ----
--
> Friends
> I want to run sql script for creating of database which
> contains tables and stored procedures by setup and deployment project
> in VS.NET. I have created customaction and passing the string
> containing script to the ExecuteNonQuery() procedure to run the script
> The problem is where ever GO statement is there in the script it
> is giving problem. I read somewhere that
> " Your script must not include any go statements. These are used only
> by Query Analyzer or the osql.exe utility. If they are present in your
> script when using it with ADO.NET (as in this demo), then the
> ExecuteNonQuery will fail."
> If i remove Go from the script then it is giving exception again
> telling that "Incorrect syntax near the keyword Procedure"
> where ever create Procedure statement is there
> Please help me in this regard.
>
> --
> sudhapec
> ---
> Posted via http://www.webservertalk.com
> ---
> View this thread: http://www.webservertalk.com/message190433.html
>

Running sql script from Setup deployment .NET

Posted - 04/21/2004 : 09:26:34
Friends
I want to run sql script for creating of database which
contains tables and stored procedures by setup and deployment project
in VS.NET. I have created customaction and passing the string
containing script to the ExecuteNonQuery() procedure to run the script
The problem is where ever GO statement is there in the script it
is giving problem. I read somewhere that
" Your script must not include any go statements. These are used only
by Query Analyzer or the osql.exe utility. If they are present in your
script when using it with ADO.NET (as in this demo), then the
ExecuteNonQuery will fail."
If i remove Go from the script then it is giving exception again
telling that "Incorrect syntax near the keyword Procedure"
where ever create Procedure statement is there
Please help me in this regard.
sudhapec
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message190433.html
Sudhapec,
from BOL: CREATE DEFAULT, CREATE PROCEDURE, CREATE RULE, CREATE TRIGGER, and CREATE VIEW statements cannot be combined with other statements in a batch. Batches are delimited by the keyword GO in a script, hence your problem. I guess you could create mult
iple scripts - one main one and a separate script for each of the above commands. Another (easier) alternative would be to not use ADO.NET for this step, but OSQL. You could have a batch file which runs osql with your complete script.
HTH,
Paul Ibison
|||Or, read the script, line by line, and each time you encounter GO, execute what you have in the buffer.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:8781168A-8324-4DE5-ACDA-C975D4B21EEF@.microsoft.com...
> Sudhapec,
> from BOL: CREATE DEFAULT, CREATE PROCEDURE, CREATE RULE, CREATE TRIGGER, and CREATE VIEW statements cannot
be combined with other statements in a batch. Batches are delimited by the keyword GO in a script, hence your
problem. I guess you could create multiple scripts - one main one and a separate script for each of the above
commands. Another (easier) alternative would be to not use ADO.NET for this step, but OSQL. You could have a
batch file which runs osql with your complete script.
> HTH,
> Paul Ibison
|||Below a link to a VB.Net code example that uses the technique Tibor
mentioned:
<http://groups.google.com/groups?hl=e...hreadm=mK%252c
..2084%24Cm3.67%40newsread3.news.pas.earthlink.net &rnum=8&prev=/groups%3Fas_q
%3Dsqlcommand%2520go%26safe%3Dimages%26ie%3DUTF-8%26oe%3DUTF-8%26as_uauthors
%3DDan%2520Guzman%26lr%3D%26hl%3Den>
Hope this helps.
Dan Guzman
SQL Server MVP
"sudhapec" <sudhapec.153vii@.mail.webservertalk.com> wrote in message
news:sudhapec.153vii@.mail.webservertalk.com...
> Posted - 04/21/2004 : 09:26:34
> ----
--
> Friends
> I want to run sql script for creating of database which
> contains tables and stored procedures by setup and deployment project
> in VS.NET. I have created customaction and passing the string
> containing script to the ExecuteNonQuery() procedure to run the script
> The problem is where ever GO statement is there in the script it
> is giving problem. I read somewhere that
> " Your script must not include any go statements. These are used only
> by Query Analyzer or the osql.exe utility. If they are present in your
> script when using it with ADO.NET (as in this demo), then the
> ExecuteNonQuery will fail."
> If i remove Go from the script then it is giving exception again
> telling that "Incorrect syntax near the keyword Procedure"
> where ever create Procedure statement is there
> Please help me in this regard.
>
> --
> sudhapec
> Posted via http://www.webservertalk.com
> View this thread: http://www.webservertalk.com/message190433.html
>

Running sql script from Setup deployment .NET

Posted - 04/21/2004 : 09:26:34
----
Friends
I want to run sql script for creating of database which
contains tables and stored procedures by setup and deployment project
in VS.NET. I have created customaction and passing the string
containing script to the ExecuteNonQuery() procedure to run the script
The problem is where ever GO statement is there in the script it
is giving problem. I read somewhere that
" Your script must not include any go statements. These are used onl
by Query Analyzer or the osql.exe utility. If they are present in you
script when using it with ADO.NET (as in this demo), then th
ExecuteNonQuery will fail."
If i remove Go from the script then it is giving exception again
telling that "Incorrect syntax near the keyword Procedure"
where ever create Procedure statement is there
Please help me in this regard
-
sudhape
----
Posted via http://www.webservertalk.co
----
View this thread: http://www.webservertalk.com/message190433.htmSudhapec
from BOL: CREATE DEFAULT, CREATE PROCEDURE, CREATE RULE, CREATE TRIGGER, and CREATE VIEW statements cannot be combined with other statements in a batch. Batches are delimited by the keyword GO in a script, hence your problem. I guess you could create multiple scripts - one main one and a separate script for each of the above commands. Another (easier) alternative would be to not use ADO.NET for this step, but OSQL. You could have a batch file which runs osql with your complete script
HTH
Paul Ibison|||Or, read the script, line by line, and each time you encounter GO, execute what you have in the buffer.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:8781168A-8324-4DE5-ACDA-C975D4B21EEF@.microsoft.com...
> Sudhapec,
> from BOL: CREATE DEFAULT, CREATE PROCEDURE, CREATE RULE, CREATE TRIGGER, and CREATE VIEW statements cannot
be combined with other statements in a batch. Batches are delimited by the keyword GO in a script, hence your
problem. I guess you could create multiple scripts - one main one and a separate script for each of the above
commands. Another (easier) alternative would be to not use ADO.NET for this step, but OSQL. You could have a
batch file which runs osql with your complete script.
> HTH,
> Paul Ibison|||Below a link to a VB.Net code example that uses the technique Tibor
mentioned:
<http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=mK%252c
.2084%24Cm3.67%40newsread3.news.pas.earthlink.net&rnum=8&prev=/groups%3Fas_q
%3Dsqlcommand%2520go%26safe%3Dimages%26ie%3DUTF-8%26oe%3DUTF-8%26as_uauthors
%3DDan%2520Guzman%26lr%3D%26hl%3Den>
--
Hope this helps.
Dan Guzman
SQL Server MVP
"sudhapec" <sudhapec.153vii@.mail.webservertalk.com> wrote in message
news:sudhapec.153vii@.mail.webservertalk.com...
> Posted - 04/21/2004 : 09:26:34
> ----
--
> Friends
> I want to run sql script for creating of database which
> contains tables and stored procedures by setup and deployment project
> in VS.NET. I have created customaction and passing the string
> containing script to the ExecuteNonQuery() procedure to run the script
> The problem is where ever GO statement is there in the script it
> is giving problem. I read somewhere that
> " Your script must not include any go statements. These are used only
> by Query Analyzer or the osql.exe utility. If they are present in your
> script when using it with ADO.NET (as in this demo), then the
> ExecuteNonQuery will fail."
> If i remove Go from the script then it is giving exception again
> telling that "Incorrect syntax near the keyword Procedure"
> where ever create Procedure statement is there
> Please help me in this regard.
>
> --
> sudhapec
> ---
> Posted via http://www.webservertalk.com
> ---
> View this thread: http://www.webservertalk.com/message190433.html
>