Hi,
How can I "confirm" that I am running sp3a ???
When I run @@version I get:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
But I should get:
Microsoft SQL Server 2000 - 8.00.760.09 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
Can somebody confirm that the .09 does not show up on the 3a SP (or) was SP3 later released (as I think I recall reading) which incorporated 3a ???
I know we are at 3a I just can't confirm it via these queries :confused: .
If you backup the transaction log (today at Noon) and then take a backup copy that's a month old of the same database and restore it to your current database [which is possible], Can you then apply the transaction log that you took at noon to that same database which you restore with last month data?
I wouldn't think so because you have a month worth of transaction log, your LSN wouldn't be matching.
I have taken over an existing SQL 7.0 server. It has current production systems running on it.
I need to *confirm* what the SQL Agent password is; what simple task or job can I setup that will require me to provide the SQL Agent password so that I can confirm that what I have been told it correct?
Server Error Message: Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1010818663, index ID 0: Page (1:305381) could not be processed. See other errors for details. Server: Msg 8944, Level 16, State 1, Line 1 Table error: Object ID 1010818663, index ID 0, page (1:305381), row 34. Test (offsetNull >= BASEOFFSET) failed. Values are 0 and 4.
I've just finished installing the Developer Edition of SQL Server 2005 over the Eval Edition. I'm happy to say that, despite a few hiccups, I seem to have everything running smoothly now. However, I have read about a few cases where, although it appeared the installation was successful, various components of the Eval Edition were not properly upgraded, the time limit was reached and the eval expired.
How can I confirm a full and successful installation of the Developer Edition? (Help... About only gives me version numbers, not "editions.")
Looking for opinions here on what is the best way to programmatically test that a password change to a credential has occurred successfully.
The password change was made using Alter Credential, and I can see in sys.credentials that the credential was updated by the tool that handles these updates. I would just like to be able to confirm that all of the credential updates were successful (in other words, they authenticate correctly) before anything starts to fail.
Assume that the number of SQL Servers is too great to manually check them even if the whole team worked on it together.
How can i confirm that the data entered within the standard controls and after the click event for the particular sql query the data is been stored in the database tables (depending insert,update,delete).I want to display the different messages on the click event and that after the changes made into the tables.How can i do it ?? I m using ASP.Net with C#,VB and the sql server to store data.I also want to know where are the database tables exactly get stored which are made in the Microsoft SQL Server Management Studio Express.I want to use as the existing item in .Net but could not find.. Thanxs...
During startup one of my servers, containing a default and a named instance of 2005, receives the following error.
Message Service Broker is disabled in MSDB or MSDB failed to start. Server level event notifications can not be delivered. Event notifications with FAN_IN in other databases could be affected as well.
The system databases for both instances were restored using backups from another instance. How do I confirm if Service Broker is enabled or disabled and why would I get this message? Is it due to restoring master or msdb?
I've just downloaded SQL Server Express (with advanced services) from both the main SQL Server Express website and from MSDN. When I right click on the exe I downloaded and go into properties the Product Version says SQLEVALVER. To me this implies it is an evaluation.
Can I confirm this is just a mistake and if we start to redistribute the product it won't timeout in the future? I am sure it is not an evaluation but just want to make absolutely sure.
Is there any way to restore a database of higher version to lower version.
E.g. I have created a database in sql server 2012, created some tables & procedures in that.I took Full backup of that database. Can I restore it to sql 2008r2 or any lower version.
I know direct restore is not possible, I have to use either import or export option or generating script,but i want to know is there any easy step to do so.
Since some analysis services features are only available in Enterprise version , I have to upgrade my SQL 2005 server from standard edition to enterpise edition.
So I uninstall originial standard version of analysis service and install a Enterprise version. However, the analysis service is still a standard version after installation.
Is it possible to keep data engine as standard version and install a enterprise version of analysis service?
Hello,I have been searching and reading a lots of information on the microsoft website about the different version of SQL server, but still can not make my decision.In term of performance, is there a real big difference between the workgroup and the standard version? The workgroup is limited to 3 GB of RAM while the standard is unlimited, would that really change the performance if my server has 16Gb or RAM?The price difference is pretty substantial so if could only have to buy the workgroup , it would be better.One more question, regarding the type of licence, my server has 2 processors, could I avoid buying 2 licences and get the Server plus CAL instead. I am using this server to host 4 web-application running on SQL server. Each database is about 15 MB.Thanks in adavance for your advises.Arno
I am wondering if it is possible to change from SQL Server Enterprise Evaluation Version to Developer Version. The reason is because the Enterprise Evaluation version expires after 180 days. So if I create reports and cubes in Enterprise Evaluation I can import them into Developer Edition right? Should I remove the Enterprise Evaluation version after 180 days or leave it then install Developer Edition?
I have tried to attatch a database ,created by SQL server Express within a C# application , in SQL server 2005 Enterprise edition, but the following error message appears:
-----------------------------
TITLE: Microsoft SQL Server Management Studio ------------------------------
Attach database failed for Server 'MEDO'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft SQL Server&ProdVer=9.00.1187.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach database+Server&LinkId=20476
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
The database 'E:X.MDF' cannot be opened because it is version 611. This server supports version 607 and earlier. A downgrade path is not supported. Could not open new database 'E:X.MDF'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 948)
------------------------------
so , how can I solve this problem , I need to reed the data resides in the tables of 'X' database , how can I do it?? please help me.
I have an ssis package that downloads a SQL Server 2000 database and restores it to a SQL 2005 server. Ninety-five percent of the time it runs just fine, but every so often the job fails and I get the following set of error messages in the log file. (I have had to delete some of the proprietary information for this message to satisfy my boss like putting in [Database name] in place of the actual name of the database in the error message).
OnError, Restore backup file to DB,,,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,Converting database [Database name] from version 539 to the current version 611. OnError,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,Converting database [Database name] from version 539 to the current version 611. OnError,Restore backup file to DB,,,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,Database [Database name] running the upgrade step from version 539 to version 551. OnError,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,Database [Database name] running the upgrade step from version 539 to version 551. OnError,Restore backup file to DB,,,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,The transaction log for database [Database name] is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases OnError,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,The transaction log for database [Database name] is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases OnError,SQL5,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,RESTORE could not start database [Database name]. OnError,SQL5,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,RESTORE could not start database [Database name]. OnError,SQL5,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,-1073548784,0x,Executing the query "RESTORE DATABASE [Database name] FROM DISK = '[Path to back up file]' WITH REPLACE, MOVE 'ASP_Live_Data' TO [Path to MDF file], MOVE 'ASP_Live_Log' TO [Path to LDF file]" failed with the following error: "RESTORE DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. OnError,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,-1073548784,0x,Executing the query "RESTORE DATABASE [Database name] FROM DISK = '[Path to backup file]' WITH REPLACE, MOVE 'ASP_Live_Data' TO [Path to MDF file]', MOVE 'ASP_Live_Log' TO [Path to LDF file]" failed with the following error: "RESTORE DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. OnTaskFailed,Restore backup file to DB,,,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,(null)
I have received the error message "Package migration from version 8 to version 6 failed".I have developed a SSIS package with Visual Studio 2013 which gives me PackageFormatVersion of 8. I then deploy my package to the ssisdb catalog that is running on a SQL Server 2012, this works fine but when I try to execute the package the error arises…due to SQL Server 2012 has a PackageFormatVersion of 6 and it can’t run something that has a greater version.I haven’t seen any good solution for this but one that would work for me would be to upgrade the Integration Services Server from 2012 to 2014, leaving everything else in 2012 (database, ssms, ssas, ssrs).Would this solve the package format problem? Would I then be able to execute my packages in the ssisdb catalog?
Now, I checked and verified that my backup version of SQL Server is the same as the version installed on the computer I'm restoring too.
I have SQL Server on a production machine that I backed up and want to test a full restore on a dev machine to make sure it will work when I need it to.
Now that I've run the restore command on my tape backup and go to restart the SQL server service I receive:
Configuration block version 0 is not a valid version number. SQL Server is exiting. Restore the master database or reinstall.
I'm afraid I don't understand why this is happening. If the builds are the same, then shouldn't restoring the MASTER database have worked normally and I'd be able to restart the service now?
I have the trial version of SQL Server 2005 installed and have setup a couple of databases. This trial version will expire in another few weeks. I recently purchased a copy of the software and want to install it. Will I lose my databases, user info, etc? How do I go about installing without losing anything?
We have a 64bit os machine that we accidently loaded the 32 bit version of sql server on. We now want to upgrade it to 64 bit sql server, but we now have a production database on it. My understanding is that all I have to do is detach the production database, upgrade to 64bit sql server, then reattach the database. Is this really all I have to do?
I started this thread as the last attempt to sort the issue out.
I have an SSIS package that loads data from a .csv file into my database. It works fine on my developer machine. I start it programmatically or from Management Studio or from Visual Studio, and it works. Then I deploy it to the MSDB database on the computer on which it will have its final place. There again I can start it from Management Studio or from Visual Studio (using the source file), and it works. But when I start it programmatically, it just fails telling me:
Package Warnings: Package Errors: The version of component "****" (11773) is not compatible with this version of the DataFlow. Component "component "Derived Column" (13627)" could not be created and returned error code 0x80070005. Make sure that the component is registered correctly. The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "Flat File Source;Microsoft Corporation;Microsoft SqlServer v9; (C) 2005 Microsoft Corporation; All Rights Reserved; http://www.microsoft.com/sql/support;1". component "Agreement File" (11773) failed validation and returned error code 0xC0048021. One or more component failed validation. There were errors during task validation.
Maybe the source of the problem is that this machine is a 64-bit one, while the developer machine is 32-bit one. But why does the package run fine when I start it from Management Studio?
Can some one here give me more insight about how to upgrade a SQL Server 2005 Standard Version (32 bits) to a SQL Server 2005 Enterprise Version (32 bits) as default instance on a Windows 2003 enterprise OS (32 bits). I want to know what is the easist way and what is the safest way. May I preserve some settings I have for the STD version, or I have to start from strach again to configure the server? Is there any catches, anything I should have attention to (We are using heavily about CLR and fulltext indexing)?
Hi, Please help me in this problem... i am new to sql server.. i am using sql server version 8...(doesnot support function with retun values..) so i have created a procedure... -----------procedure------------------(to find next monday after 6 months)------------------- [code] create proc next_Monday ( @myDate DATETIME ) as BEGIN set @myDate = dateadd(mm, 6, @myDate) while datepart(dw,@myDate) <> 2 begin set @myDate = dateadd(dd, 1, @myDate) end select @myDate end go [/code] -------------------------------------------------------- i can able to execute this procedure separately.... working well... but don't know how to call it inside another query.... the following throws error.... select smaster.sname, smaster.Datex, 'xxx'=(execute next_monday smaster.Datex) from smaster please help me... how to fix this problem...
Hello, I installed the SQL Server 2k EnterPrise version and developer version on the same version, and the developer version is an instance "Development". How do I expose both of them to internet? Just open both of them to port 1433? And on the client side, just say IP and IP/Development? Do I need specific set up, will they conflict? Thanks,
The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'C.0.8.54'. the expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights. I'm getting this whenever try to access the report server via SSMS, I have tried to upgrade via the Reporting Service Configuration Manager but get an error message similar to above except it says: The database version (C.o.8.54) does not match your Reporting Services installation. This version of the database cannot be upgraded. You must use a different database. Has anyone seen this before? I can create a new database, but don't want to loose all my reports. Any ideas. Oh, not even sure if the backups exist from before this error, I've spent 2 weeks trying to get access to the server so I could try to upgrade, only to get the above results. Thanks for your help, David
I downloaded the 101 Samples installation (i.e. 101SamplesCS.msi) from Microsoft's website, which contains SQL Server database files.
While working with the databases in the "Data Access" samples from the 101 Samples projects, I get the following error:
"Database <mdf_name> cannot be upgraded because its non-release version (600) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database..."
I assume the database files were created with a beta or CTP version of SQL Server 2005. Does anyone know where I can get an updated version of these database files or scripts to update them?
Can I set up sql server 7.0 standard version in cluster enviorment, what the different betwent sql server 7.0 enterprise version and standard version? any problem I may encouter when I install the SQL server 7.0 standard version in Cluster enviorment? Thank you very much. Judy
We have a Sqlserver 2005 Installed on One of our servers.I wanted to know whether the installed database is a Evaluation copy or Licensed Copy.How to Evaluate this. Do we have to check any Log files etc for knowing whether it is evaluation copy or Licensed copy. Please help me Asap. thanks in Advance
Does anyone know how to get SQL Server versions, Service pack versionsand the Server that instance of SQL is running on a network. I haveseen some threads on how to list SQL servers in a network but I need tofind more info about these SQL servers.Any help appreciated..!Thx...
we have a backup of a database from a release version with version number 9.00.1399 and we wanted to restore it to a server with version number (9.00.1116) CTP release. we were issued a version incopatibility message. is it possible to backup from a 9.00.1399 release with a backup file compatible for a CTP release, is there an available option during backup? thanks!