FOR XML Works Differently Between Developer And Enterprise Edition In SQL 2005
Jun 22, 2007
If I run the same FOR XML query in a Development edition enviornment and a Enterprise Edition environment, the results are different. The query is exactly the same.
Here is the query:
DECLARE @MessageBody XML
DECLARE @AuditTable SYSNAME
DECLARE @SendTrans BIT
DECLARE @SendAudit BIT
DECLARE @RecordCount INT
DECLARE @OperationType CHAR(1)
SET @RecordCount = @@ROWCOUNT
SET @OperationType = 'U'
SET @SendTrans = 1
SET @SendAudit = 1
SET @AuditTable = 'States'
SELECT @MessageBody = (
SELECT * FROM
(
SELECT TOP 10
'INSERTED' AS ActionType, @SendTrans AS SendTrans, @SendAudit AS SendAudit,
COLUMNS_UPDATED() AS ColumnsUpdated, GETDATE() AS AuditDate,
@AuditTable AS AuditTable, 'test' AS UserName, @RecordCount AS RecordCount, *
FROM l_states
)AuditRecord
FOR XML AUTO, ROOT('AuditTable'), BINARY BASE64)
SELECT @MessageBody
In my DEV env (Developer Edition), this result is produced:
<AuditTable>
<AuditRecord ActionType="INSERTED" SendTrans="1" SendAudit="1" AuditDate="2007-06-22T15:43:12.497" AuditTable="States" UserName="test" RecordCount="1" StateAbbreviation="AK" State="Alaska" />
<AuditRecord ActionType="INSERTED" SendTrans="1" SendAudit="1" AuditDate="2007-06-22T15:43:12.497" AuditTable="States" UserName="test" RecordCount="1" StateAbbreviation="AL" State="Alabama" />
</AuditTable>
In my Enterprise Edition evn, this is the result:
<AuditTable>
<AuditRecord ActionType="INSERTED" SendTrans="1" SendAudit="1" AuditDate="2007-06-22T15:44:48.230" AuditTable="States" UserName="test" RecordCount="1">
<l_states StateAbbreviation="AK" State="Alaska" />
<l_states StateAbbreviation="AL" State="Alabama" />
</AuditRecord>
</AuditTable>
Does anyone have any idea what might be wrong? Any help is greatly appreciated.
Tim
Is it possible to connect SSRS running on SQL Server 2005 enterprise edition (our production system) to a database running on SQL Server 2005 Developer's edition (our test system)
We have an existing installation of SQL Server 2005 Developer Edition (64bit) that we are ready to go live with and would like to change the edition to Enterprise Edition (64bit). We have purchased all the appropriate licenses. We would like to avoid UN-installing the Developer Edition and RE-installing the Enterprise Edition. There must be some way to change a registry key, provide your serial number via a command line utility or re-run the setup with the license key provided and direct it to just change the edition from Developer to Enterprise and not change any of the other settings like service account, sa account, collation, etc. Any help is most appreciated.
I'm trying to register a developer's 2000 pc from my 2005 pc.
i'm not sure this is even something possible from Dev Edition to Dev Edition- I can register a 2000 server just fine.
I can ping him. Both our systems have remote access 'on'. His server is (local), i've tried connecting to it by just entering his machine name and by using just the ip address. The error I get is "timeout expired. The timeout elapsed prior to completion of the operation or the server is not responding."
Am I just not registering this properly? I entered just the ip address in the 'server' box. I am connecting as sa with the pw he gave me. When i connect to my server, I use the ip addressinstance. However, I am not sure what to use for the instance when all I see when I look at his machine is (local).
I have made my website using SQL Server Express edition. It is totally database driven and manypages use databases to display data. My problem is that after paying for webhosting fees my web host told me that they do not support SQL Server express edition. Instead they have support for MySQL and Ms Access. Except that there is this MS 2000 Database service for an additional cost. Any recommendations what I should do except changing the host? If I pay for MS 2000 Database servicem, will my website work? My user management(i.e ASPNETDB database) was created by Visual Web developer and I don't want to do user management myself. Any advice?
We have 2005 Standard Edition in our production environment and 2005 Developer Edition in dev. Recently we started using a feature in dev only to realize it was an Enterprise specific feature when we wanted to move it to prod. Is there any way to turn off the enterprise features in developer edition so it behaves just like standard edition?
I am currently using SQL Server Enterprise Evaluation which runs out after 6months. When this happens or even sooner I plan to install SQL Server Developer.
My questions is can I copy all the things I develop (databases, cubes, reports,) from enterprise evaluation & import/load them into SQL Developer with no problems? Will everything integrate? Is there any implications?
Hi I am interested in taking MCTS exam 70-431 for sql server 2005 implementation and maintainance. I have been reading the hardware requirements for the instalation of sql server versions and realise that enterprise and developer editions have same minimum requirements for the operation system. I understand that the Developer Edition includes all the functionality of SQL Server 2005 Enterprise Edition, but it is licensed for use as a development and test system, not as a production server.
Also I undestand that the developer edition supports the Windows XP Home Edition with SP2 or later but the enterprise edition does not support this operating system. The evaluation/trial version is for the enterprise edition. Can I use the developer version of sql server 2005 for my practice exercises instead of using the trial version? I have all hardware requirements for the trial enterprise version except that I am using Microsoft windows Xp home edition version 2002 with SP2. I am trying to see if I can use the developer version of sql server 2005 as it is cheaper for me to buy this software than buying the new operating system for my computer. According to the microsoft book for the MCTS exam 70-431 there is a section which states that before you begin you should have Microsoft Windows Server 2003 running on your computer on an NTFS file system (NTFS) partition. Will I still be ok to use the book and be able to do all the tests in the book if i am using the developer version of sql server 2005 with my Microsoft windows Xp home edition than using the trial version which comes with the book?
As an ISV, I want to certify my product on Standard Edition. I am using Developer Edition everywhere. Is there a way I can do the certification using the Developer Edition, or do I need to obtain/purchase a copy of the Standard Edition?
I tried to download PerformancePoint Server Trial Version to ther server today and I got to the configuration point of the Analysis Services Setting, and when I clicked next to proceed with the configuration I got a popup error message: "Microsoft Analysis Server must be Evaluation, Developer or Enterprise Edition".
Now I have SQL Server 2005 Developer Edition Disc (Bought it with Visual Studio 2005) but on the server I have SQL Server 2005 Standard Edition, if I try to run the sql server developer Edition disc, I use the wizard download and it seems that the download is going through the SQL Server entire download, it's like I'm re-downloading SQL Server all over again.
Does that seem right? what is the best approach to work around this probelm?
because we installed the SQL Server 2005-64Bit Developer Edition on a 2003 Server R2-64Bit with 10GB RAM an 2 Xeon. Now we have huge performance problems wich should be better using the Stadard Edition...
I don't know if it is easily possible to upgrade by only inserting the DVD and start the Setup...
The following code does not function if I use SQLOLEDB if I omit the provide and default to ODBC OLE DB it works correctly. I am assume I am coding something wrong for a SQLOLEDB provide. Any help is greatly appricated.
VB Code
Public Function SqlExecuteResult(xSQL As String, sServer As String, sDatabase As String, sUserName As String, sPassword As String, sCaller As String, Optional bLog As Boolean = False) As Object
Dim oDB As Object Dim oRS As Object
Set oDB = CreateObject("adodb.connection") Set oRS = CreateObject("adodb.recordset")
Private Sub Form_Load() Dim rs As Object Set rs = SqlExecuteResult("exec NextEntry 'SentMessages'", "surecomp-bob", "pmsureus33", "sa", "", "") MsgBox rs.fields(0) End Sub
SQL proceedure
CREATE PROCEDURE NextEntry @CounterName Varchar(20) AS
begin declare @counter int select @counter = counter from counters where countername = @counterName select @counter = @counter + 1 update counters set counter = @counter where countername = @countername select counter from counters where countername = @counterName End GO
Hi -I have istalled sql server 2005 standard edition , I want to install sql server 2005 enterprise edition on the same machine. Is it possible? I have Microsoft windows server 2003 SP2 and 1GB RAM. I want to use partition function with the enterprise edition, will the trial version of sql server work for me? -If I have already created a database and tables using the standard edition, will I be able to access and use the database using the installed trial version or will I have to start a fresh creating a new database? - Is it possible to access the same database with any of the installed versions?
BTW, I am prety new to sql server and databases , I am trying to learn by myself
Dear All,We have a database which contains many tables which have millions ofrecords. When We attach the database with MS SQL Server 2005 StandardEdition Server and run some queries (having joins, filters etc.) thenthey take very long time to execute while when We execute same querieson Enterprise Edition then they run 10 times faster than on standardedition.Our database does not use any features which are present in EnterpriseEdition and not present in Standard Edition. We want to know what arethe differences between Standard Edition and Enterprise Edition forperformance. Why should we go for Enterprise Edition when StandardEdition has all the features required.We are presently using evaluation versions of SQL Server 2005 Standardand Enterprise Editions.Thanks and regards,Nishant Sainihttp://www.simplyjava.com
I am attempting to upgrade a 2005 Standard Edtion to Enterprise Edition. This is a default instance. All components are upgraded successfully except the Database Engine. I receive the following error:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]The certificate cannot be dropped because one or more entities are either signed or encrypted using it.. To continue, correct the problem, and then run SQL Server Setup again.
This installation does not have encryption enabled, so I do not undersand the error or how to correct it.
After rebooting the SQL instance appears to be upgraded to Enterprise, but it cannot be upgraded to SP2.
Hi all--I'm researching the cleanest downgrade path from a trial edition of SQL Server 2005 Enterprise to a licensed Standard Edition copy. It looks like downgrading will entail uninstalling the old version and installing the new version, but I'd like to save the original setup as much as possible. Detaching the old databases will preserve the non-system databases; what method would work best for restoring the system databases?
I develop for a number of clients, and rely on DTS in SQL Server 2000 to transport schemas and data to remote client databases.
I've been using the Express edition of the SQL Server 2005 Management Studio to access these databases lately, but it does not have the DTS feature, which is horribly inconvenient when I need to add tables, etc to remote databases.
If I purchase the Developer Edition of SQL Server 2005, and install the Management Studio on my workstation (my development db is on another machine), will it give me full DTS support for remote databases, or is DTS limited to one db only?
I've searched MS and this obscure info doesn't seem to be there anywhere. Does anyone know this?
is it possible to install ms sql 2005 developer edition databse serveron window XP professional version 2002 with SP2 or just allows installclient version?
I am currently downloading the mega-sized files for SQL Server 2005 Express Edition and was wondering if I was going to be able to install it onto my workstation alongside the SQL Server 2005 Developer Edition? Was hoping someone could advise. I did browse for an answer, but have not come across it yet. I know I'll find out once my download is complete, but that could be awhile :)
Everytime I open SQL Server Studio Management I recieve the below error. I've un-installed and reinstalled but it continues to come back. I cna continue on and it'll work kind of, but after a while it'll jsut crash on me normally when I'm trying to save a script or create a new DB. Sql Server 2000 is installed on the same machine so I'm wondering if I can have them both installed like this. Has any one seen this one?Bruce See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text **************System.IO.IOException: Cannot create a stable subkey under a volatile parent key. at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str) at Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, RegistryKeyPermissionCheck permissionCheck, RegistrySecurity registrySecurity) at Microsoft.Win32.RegistryKey.CreateSubKey(String subkey) at Microsoft.SqlServer.Management.UI.ConnectionDlg.RegisteredServersUtils.CreateKeyValueIfNotExist(String regPath, String keyName) at Microsoft.SqlServer.Management.UI.ConnectionDlg.RegisteredServersUtils.RegisterLocalInstancesIfFirstTimeUser() at Microsoft.SqlServer.Management.UI.ConnectionDlg.ConnectionDialog.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ContainerControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies **************mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll----------------------------------------AppIDPackage Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/AppIDPackage.DLL----------------------------------------System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll----------------------------------------Microsoft.SqlServer.SqlTools.VSIntegration Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.SqlTools.VSIntegration.DLL----------------------------------------Microsoft.VisualStudio.Shell.Interop Assembly Version: 7.1.40304.0 Win32 Version: 7.0.4054 CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll----------------------------------------Microsoft.VisualStudio.OLE.Interop Assembly Version: 7.1.40304.0 Win32 Version: 7.0.4054 CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll----------------------------------------System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll----------------------------------------System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll----------------------------------------Microsoft.SqlServer.SqlTDiagM Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlTDiagM/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SqlTDiagM.dll----------------------------------------Microsoft.DataWarehouse.SQM Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL----------------------------------------Microsoft.SqlServer.Instapi Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll----------------------------------------ObjectExplorer Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ObjectExplorer.DLL----------------------------------------ConnectionDlg Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ConnectionDlg.DLL----------------------------------------Microsoft.SqlServer.RegSvrEnum Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.RegSvrEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.RegSvrEnum.dll----------------------------------------Microsoft.SqlServer.CustomControls Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.CustomControls/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.CustomControls.dll----------------------------------------SqlWorkbench.Interfaces Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlWorkbench.Interfaces.DLL----------------------------------------Accessibility Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll----------------------------------------SqlMgmt Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlMgmt.DLL----------------------------------------SQLEditors Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SQLEditors.DLL----------------------------------------Microsoft.VisualStudio.TextManager.Interop Assembly Version: 7.1.40304.0 Win32 Version: 7.0.4054 CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.TextManager.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.TextManager.Interop.dll----------------------------------------System.Data Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll----------------------------------------Microsoft.SqlServer.ConnectionInfo Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.ConnectionInfo/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.ConnectionInfo.dll----------------------------------------EnvDTE Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC/EnvDTE/8.0.0.0__b03f5f7f11d50a3a/EnvDTE.dll----------------------------------------Microsoft.SqlServer.SqlEnum Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SqlEnum.dll----------------------------------------Microsoft.ReportViewer.WinForms Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.42 CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.ReportViewer.WinForms/8.0.0.0__b03f5f7f11d50a3a/Microsoft.ReportViewer.WinForms.dll----------------------------------------Microsoft.NetEnterpriseServers.ExceptionMessageBox Assembly Version: 9.0.242.0 Win32 Version: 9.00.1399.00 CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.NetEnterpriseServers.ExceptionMessageBox/9.0.242.0__89845dcd8080cc91/Microsoft.NetEnterpriseServers.ExceptionMessageBox.dll----------------------------------------System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll---------------------------------------- ************** JIT Debugging **************To enable just-in-time (JIT) debugging, the .config file for thisapplication or computer (machine.config) must have thejitDebugging value set in the system.windows.forms section.The application must also be compiled with debuggingenabled. For example: <configuration> <system.windows.forms jitDebugging="true" /></configuration> When JIT debugging is enabled, any unhandled exceptionwill be sent to the JIT debugger registered on the computerrather than be handled by this dialog box.
Ive installed SQL server 2005 developer edition onto my pc but when I use management studio, the only server I get is SQLEXPRESS. I did install the express version just to check it out, whats happend to the developer edition ? Is this named SQLEXPRESS as well ? and has overwritten the express version ? Has anyone else experienced this ?
I am in the early stages of migrating an extensive Access 2003 application to C#/SQL Server. The client already has SQL Server 2005, whereas I am using SQL Server 2000 Developer Edition. It has worked fine for me, but I'd like to upgrade to SQL Server 2005 Developer Edition and have a couple of questions.
In Access 2000 I am always using Query Analyzer and Enterprise Manager. Are these features available in 2005 Develper Edition?
Can more than one user connect to SQL Server at a time? That is, for testing concurrency, etc, can two people connect at the same time?
Is these any restriction on connecting to SQL Srever from another computer or workstation? Again for testing, one or two other workstations would be fine.
Finally, what is the street price? I've seen this advertised for $ 47 where I would have expected far more than that.
Hi!<br><br>A larger SP runs ok in console. When called in VB NET 1.1, results get turncated and some thing don't run at all. The connection is ODBC. Small SP's run ok.<br><br>Is this default behavior or something common? Are there VB parameters to let a larger SP run without interruption?<br><br>-Bahman<br><br><br>
Hi, I'm not sure if this is where I should post this, but I'm trying to find out what the limitations of SQL Server 2005 Developer Edition (DE) are. I've gone through the Microsoft SQL Server site and they have very little information about the developer edition.Is there a connection limit for DE like 2000 did?
Will SQL Server 2005 developer edition and Visual Web Developer Express work on the same machine? One reviewer of SQL Server 2005 developer edition on amazon.com stated won't work on the same machine? Is this true?
Hi Everyone, Recently I installed Visual Studio 2005 which also installed SQL Express Edition with it. I then installed SQL Server 2005 Developer Edition and am now able to see two instances SQLEXPRESS and MSSQLERVER. I do not want to use the Express version anymore, Do I have to have the Express version running or can I have just the Developer Edition ? Please help, can't find any help on the SQL website! Thanks
i am trying to find it, the only thing the MS site shows is enterprise licensing. is the developer edition still going to be like $100 or whatever it was?
I am unable to successfully install SQL Server 2005 Developer edition here on a machine at work. Database service and client tools fails to install. I get the message that:"The computer running SQL Server setup does not meet the minimum system requirements for this SQL server release. Microsoft SQL Server is not supported by this operating system."
I am running Win XP pro sp2 with all the latest updates installed. What could be causing this and how do I fix it?
Hi I currently have this edition of SQL server on my laptop:
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
It is running on SQL Server Management Studio 2005.
I wish to upgrdade to Developer Edition (as my laptop won't support Enterprise as it's running on Windows XP).
I have some questions, which I would be grateful if somebody could help answering:
1- will all my database remain as they are? 2- Will I loose any functionality? 3- Will it upgrade or intstall a separate edition? 4- Can anybody recommend where to purchase Developer 2005 edition? 5- I currently have 2gb capped database limit on my version, will I get a no capped limit? 6- Will the 2gb Capped limit increase to uncapped once I install (i.e. can i use my previous 2gb database and add more data to above 2 gb)
The main issues are that I need an uncapped limit for my DB's and that I will keep my existing db's.