I am currently having issues getting the odbc32ad driver configured properly so I can transfer the database off of the old Oracle 7 database (currently running SCO UNIX). I have the orignal Oracle 7 disk and installed the drivers, but I am not sure what the SA login for Oracle is, nor do I know what the "Connection String" is.
Has anyone made this transfer before? Please help.
I was a Oracle Developer / DBA on Unix Environments all along my career, Very recently iam starting to manage a SQL Server 2005/Windows 2003 Server setup.
Part of my new job is to automate to load Huge Data files/Flat Files (3/4 GB in size) into SQL Server 2005 DB.
Have these initial questions..
Since the files are too large to open at once... What sort of Command Line Interfaces people use on the Windows Boxes.. like doing a "wc" (Word Count) / GREP 'ng Files / Massaging Data Files one line at a time (Like using SED / AWK Commands).. Etc
Any Input / Direction is appreciated...
I have a windows server 2003 R2 sharing a filesystem using NFS. I have created a group and passwd file and mapped the ids' to the unix login ids' . I', able to mount but when I try to cd to the directory I get "NFS access failed for server testsrvr: RPC: Authentication error". On the win2k3 server I'm getting an event error "There was a mapping failure". I have the Admin id on the win2k3 server mapped to the unix root login .
View 1 Replies View RelatedGod morning!
I 've just installed SQL Server 2005 on Windows 2003 Server 64 bit. One of my databases need to connect to seveal Oracle databases.
- I tried installing 64 bit Orcale 9 on this server. Got a strange message that the application (Oracle 64 bit) could not be installed on a 32 bit server! Strange!
- I installed Oracle 9 32 bit on the server, but I could not find ODBC driver in the Data sources! Neither the oledb under providers in MSS Manager Studio!
- Same result efter several desintall and installation. A college copied the .dll files och run a script to register the dll files. We could then se the Oracle driver in the Database sources, but we could not create any connection.
- We have even tried an 10G version of Oracle with the same result.
Is there anyone who succeeded installing Oracle on 64 bit Windows and could create odbc connection/linked server?
Regards
First, let me start by saying I know the answer to this, but due to politics any answer I give will be viewed with some disdain and disbelief.
A Unix/Network [rtdpmin one our sister agencies is trying to solve a problem that really does not need to be solved, but ....
The sister agency uses Information Builder's WebFocus on Unix. When they try to read my data warehouse in SQL Server 2000 it times out on them (on their end and they claim they cannot fix it) (This is using the supplied WebFocus ODBC/JDBC driver for SQL Server). This has lead to accusations of us not letting them read the data.
After much gnashing of teeth over "if you do data and data analysis for a living, why do I have to show you how to set-up an ODBC connection" we have shown them how to connect to the data, read it, and transfer it using MS-ACCESS, EXCEL, and more importantly SPSS. This is not good enough because they cannot figure out how to put it into WebFocus.
Their network person has come-up with the brilliant idea of reading the .mdf directly by installing Windows for Unix on the Unix side and then just pointing to the .mdf file and "reading it ".
Unless I have missed something somwhere (I will admit possible), I know you need a driver to read MS-SQL and that driver in every example I have seen could care less about the physical location of the .mdf file. It wants to know what database, what server (ip or name) and what security/login to use.
Could someone give me a more "technical answer" or even Microsoft's party line so I do not have this person mucking around with my production server trying to acomplish the impossible.
Hi,
We are trying to move our application from SQL2005 to SQL2005, we are using 2005 jdbc driver 1.1.
The problem we have is, when a date is retrieved from the database, only the year part got correctly, but the date is automatically set to January 1 of that year. The interesting thing is this problem doesn't occur on local development environment (developer's windows platform), it only happens when we deploy the application to production server (unix).
Does anyone know what is going on, how to fix it?
Thanks.
Cathie
We just upgraded the memory of our database server from 2GB to 4GB. And its OS is windows 2003 standard and sql is 2005 standard edition. According to microsoft(http://msdn2.microsoft.com/en-us/library/ms143685.aspx and http://msdn2.microsoft.com/en-us/library/aa366778.aspx#physical_memory_limits_windows_server_2003), this configuration should allow database use up to 4 GB memory. My question is : Do I need to do anything(such as: adjust the maximum memory in management studio) to let our server be able to consume this extra 2 GB memory?
Does this solution http://support.microsoft.com/kb/274750 apply for SQL server 2005?
At first I thought it was just me, but has anyone else noticed that SQL 2005 suffers a performance hit when you install Windows Server 2003 SP2?
Since SP2, memory and hard drive usage has gone through the roof on a number of servers I use. It may just be coincidence... but it seems unlikely.
Maybe this is just an oversight in the documentation? Here it is for all to see on the download page for SQL 2005 SP2:
http://tinyurl.com/35nunk
Note the supported operating systems:
Windows 2000 Service Pack 4; Windows Server 2003 Service Pack 1; Windows Vista; Windows XP Service Pack 2
NO mention of Windows 2003 Service Pack 2, but Windows 2003 Service Pack 1 is specifically mentioned.
Any ideas on this one? Thanks!
Chris
when i try to create a new database i get a error: The server could notload DCOMwhat is wrong and how can i fix it?i have updated mssql/win 2003 with the lates updatesRgdsBobby
View 1 Replies View RelatedI've got a Windows Server 2003 for Small Business Server. It had got SQL installed. But then SQL was uninstalled. Now I need to put SQL back in, but I don't see how!
There're three CD-Rom but I don't see how and from which CD to install back SQL.
PS: Correct me if I'm wrong, Windows Server 2003 is sold with SQL 2005, right?
We have a SQL 2005 installed in Windows 2003 64 bit system, which has 16 CPU and 32GB RAM, but the performance is poor. SQL server is AWE enable and the sql start account with "Lock Pages In Memory". I checked the task manager and it looks that the SQL server used only about 300 MB memory. Here is what I found:
http://blogs.msdn.com/psssql/archive/2006/11/28/sql-server-becomes-sluggish-or-appears-to-stall-on-64-bit-installations.aspx?CommentPosted=true#commentmessage
What I need to do?
Thanks
Hello to all,
we try to install an SQL 2005 server on a Windows 2003 server that is also a Domain controller. In discussions of july last year, Dan Jones said :"Unfortunately in setup you cannot change the default account for all services. So there is absolutely no work around for this problem. This will absolutely be fixed by RTM - "
Can anybody help me in that way. We tried installing with our latest CDs (december 2005)
I'm unable to successfully install SQL 2005 on Windows Server 2003. Everything installs correctly except 'SQLXML4', and after installation, there's no Management Studio, unless I then install SQL Express Management Studio.
Installation details: Successfully installs 'Native Client' and the 'Support Files'. The 'System Configuration Check' passes everything. Installed 'Database Services', 'Integration Services', 'Client Components' (except for the 2 development tools), and 'Books Online'. Created the default instance (there were no other instances). Set it to run as 'Local System'. Set only the 'SQL Server' service to start after setup. Specified 'Mixed Mode'.
Then the installation proceeds, and everything looks good until SQLXML4 fails. Soon after, a window pops up saying "Setup is preparing to continue with the installation". Nothing happens till I click 'OK', and then 'Workstation Components' shows as having failed. Then the installation finishes normally. However there's no Management Studio, except that I then installed the SQL Express Management Studio, which appears to work fine.
I tried uninstalling, and installing again, but got the same results.
How can I get this to install correctly?
Thank you.
Hello!I'm migrating an IIS/SQL-Server application from Windows NT4.0 and SQL-Server 2000 to Windows 2003 Server and SQL-Server 2005.My problem is that it is not possible to connect local (IIS and SQL-Server 2005 are runnng on the same node) using ODBC. Running theapplikation on a remote IIS (XPPro) all works fine. I can't see anydifferences in the ODBC-configuration.Any idea?Thanks
View 5 Replies View RelatedI get and error when installing MS SQL 2005 on Windows 2003 server with SP2. It bombs at the very end of the install and Microsoft notification program generated he message below to be sent to Microsoft. Please help. At a stand still.
-------------------------------------------------------------------------------------------------------------------
EventType : sql90setup P1 : unknown P2 : 0x645 P3 : unknown
P4 : 0x645 P5 : unknown P6 : unknown P7 : sqlserver2005_bc.msi@
Below is the summary.txt
-------------------------------------
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time : Thu Feb 28 22:52:28 2008
Machine : ESAPPS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_2.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_2.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_2.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_2.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_3.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_3.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_3.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_BOL_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_3.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLXML4_1.log
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Thu Feb 28 23:01:11 2008
List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_BackwardsCompat_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SqlWriter_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_BOL_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLXML4_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework 2.0 LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework Upgrade Advisor.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework Upgrade Advisor LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework Windows Installer.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework Windows Installer LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SCC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_WI.log
I cannot make named pipe connection with client by ODBC DSA.
Here is information. Refering to http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1.
[1] Client side:
1. What is the connection string in you app or DSN? (please specify) ODBC \[SERVER_NAME]pipesqlguery
2. If client fails to connect, what is the client error messages? (please specify) Connection failed: SQLState: €™01000€™ SQL ServerError: 1326 [Microsoft][ODBC SQL Server Driver][Named Pipes]connectionOpen (Connect()) Connection failed: SQLState: €™08001€™ SQL Server Error: 17 [Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.
3. Is the client remote or local to the SQL server machine? [Remote | Local]
4. Can you ping your server? [YES | NO ]
In cmd.exe console, type €œping -a <server_name>€?.
5. Can you telnet to your SQL Server? [YES | NO, please specify the error message ]
In cmd.exe console, type €œtelnet <server name> port, where port can be 135, 445 or sql_server_tcp_port. If your cmd.exe console turns into a complete black screen with a cursor flushing on top left corner, you are connected. Type ctrl+€™[€˜ to bring up telnet prompt and type €œquit€? <enter>.
6. What is your client database provider? [SNAC | MDAC | ADO.NET1.0 | ADO.NET2.0| other ODBC (please specify] Or/And, what is your client application? [SQL Management Studio | SQL Profiler | Visual Studio | Other (please specify).
7. Is your client computer in the same domain as the Server computer? (Same domain | Different domains | WorkGroup)
8. What protocol the client enabled? [Shared Memory | TCPIP | Named Pipes].
9. Do you have aliases configured that match the server name portion of your connection string? If so, please check if it is correct. You can use cliconfg.exe (SS 2000) or SQL Server Configuration Manager (SS 2005) to configure the alias. [NO]
10. Do you select force encryption on server and/or client? [NO]
I was able to connect with TCP/IP settings.
[2] Server side:
1. What is the MS SQL version? [SQL Server 2005]
2. What is the SKU of MS SQL? [Enterprise | Standard | Workgroup | Express (or MSDE) | other (please specify)].
3. What is the SQL Server Protocol enabled? [Shared Memory | TCPIP | Named Pipes ]. Use SQL Server Configuration Manager to configure it and check ERRORLOG or event log to confirm.
4. Does the server start successfully? [YES | NO] If not what is the error messages in the SQL server ERRORLOG?
5. If SQL Server is a named instance, is the SQL browser enabled? [YES | NO]
6. What is the account that the SQL Server is running under?[Local System | Network Service | Domain Account]
7. Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? [YES | NO | not applicable | not enabled]
8. Do you make firewall exception for SQL Browser UDP port 1434? In SQL2000, you still need to make firewall exception for UDP port 1434 in order to support named instance.[YES | NO | not applicable | not enabled]
I could connect locally with named pipes.
Do I have to make some file shares manually?
[2a] Tool Used to Connect
What tool or Application are you using to connect to SQL Server (eg: Visual Studio, SQL Server Management Studio, SQLCmd.exe, OSQL, etc) and especially the version of SQL Server (Express, Workgroup, Standard, Enterprise, Developer)
[3] Platform:
1. What is the OS version? [Windows XPSP2 | Windows 2003 | Windows 2000 | Windows 98 | others (please specify ) ].
1. Server [Windows Server 2003 R2]
2. Client [Windows XP SP2]
2. Do you have third party antivirus, anti-spareware software installed? [Symantec | Norton | other (please specify) ½ NO].
[4] Misc:
1. If you have certificate configuration issue: Please use €œcertutil.exe €“v €“store my€? to dump certificate specific info and post it in your question. [NO]
Hi all
I am busy looking at the WIndows 2003 Comptu Cluster setup (Well I am loading it)
And I am interested to know if any body has run SQL 2005 Enterprise on this platform before ?
I know that Windows Compute Cluster uses a JOB scheduler to run tasks and this can be customised for each task , to allow it to use more resourses or less .
I also know that SQL 2005 is much more capable of running cluster mode with database replication and log file shipping
I want to know is of I load SQL 2005 on a Clustered Compute setup will it handle the SQL jobs, database requests with out the scheduler.
The question might be a bit tricky but any help is appricated
Thanks
Sylvester
Hello.
When I installed SQL 2005 SP1 on Windows 2003 Server, I received the following message:
"A recently applied update, KB913090, failed to install."
At the end, "Database Services" was marked as "Failure".
I have tried everything I could find in the knowledge base and on the forums, but still
was not able to install SP1.
For example:
http://support.microsoft.com/default.aspx?scid=kb;en-us;918357
Any insights would be greatly appreciated.
Is this supported on Windows 2003 sp2 and does anyone know how to do a silent install of this using Altiris?
Thanks!
We have done a complex software with VB using SQL Server through ADO. Nowour customer is planning to switch from SQL Server to Unix/Aix Oracle 8 DB.I'm a newbie both in Oracle and Unix and wonder how this will affect oursoftware. Would changing the connection string be enough (I quess not).Any help would be appreciated !Jyrki HamalainenLaukaa, Finlandjyrki . hamalainen @ ids . fi
View 1 Replies View RelatedHello, we currently have our database (MSSQL 2005) on our web server however to do increased traffic and business we are now moving our database to its own server. I was wondering if anyone here knew of some good ways to setup/tune Windows Server 2003 and SQL 2005 for best performance. MSSQL will be the only application running on the server and want to make sure it is as fast as possible!
Thanks in advance!!!
Hello - We have been unable to successfully install Integration Services with an instance of SQL 2005 running on a Windows Small Business Server 2003. Installation proceeds with no errors, but when you attempt to connect to the Integrations Services and browse to where it apparently exists, the SQL Server Managment Studio returns the following error:
TITLE: Connect to Server
------------------------------
Cannot connect to ABDI04.
------------------------------
ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
Connect to SSIS Service on machine "ABDI04" failed:
The specified service does not exist as an installed service.
.
------------------------------
Connect to SSIS Service on machine "ABDI04" failed:
The specified service does not exist as an installed service.
.
------------------------------
BUTTONS:
OK
------------------------------
We have tried uninstalling the Integration Services, then reinstalling it and again applying SP2 with the same results.
Thank you.
I'm a new developer to both SQL Server 2005 & Windows 2003, so forgive me if this question seems a little too basic. I'm coming from a Oracle and UNIX background.
I've create a stored procedure in SQL Server 2005. I now want to execute this from the command line in Windows 2003. Eventually, I want our UNIX scheduler, autosys (which runs on a different UNIX machine obviously) to be able to execute this. In my old environment, I created a UNIX shell script as a wrapper let's say 123.sh. This shell script would accept as a parameter the name of the stored procedure I wanted to execute. If this stored procedure also had parameters it needed to be passed to it, I would have strung these values out in the command line in UNIX. Two examples of how the command line in UNIX I used to execute the Oracle stored procedure might look are listed below.
123.sh sp_my_stored_procedure input_parm1 input_parm2
123.sh sp_different_stored_procedure input_parm1
This way anytime I created a new stored procedure, I could reuse the shell script wrapper 123.sh and just pass in the name of the newly created stored procedure and any parameters it needed.
How can I accomplish this same type of functionality in the SQL Server 2005/Windows 2003 environment.
Thanks, Jim
Has anyone done this? If so, how? I saw the systems requirement pages and web edition is not listed as as supported OS, but it's what we have. TIA.
View 1 Replies View RelatedI have installed SQL 2005 (X64) on 64-bit Windows 2003 server (AMD). One of my databases need to connect several Oracle databases on 32 bit servers.
I managed to install Oracle 32 bit Client (was unsuccessful with 64 bit installation) and could set up the odbc (32). But I coul'nt find Oracle under linked servers!
Does anyone know what I need to do?
I am having major performance issues with Microsoft SQL 2005 x64 Standard Editions performance on Windows Server 2003 x64. The PC has two quad core cpu's with 8gb of ram and running a 500gb mirrored SCSI (Raid 1) drive system. The database running on the server is about 11gb. I've run a defrag several times which helps a little but I was hoping I could do something else to increase the performance.
I have also found that the bottle neck in the SSIS package is the backup and restore process of an 11gb database which takes about 1 hour (backup takes 1 hour and restore takes 1 hour) when it should take about 11 minutes. Is there anything I can do to make these processes run faster or to find out why they are taking so long? Any ideas would be a great help.
Thanks,
100011
Hey all!
I've tried all I know in an effort to get SQL 2005 Express to allow remote connections on my customer's 2K3 server and I'm not having any luck. I've followed MSKB 914277, including adding the exceptions to their Windows firewall...even disabled the firewall altogether (for testing purposes), and I still can't get remote clients to connect. As suggested by various other posts, I used netstat -an to confirm that SQL is listening on port 1433 for the desired IP on the server.....and saw that it is listening. Here's a snippet:
TCP 192.168.0.2:1433 0.0.0.0:0 LISTENING
TCP 192.168.0.2:1433 192.168.0.2:1738 ESTABLISHED
TCP 192.168.0.2:1738 192.168.0.2:1433 ESTABLISHED
TCP 127.0.0.1:1433 0.0.0.0:0 LISTENING
I can connect to the database locally (i.e. on the 2K3 server itself) using just the IP address .... tried with a DSN, UDL, ODBC, and SSMSE...all of which have no problems (as shown by the two, "ESTABLISHED" entries in the netstat results above which were from running SSMSE locally on the server at the time of the netstat). But if a remote computer on the network tries to connect, they cannot connect. Sorry, I don't have a copy of the error message the clients are getting yet.
I asked The customer's IT to confirm that the clients CAN can "see" the server (i.e. that there wasn't some kind of router or firewall blocking their path) and they sent me a copy of the server's pfirewall.log file. Here is an entry from the file that seems to show that client requests ARE getting to the server:
2007-12-17 19:12:13 OPEN-INBOUND TCP 192.168.0.4 192.168.0.2 1213 1433 - - - - - - - - -
2007-12-17 19:12:13 CLOSE TCP 192.168.0.2 192.168.0.4 1433 1213 - - - - - - - - -
I'm starting to get in over my head here (I'm a programmer, not a DBA or Net Admin), but doesn't the above suggest that an incoming request came in from .4 on port 1213 and attempted to connect to .2 on port 1433, but the connection was denied or dropped by the server? If so, why? Is this related to another MS KB I read about connection pooling? I'm way over my head here and could use some help. Did I miss something subtle during configuration of SQL Express?
Thanks in advance.
Hi,
I am testing SQL 2005 Standard (32 bit) on a Windows 2003 Server 64 bit with 8GB of RAM? Should I enable the AWP Setting or not and should I change the maximum server memory (currently saying 2GB)?
Thanks!
Tom
This is a fresh install of SQL Server 2005 (64bit) on a Windows 2003 R2 SP2 64bit OS. The Cluster has been built and SQL 2005 has been installed (Database Engine(clustered), Analysis Server(clustered), Notification Server, Integration Server, Reporting Services). SQL 2005 SP2 has been installed.
Now, I want to install Notification Server, Integration Server and Reporting Services on the second node for high availability.
When I select 'Install New Components' from Add/Remove Programs, the System Configuation Checker tells me theres a version difference and to:
To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
I'm using the same binaries as the original install. Could this be a result of installing SQL 2005 SP2?
Can someone help me out with this. I'd prefer using the setup interface instead of a command line script.
I Try to install SQL Server Express in Windows 2003 Standard edition x64 and have some problems.
It say that can not instal client and say to use sqlncli_x64.msi, but I can not find this packege to install this client and I receive one alert with ASP.NET register 64.
I Check all request systems requirements many times and looks ok.
How can I solve this to install properly the SQL 2005 Express? When the setup finish say that was not possiblem to install SQL Server 2005 Express.
Regards
Leandro
Hello
I've installed Windows 2003 SP2 in a stand-alone cluster (will be adding a second node later). I'm now installing SQL Server 2005 Developer Edition 64-bit extended and would like to have the "Create a SQL Server Failover Cluster" box to not be grayed out. Even when I check the "SQL Server Database Services" box, it still has the cluster box grayed out.
Any idea's?
TIA!
Greetings,
We are having major performance issues with Microsoft SQL 2005 64bit Standard Editions performance on Windows Server 2003. We have an SSIS package running very slowly (and other sql tasks) on our two quad core cpu system with 8gb of ram and running a 500gb mirrored SCSI (Raid 1) drive system. The database running on the server is about 11gb.
Does anybody have any suggestion we could try to increase the performance of the server? I've run a defrag several times which helps a little but I was hoping I could do something else to increase the performance.
Thank you.