How do I determine which SQL7 service pack is install. I ran select @@version and this is the version number it shows: "Microsoft SQL Server 7.00 - 7.00.842 (Intel X86)"
I checked Microsofts site and could not find any info on this.
Microsoft SQL Server 2005 - 9.00.1399.06 (X64) Oct 14 2005 00:35:21 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
how to determine that i have installed sql server service pack 2
do i have to restart the server to see the effect, how will it show that it is service pack 2
if we installed ssis on the same server much later than the engine itself, could it have been installed successfully at an earlier service pack than the engine? I did a select @@version on the engine and got
Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
I cant see a way from the client to get a service pack on ssis itself. I'd like to be sure about a suggestion from one of your contributors before approaching our technical guys about their failure to install sp 2 of something.
I upgraded the OS on my SQL 2005 SP2 to Windows 2003 SP2. Everything still works fine but now Windows Update says that I need SQL 2005 SP2 again. I checked the version of SQL on the server and it's still SP2. Did the Windows service pack somehow downgrade parts of my SQL installation? I know I can probably just reinstall the SQL service pack but I was just curious...
We have our custom install code using C# for a huge Client desktop application. We package SQL Express 2005 along with Backward Compatibility pack as this application was using MSDE before and at 11th hour management decided to pack SQL Express and backward compatibility pack.
During installation we want to detect if the Backward compatibility pack is already installed to avoid overwrite. Can anyone suggest how to detect if Backward compatibility pack is already installed using C#? I am sure there should be some registery keys to look for but don't know which.
I am trying to install MS Sql Server 2000 on my machine. The OS on my machine is Windows XP SP2. During the installation i keep getting an error message, "Setup failed to configure the server. Refer to the server error logs and C:WINDOWSsqlstp.log for more information." I have copied an extract from the sqlstp.log file below:
10:05:28 Process Exit Code: (-1) 10:05:31 Setup failed to configure the server. Refer to the server error logs and C:WINDOWSsqlstp.log for more information. 10:05:31 Action CleanUpInstall: 10:05:31 C:WINDOWSTEMPSqlSetupBinscm.exe -Silent 1 -Action 4 -Service SQLSERVERAGENT 10:05:31 Process Exit Code: (1060) The specified service does not exist as an installed service.
Does Anyone know if there is a way to verify the SQL Service Pack Version on 7.0 on Windows 2000 Advanced server?
I'm getting this results for select @@version
Microsoft SQL Server 7.00 - 7.00.623 (Intel X86) Nov 27 1998 22:20:07 Copyright (c) 1988-1998 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 1)
I installed Service Pack 5 on SQL 7.0 successfully, but when I go back to run @@version, it gives me Service Pack 2 which is the old pack. Does anyone know why and had an experience with this?? Thanks wonderful people!!!
I have a cluster server, with SP3 coming out I wanted to upgrade the SP2 I have right now, when I start SP3 installation it starts and quickly exits from the program. DO I need to uncluster the server before applying SP3? or there is a way arround it?
has anyone had this experience before after we installed service pack 2 our jobs are taking about 10hrs, some run it says it's succesfull but it didn't update the tables.
I have installed service pack-1 on SQL SERVER 7.0 Standard Edition. After the pack is installed @@version is still showing 7.00.623 instead of 7.00.699 HELP !!!
Does anyone else have any concern about this Watson technology creeping in to SQL Server in SP3? I don't like it in Explorer and I'm sure not going to like it in SQL Server!
BTW, Forrest article about the new security patches at http://www.databasejournal.com/news/article.php/1475241 is in error, I think, when it refers to SP4.
Is the sql server 2000 service pack 3 worth applying to production database server or should I still wait. i do have sql 2000 service pack 2 on the server ?
I am binding bunch of SQL object change t/sql code into one service pack and then distribute to around 1500 databases.
gradually, I feel I need to put the table/proc/trigger/field/datatype/data size.... all the changes into a kind of database so that could let me or other developers quickly pull out all the change info against a particular object, say table customer. It may have changed 15 times already, from enlarge customerName data size from 30 to 50, add a unique constraint to force the customerName uniquenss, add an index on companyPhone field, modify a delete trigger when an customer becomes inactive to append to a historyCustomer table before delete it....
Of course, the db should also include servicePack release date, each object release reason, approved by.....
At first, it sounds simple and not a big deal, but when I draw something and found the relationship between table--field--datatype--size--constraint is not so simple. Is there something even 'raw' available there already, so I might take a short cut and move on?