I had my IT dept. install sql server 2005 enterprise edition on a new windows server 2003. All other machines are running sql 2000 server on windows server 2000. I am a sa and local admin on all servers. I tried performing copy database, backup and restore and detach and attach to upgrade the sql server 2000 databases to 2005 and all fail. They also installed sql server 2005 sp2. I followed all steps. It's like the servers dont talk to each other. Their all on the company's domain. I am wondering if something happen with the install but the IT dept. insist that everything went fine. It's strange that I can't perform a simple backup and restore it on the new server buy when I click on restore it doesn't let me browse to get the backup file on the 2000 server. I never had a problem in Sql 2000 with backup. Can it be the installation was corrupted somehow. It seems fine. I haven't created any new databases because I wanted to move the databases from sql 2000. Can anyone help me get a clue of what the problem is please?
ThanksSounds like the service account for the SQL Server 2005 service has no network rights. Try copying the backup file locally, then doing the restore.
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Friday, March 30, 2012
Friday, March 23, 2012
running 32bit standard edition on 64bit hardware?
I just found out that the hardware that came uses 64bit AMD. But the
Windows Server 2003 license is for Standard Edition; a 32bit version.
What kind of performance hit would I take if I ran the Standard Edition
on the 64bit hardware?
Thanks,
Mark.None.
If you install the 64 bit OS, your executables will be a bit larger and
yoyu'll use a bit more memory. But then, you can install way more memory :)
"Mark" <murkynow50@.yahoo.com> wrote in message
news:OreRLT8%23HHA.4184@.TK2MSFTNGP05.phx.gbl...
>I just found out that the hardware that came uses 64bit AMD. But the
>Windows Server 2003 license is for Standard Edition; a 32bit version.
> What kind of performance hit would I take if I ran the Standard Edition on
> the 64bit hardware?
> Thanks,
> Mark.|||Mark wrote:
> I just found out that the hardware that came uses 64bit AMD. But the
> Windows Server 2003 license is for Standard Edition; a 32bit version.
> What kind of performance hit would I take if I ran the Standard Edition
> on the 64bit hardware?
> Thanks,
> Mark.
Sorry about this posting. I meant to post it in the windows section.
Mark.
Windows Server 2003 license is for Standard Edition; a 32bit version.
What kind of performance hit would I take if I ran the Standard Edition
on the 64bit hardware?
Thanks,
Mark.None.
If you install the 64 bit OS, your executables will be a bit larger and
yoyu'll use a bit more memory. But then, you can install way more memory :)
"Mark" <murkynow50@.yahoo.com> wrote in message
news:OreRLT8%23HHA.4184@.TK2MSFTNGP05.phx.gbl...
>I just found out that the hardware that came uses 64bit AMD. But the
>Windows Server 2003 license is for Standard Edition; a 32bit version.
> What kind of performance hit would I take if I ran the Standard Edition on
> the 64bit hardware?
> Thanks,
> Mark.|||Mark wrote:
> I just found out that the hardware that came uses 64bit AMD. But the
> Windows Server 2003 license is for Standard Edition; a 32bit version.
> What kind of performance hit would I take if I ran the Standard Edition
> on the 64bit hardware?
> Thanks,
> Mark.
Sorry about this posting. I meant to post it in the windows section.
Mark.
running .sql script from command line
how do I run a file with an .sql extension from the command window in windows 2k server?
Hi,
Use OSQL utility from command prompt
OSQL -SSERVER_NAME -Uuser -Ppassword -d db_name -i file_name.sql -o
output.log
Thanks
Hari
MCDBA
"joel" <anonymous@.discussions.microsoft.com> wrote in message
news:0FB9BC49-83D4-416D-889C-00A024A07079@.microsoft.com...
> how do I run a file with an .sql extension from the command window in
windows 2k server?
Hi,
Use OSQL utility from command prompt
OSQL -SSERVER_NAME -Uuser -Ppassword -d db_name -i file_name.sql -o
output.log
Thanks
Hari
MCDBA
"joel" <anonymous@.discussions.microsoft.com> wrote in message
news:0FB9BC49-83D4-416D-889C-00A024A07079@.microsoft.com...
> how do I run a file with an .sql extension from the command window in
windows 2k server?
Wednesday, March 21, 2012
Run time jobs
A job is created to fetch data from source server and populate the
destination server. This job has the owner as windows authentication(user
account). This main job inturn creates sub jobs with owner as sa.
when i run the sub jobs from query analyser it works fine. But when ran from
sql server agent/jobs it is failing with the following error.
Msg 18456, Sev 14: Login failed for user 'CHNDomain\CHNSHL23456$'. [SQLS
TATE
28000]
Msg 7312, Sev 14: [SQLSTATE 01000].
[Note: CHNSHL23456$ is the destination system number]
when same job ran from query analyser that was logged using 'sa' account
fails with the following error.
Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'sa'.
[OLE/DB provider returned message: Invalid connection string attribute]
The windows authenticated user ID exists in both source server/destination
server users list.
Pls hlp to get rid of this error.
Regards,
SSKSSK
Does the login have full pemissions? What is an account SQL Server Agent run
under?
"SSK" <SSK@.discussions.microsoft.com> wrote in message
news:CC9BF3BD-5394-40B1-A8E2-7D1DAC73BBA2@.microsoft.com...
>A job is created to fetch data from source server and populate the
> destination server. This job has the owner as windows authentication(user
> account). This main job inturn creates sub jobs with owner as sa.
> when i run the sub jobs from query analyser it works fine. But when ran
> from
> sql server agent/jobs it is failing with the following error.
> Msg 18456, Sev 14: Login failed for user 'CHNDomain\CHNSHL23456$'.
> [SQLSTATE
> 28000]
> Msg 7312, Sev 14: [SQLSTATE 01000].
> [Note: CHNSHL23456$ is the destination system number]
> when same job ran from query analyser that was logged using 'sa' account
> fails with the following error.
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'sa'.
> [OLE/DB provider returned message: Invalid connection string attribute
]
> The windows authenticated user ID exists in both source server/destination
> server users list.
> Pls hlp to get rid of this error.
> Regards,
> SSK
>|||What account is the SQL Agent service running under ? Jobs owned by sa will
access resources under the context of the SQL Agent service account.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"SSK" <SSK@.discussions.microsoft.com> wrote in message
news:CC9BF3BD-5394-40B1-A8E2-7D1DAC73BBA2@.microsoft.com...
>A job is created to fetch data from source server and populate the
> destination server. This job has the owner as windows authentication(user
> account). This main job inturn creates sub jobs with owner as sa.
> when i run the sub jobs from query analyser it works fine. But when ran
> from
> sql server agent/jobs it is failing with the following error.
> Msg 18456, Sev 14: Login failed for user 'CHNDomain\CHNSHL23456$'.
> [SQLSTATE
> 28000]
> Msg 7312, Sev 14: [SQLSTATE 01000].
> [Note: CHNSHL23456$ is the destination system number]
> when same job ran from query analyser that was logged using 'sa' account
> fails with the following error.
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'sa'.
> [OLE/DB provider returned message: Invalid connection string attribute
]
> The windows authenticated user ID exists in both source server/destination
> server users list.
> Pls hlp to get rid of this error.
> Regards,
> SSK
>|||The SQL server agent is started by Local System account.
The login account has admin privileges on source and destination server als
o.
"Jasper Smith" wrote:
> What account is the SQL Agent service running under ? Jobs owned by sa wil
l
> access resources under the context of the SQL Agent service account.
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "SSK" <SSK@.discussions.microsoft.com> wrote in message
> news:CC9BF3BD-5394-40B1-A8E2-7D1DAC73BBA2@.microsoft.com...
>
>|||Local System does not have access to network resources. If
you are accessing other servers, you need to use a domain
account for the service with the appropriate permissions.
-Sue
On Wed, 24 Aug 2005 23:33:09 -0700, SSK
<SSK@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>The SQL server agent is started by Local System account.
>The login account has admin privileges on source and destination server al
so.
>"Jasper Smith" wrote:
>
destination server. This job has the owner as windows authentication(user
account). This main job inturn creates sub jobs with owner as sa.
when i run the sub jobs from query analyser it works fine. But when ran from
sql server agent/jobs it is failing with the following error.
Msg 18456, Sev 14: Login failed for user 'CHNDomain\CHNSHL23456$'. [SQLS
TATE
28000]
Msg 7312, Sev 14: [SQLSTATE 01000].
[Note: CHNSHL23456$ is the destination system number]
when same job ran from query analyser that was logged using 'sa' account
fails with the following error.
Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'sa'.
[OLE/DB provider returned message: Invalid connection string attribute]
The windows authenticated user ID exists in both source server/destination
server users list.
Pls hlp to get rid of this error.
Regards,
SSKSSK
Does the login have full pemissions? What is an account SQL Server Agent run
under?
"SSK" <SSK@.discussions.microsoft.com> wrote in message
news:CC9BF3BD-5394-40B1-A8E2-7D1DAC73BBA2@.microsoft.com...
>A job is created to fetch data from source server and populate the
> destination server. This job has the owner as windows authentication(user
> account). This main job inturn creates sub jobs with owner as sa.
> when i run the sub jobs from query analyser it works fine. But when ran
> from
> sql server agent/jobs it is failing with the following error.
> Msg 18456, Sev 14: Login failed for user 'CHNDomain\CHNSHL23456$'.
> [SQLSTATE
> 28000]
> Msg 7312, Sev 14: [SQLSTATE 01000].
> [Note: CHNSHL23456$ is the destination system number]
> when same job ran from query analyser that was logged using 'sa' account
> fails with the following error.
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'sa'.
> [OLE/DB provider returned message: Invalid connection string attribute
]
> The windows authenticated user ID exists in both source server/destination
> server users list.
> Pls hlp to get rid of this error.
> Regards,
> SSK
>|||What account is the SQL Agent service running under ? Jobs owned by sa will
access resources under the context of the SQL Agent service account.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"SSK" <SSK@.discussions.microsoft.com> wrote in message
news:CC9BF3BD-5394-40B1-A8E2-7D1DAC73BBA2@.microsoft.com...
>A job is created to fetch data from source server and populate the
> destination server. This job has the owner as windows authentication(user
> account). This main job inturn creates sub jobs with owner as sa.
> when i run the sub jobs from query analyser it works fine. But when ran
> from
> sql server agent/jobs it is failing with the following error.
> Msg 18456, Sev 14: Login failed for user 'CHNDomain\CHNSHL23456$'.
> [SQLSTATE
> 28000]
> Msg 7312, Sev 14: [SQLSTATE 01000].
> [Note: CHNSHL23456$ is the destination system number]
> when same job ran from query analyser that was logged using 'sa' account
> fails with the following error.
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'sa'.
> [OLE/DB provider returned message: Invalid connection string attribute
]
> The windows authenticated user ID exists in both source server/destination
> server users list.
> Pls hlp to get rid of this error.
> Regards,
> SSK
>|||The SQL server agent is started by Local System account.
The login account has admin privileges on source and destination server als
o.
"Jasper Smith" wrote:
> What account is the SQL Agent service running under ? Jobs owned by sa wil
l
> access resources under the context of the SQL Agent service account.
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "SSK" <SSK@.discussions.microsoft.com> wrote in message
> news:CC9BF3BD-5394-40B1-A8E2-7D1DAC73BBA2@.microsoft.com...
>
>|||Local System does not have access to network resources. If
you are accessing other servers, you need to use a domain
account for the service with the appropriate permissions.
-Sue
On Wed, 24 Aug 2005 23:33:09 -0700, SSK
<SSK@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>The SQL server agent is started by Local System account.
>The login account has admin privileges on source and destination server al
so.
>"Jasper Smith" wrote:
>
run time error 3265 after moving from Sql servr 7 to sql server 20
Hopefully somebody see the mistake I am doing.
We are using an Vb application connecting to SQL 7. After moving to SQL 2000
and Windows 2000 system the same application send error message when trying
to insert or update any data via the VB application. What did I missied to
transfer?
I try to move the application via the Copy wizard and also via data import
and both had same result. I also checked the security settings on the old
server and the new one.
Thanks Katja
What exactly are you doing when you get the error?
Andrew J. Kelly SQL MVP
"Katja J." <Katja J.@.discussions.microsoft.com> wrote in message
news:8ABAEC7E-CB87-415F-9066-D19340ED688B@.microsoft.com...
> Hopefully somebody see the mistake I am doing.
> We are using an Vb application connecting to SQL 7. After moving to SQL
> 2000
> and Windows 2000 system the same application send error message when
> trying
> to insert or update any data via the VB application. What did I missied to
> transfer?
> I try to move the application via the Copy wizard and also via data import
> and both had same result. I also checked the security settings on the old
> server and the new one.
> Thanks Katja
We are using an Vb application connecting to SQL 7. After moving to SQL 2000
and Windows 2000 system the same application send error message when trying
to insert or update any data via the VB application. What did I missied to
transfer?
I try to move the application via the Copy wizard and also via data import
and both had same result. I also checked the security settings on the old
server and the new one.
Thanks Katja
What exactly are you doing when you get the error?
Andrew J. Kelly SQL MVP
"Katja J." <Katja J.@.discussions.microsoft.com> wrote in message
news:8ABAEC7E-CB87-415F-9066-D19340ED688B@.microsoft.com...
> Hopefully somebody see the mistake I am doing.
> We are using an Vb application connecting to SQL 7. After moving to SQL
> 2000
> and Windows 2000 system the same application send error message when
> trying
> to insert or update any data via the VB application. What did I missied to
> transfer?
> I try to move the application via the Copy wizard and also via data import
> and both had same result. I also checked the security settings on the old
> server and the new one.
> Thanks Katja
Run SSIS package as an sql server job
Hi There,
I have sqlserver agent running with a windows user account which is member of administrator group. I try to set up the job to run an ssis package and set up to run as sql server agent service account. For some reason, the job fails and it doesn't give much error info if I look at job History. Can somebody plzz help me? I am unable to understand what extra permissions must that user have to run the ssis package as a sql job? And how do I configure the job to give more error details?
Any suggestions are greatly appreciated.
Thanks.
See this KB:http://support.microsoft.com/kb/918760
Run SQL Server Report from .Net WIndows App...
Does a report have to be run from the Report Manager (IIS), or can rdl files
be executed from .Net code in a Windows Application?
I quess what I am asking is, with Crystal and VB 6, I can lauch a report
through a control embedded in the exe file.
Is there a control to place in a Windows Form that can view a report without
haing a IIS Report Manager?
--
Thanks,
ThomasLL, MCDBAI'm pretty sure SQL Reporting Services 2005 will have a WinForms and a
WebForms viewer.
"Thomas.LeBlanc@.NoSpam.Com" wrote:
> Does a report have to be run from the Report Manager (IIS), or can rdl files
> be executed from .Net code in a Windows Application?
> I quess what I am asking is, with Crystal and VB 6, I can lauch a report
> through a control embedded in the exe file.
> Is there a control to place in a Windows Form that can view a report without
> haing a IIS Report Manager?
> --
> Thanks,
> ThomasLL, MCDBAsql
be executed from .Net code in a Windows Application?
I quess what I am asking is, with Crystal and VB 6, I can lauch a report
through a control embedded in the exe file.
Is there a control to place in a Windows Form that can view a report without
haing a IIS Report Manager?
--
Thanks,
ThomasLL, MCDBAI'm pretty sure SQL Reporting Services 2005 will have a WinForms and a
WebForms viewer.
"Thomas.LeBlanc@.NoSpam.Com" wrote:
> Does a report have to be run from the Report Manager (IIS), or can rdl files
> be executed from .Net code in a Windows Application?
> I quess what I am asking is, with Crystal and VB 6, I can lauch a report
> through a control embedded in the exe file.
> Is there a control to place in a Windows Form that can view a report without
> haing a IIS Report Manager?
> --
> Thanks,
> ThomasLL, MCDBAsql
Run SQL Server 7.0 in Windows 2003
Dear all,
Lately, we bought a new server to replace existing old one. After
installation of SQL7, we followed to install the service pack 4 into it.
During the installation, we found SQL7 didn't support in 2003. And we
continued the process until it finished. Is there any problem on using SQL7
in windows server 2003? Since we have some application supported in SQL7
only, we have to keep using SQL7. Anyone know there's any impact using SQL7
in windows 2003? Please help
Best Rdgs
EllisIs there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
> Best Rdgs
> Ellis
>
Lately, we bought a new server to replace existing old one. After
installation of SQL7, we followed to install the service pack 4 into it.
During the installation, we found SQL7 didn't support in 2003. And we
continued the process until it finished. Is there any problem on using SQL7
in windows server 2003? Since we have some application supported in SQL7
only, we have to keep using SQL7. Anyone know there's any impact using SQL7
in windows 2003? Please help
Best Rdgs
EllisIs there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
> Best Rdgs
> Ellis
>
Run SQL Server 7.0 in Windows 2003
Dear all,
Lately, we bought a new server to replace existing old one. After
installation of SQL7, we followed to install the service pack 4 into it.
During the installation, we found SQL7 didn't support in 2003. And we
continued the process until it finished. Is there any problem on using SQL7
in windows server 2003? Since we have some application supported in SQL7
only, we have to keep using SQL7. Anyone know there's any impact using SQL7
in windows 2003? Please help
Best Rdgs
Ellis
Is there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
> Best Rdgs
> Ellis
>
|||Do you have a test environment where you could test the application as a SS 2K installation but running in 7.0 compatibility mode? I'd try it with a full blown upgrade but, if you run into problems, try again in the old 7.0 compatibility.
Sincerely,
Anthony Thomas
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message news:OeIJSk20EHA.1204@.TK2MSFTNGP10.phx.gbl...
Is there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
>
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
>
> Best Rdgs
> Ellis
>
>
Lately, we bought a new server to replace existing old one. After
installation of SQL7, we followed to install the service pack 4 into it.
During the installation, we found SQL7 didn't support in 2003. And we
continued the process until it finished. Is there any problem on using SQL7
in windows server 2003? Since we have some application supported in SQL7
only, we have to keep using SQL7. Anyone know there's any impact using SQL7
in windows 2003? Please help
Best Rdgs
Ellis
Is there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
> Best Rdgs
> Ellis
>
|||Do you have a test environment where you could test the application as a SS 2K installation but running in 7.0 compatibility mode? I'd try it with a full blown upgrade but, if you run into problems, try again in the old 7.0 compatibility.
Sincerely,
Anthony Thomas
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message news:OeIJSk20EHA.1204@.TK2MSFTNGP10.phx.gbl...
Is there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
>
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
>
> Best Rdgs
> Ellis
>
>
Run SQL Server 7.0 in Windows 2003
Dear all,
Lately, we bought a new server to replace existing old one. After
installation of SQL7, we followed to install the service pack 4 into it.
During the installation, we found SQL7 didn't support in 2003. And we
continued the process until it finished. Is there any problem on using SQL7
in windows server 2003? Since we have some application supported in SQL7
only, we have to keep using SQL7. Anyone know there's any impact using SQL7
in windows 2003? Please help
Best Rdgs
EllisIs there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
> Best Rdgs
> Ellis
>|||Do you have a test environment where you could test the application as a SS
2K installation but running in 7.0 compatibility mode? I'd try it with a fu
ll blown upgrade but, if you run into problems, try again in the old 7.0 com
patibility.
Sincerely,
Anthony Thomas
--
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message new
s:OeIJSk20EHA.1204@.TK2MSFTNGP10.phx.gbl...
Is there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So i
f
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
>
> Lately, we bought a new server to replace existing old one. Afte
r
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
>
> Best Rdgs
> Ellis
>
>
Lately, we bought a new server to replace existing old one. After
installation of SQL7, we followed to install the service pack 4 into it.
During the installation, we found SQL7 didn't support in 2003. And we
continued the process until it finished. Is there any problem on using SQL7
in windows server 2003? Since we have some application supported in SQL7
only, we have to keep using SQL7. Anyone know there's any impact using SQL7
in windows 2003? Please help
Best Rdgs
EllisIs there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
> Best Rdgs
> Ellis
>|||Do you have a test environment where you could test the application as a SS
2K installation but running in 7.0 compatibility mode? I'd try it with a fu
ll blown upgrade but, if you run into problems, try again in the old 7.0 com
patibility.
Sincerely,
Anthony Thomas
--
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message new
s:OeIJSk20EHA.1204@.TK2MSFTNGP10.phx.gbl...
Is there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So i
f
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
>
> Lately, we bought a new server to replace existing old one. Afte
r
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
>
> Best Rdgs
> Ellis
>
>
Tuesday, March 20, 2012
Run SQL against SQL Server 2000 on Windows 2003 Web Edition
I have a dedicated Windows 2003 Web Edition server running SQL Server 2000.
SQL Server 2000 was pre-installed. What tools can I use to interrogate and
update the SQL Server 2000 database from the Windows 2003 Web Edition Server
?
Client and Adminstration tools are not supported and will not install on the
Web version of the 2003 operating system.Am Mon, 5 Jun 2006 04:35:02 -0700 schrieb AJ:
> I have a dedicated Windows 2003 Web Edition server running SQL Server 2000
.
> SQL Server 2000 was pre-installed. What tools can I use to interrogate an
d
> update the SQL Server 2000 database from the Windows 2003 Web Edition Serv
er?
> Client and Adminstration tools are not supported and will not install on t
he
> Web version of the 2003 operating system.
Maybe this can help you:
http://www.sqlmanager.net/en/products/mssql/manager
At the bottom you can download a free Lite-version!
bye, Helmut
SQL Server 2000 was pre-installed. What tools can I use to interrogate and
update the SQL Server 2000 database from the Windows 2003 Web Edition Server
?
Client and Adminstration tools are not supported and will not install on the
Web version of the 2003 operating system.Am Mon, 5 Jun 2006 04:35:02 -0700 schrieb AJ:
> I have a dedicated Windows 2003 Web Edition server running SQL Server 2000
.
> SQL Server 2000 was pre-installed. What tools can I use to interrogate an
d
> update the SQL Server 2000 database from the Windows 2003 Web Edition Serv
er?
> Client and Adminstration tools are not supported and will not install on t
he
> Web version of the 2003 operating system.
Maybe this can help you:
http://www.sqlmanager.net/en/products/mssql/manager
At the bottom you can download a free Lite-version!
bye, Helmut
Friday, March 9, 2012
Run DTS package
Hello !
I have a DTS package which I can run it fine from command line using
one SQL account who is not a also a user in the windows 2003
machine.If I try as another user that is a user or sysadmin account in
the box then I get a login error from OLE. Any ideas? When I use the
Enterprise Manager to run the package it runs fine regardless of the
user.
Many Thanks,
Marios Koumides"Marios Koumides" <koumides@.gmail.com> wrote in message
news:f0e6dfb6.0504180147.2807f984@.posting.google.c om...
> Hello !
> I have a DTS package which I can run it fine from command line using
> one SQL account who is not a also a user in the windows 2003
> machine.If I try as another user that is a user or sysadmin account in
> the box then I get a login error from OLE. Any ideas? When I use the
> Enterprise Manager to run the package it runs fine regardless of the
> user.
>
> Many Thanks,
> Marios Koumides
It's not really clear (to me) from your description exactly who is running
the package, and where it's executing. Are you running it with dtsrun.exe?
Are you running it on the server, or on your workstation? Can the users who
cannot run the package log in to MSSQL, or only to Windows? Are you using
Windows authentication or SQL logins for MSSQL? What exactly is the error
message? Which version of MSSQL do you have?
As a complete guess, the package contains MSSQL connection objects which use
Windows authentication, so it fails when you run it with a Windows user
which cannot log in to those MSSQL servers. But without more information,
that may be totally wrong.
Simon|||Simon Hayes wrote:
> "Marios Koumides" <koumides@.gmail.com> wrote in message
> news:f0e6dfb6.0504180147.2807f984@.posting.google.c om...
> > Hello !
> > I have a DTS package which I can run it fine from command line
using
> > one SQL account who is not a also a user in the windows 2003
> > machine.If I try as another user that is a user or sysadmin account
in
> > the box then I get a login error from OLE. Any ideas? When I use
the
> > Enterprise Manager to run the package it runs fine regardless of
the
> > user.
> > Many Thanks,
> > Marios Koumides
> It's not really clear (to me) from your description exactly who is
running
> the package, and where it's executing. Are you running it with
dtsrun.exe?
I tried 2-3 users and they can run the package using dtsrun.exe but
providing a username and password different from theirs.(This username
and password is not a windows user but MS-SQL one)
> Are you running it on the server, or on your workstation?
Running it on the server.
> Can the users who cannot run the package log in to MSSQL, or only to
>Windows?
They can log to both SQL and Windows
Are you using Windows authentication or SQL logins for MSSQL? What
exactly is the error
> message? Which version of MSSQL do you have?
Yes I am using windows authentication in MS SQL 2000.
The error message is they can't login MS SQL 2000
Many Thanks,
Marios Koumides
> As a complete guess, the package contains MSSQL connection objects
which use
> Windows authentication, so it fails when you run it with a Windows
user
> which cannot log in to those MSSQL servers. But without more
information,
> that may be totally wrong.
> Simon
Wednesday, March 7, 2012
Run a SSIS Package including Windows Tasks Scheduler?
Hello
As a beginner I have created some Packages to import Data to SQL Server.
The Packages are running well.
I have created a Task to run the Package on a SQL SERVER 2005 Express. The Task starts.
Then a Execute Package Wizard Picture appears on the Screen.
I have mannually to select the Connection Manager and the Connection String.
After the selection the Task runs without any Problem.
Now I like to get the Task to run without any manual intervention.
I was looking in Internet but could not find a solution.
Can someone give me a hint how to get the Task working without intervention?
Thanks for an early answer.
Regards
Chaepp
Specify dtexec.exe as executable to run in the Job definition.See Books Online for dtexec command line parameters reference. In simplest case: "dtexec.exe /f c:\package.dtsx"|||
Hello Michael
I'ts working now. Thank you very much for your help!
Regards
Chaepp
run a new server registration
Hi:
My pc is windows 2003 server and I have installed SQL SERVER 2005 EXPRESS.
From Management Studio I made a New Server Registration with Windows Authentication.
I can't run the new server, its icon appears with a white dot (instead of green when a server is running or red when the
server is stopped)
I go to server properties and click the "Test" button and I get the next message error:
Testing the registered server failed. Verify the server name, credentials, an database, an then click Test again.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may becaused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL NetworkInterfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server)
what could be wrong?
How can I run the server?
Thanks!
Make sure Named Pipes and TCP/IP network are enabled.
You can set from Sql Server Configuration Manager.
|||Is the new registered SQL a remote instance? Make sure the server name is correct, and SQL Browser service is running on the SQL box.|||I have enabled remote connections at the surface area configuration tool but when I register the new server at Management Studio I get the same message box when I test this new server.The type of server I want to register is Database Engine
The icon appears with a white dot again.
At the surface area configuration tool I can't start SQL Server Browser. Start, Stop, Pause and Resume buttons are disabled.
The default database engine server is running, its name is server1\sqlexpress.
Why I can't register another server?|||
yes
Named Pipes and TCP/IP network are enabled
|||You can start SQL Browser from services.msc or "SQL Server Configuration Manager". Is?the?new?server?you?want?to?register?a?remote?server??If?so?you?can?take?a?look?at?this?post:http://forums.asp.net/thread/1289341.aspx
Saturday, February 25, 2012
Run a DTS Package "in the background" or with low priority?
Configuration:
Windows 2000
Sql Server 2000
Quad CPU
Problem:
I have a DTS update operation that takes many hours to run. The
process is monthly, and for that process speed is not an issue; however,
the database server hosts multiple databases, some with applications
that do interactive queries. The DTS Update step brings down the speed
of interactive queries on the database being updated and all other
databases dramatically.
Is there any way to lower the priority of a DTS package operation so
that it does not impact interactive queries on that databases and other
databases running on the server?
Basically, can I run a DTS package "in the background" or with a very
low priority?Hi
You may want to read The Guru's Guide to SQL Server Architecture and
Internals by Ken Henderson ISDN 0-201-70047-6 which goes into depth on
thread scheduling. You may get some benefit by setting the MAXDOP query hint
on some of your statements. Highlighting what part of your process is slow
and why it is slow may help you to provide a more efficient solution.
You may also want to review the architecture of this process and either
split it into smaller independent chunks that can be run separately, or if
the data created by this process is read-only to the other processes, then
you may want to look at doing it offline and then swapping it in when the
process is complete e.g. having it all in a separate read-only database.
John
"John Bailo" <jabailo@.texeme.com> wrote in message
news:gsudneQq3ZlEYAzeRVn-uw@.speakeasy.net...
> Configuration:
> Windows 2000
> Sql Server 2000
> Quad CPU
>
> Problem:
> I have a DTS update operation that takes many hours to run. The process
> is monthly, and for that process speed is not an issue; however,
> the database server hosts multiple databases, some with applications that
> do interactive queries. The DTS Update step brings down the speed of
> interactive queries on the database being updated and all other databases
> dramatically.
> Is there any way to lower the priority of a DTS package operation so that
> it does not impact interactive queries on that databases and other
> databases running on the server?
> Basically, can I run a DTS package "in the background" or with a very low
> priority?
>
>
Windows 2000
Sql Server 2000
Quad CPU
Problem:
I have a DTS update operation that takes many hours to run. The
process is monthly, and for that process speed is not an issue; however,
the database server hosts multiple databases, some with applications
that do interactive queries. The DTS Update step brings down the speed
of interactive queries on the database being updated and all other
databases dramatically.
Is there any way to lower the priority of a DTS package operation so
that it does not impact interactive queries on that databases and other
databases running on the server?
Basically, can I run a DTS package "in the background" or with a very
low priority?Hi
You may want to read The Guru's Guide to SQL Server Architecture and
Internals by Ken Henderson ISDN 0-201-70047-6 which goes into depth on
thread scheduling. You may get some benefit by setting the MAXDOP query hint
on some of your statements. Highlighting what part of your process is slow
and why it is slow may help you to provide a more efficient solution.
You may also want to review the architecture of this process and either
split it into smaller independent chunks that can be run separately, or if
the data created by this process is read-only to the other processes, then
you may want to look at doing it offline and then swapping it in when the
process is complete e.g. having it all in a separate read-only database.
John
"John Bailo" <jabailo@.texeme.com> wrote in message
news:gsudneQq3ZlEYAzeRVn-uw@.speakeasy.net...
> Configuration:
> Windows 2000
> Sql Server 2000
> Quad CPU
>
> Problem:
> I have a DTS update operation that takes many hours to run. The process
> is monthly, and for that process speed is not an issue; however,
> the database server hosts multiple databases, some with applications that
> do interactive queries. The DTS Update step brings down the speed of
> interactive queries on the database being updated and all other databases
> dramatically.
> Is there any way to lower the priority of a DTS package operation so that
> it does not impact interactive queries on that databases and other
> databases running on the server?
> Basically, can I run a DTS package "in the background" or with a very low
> priority?
>
>
Subscribe to:
Posts (Atom)