Migrating from Acess 2003 to Sql server - Function Val()

Hi folks

I do a lot of work with address data. I have been using Acess 2003 as my database but now need to upgrade to SQL Server.

My queries have been making extensive use of the Val function to order my queries on address columns. A typical address column might be:

12 The Avenue .......

by using Order By Val(AddressCol) I can sort these rows in ascending house number.

I can't find anything in SQL Server that will acomplish this. Does anybody have any ideas.

Thanks

Paul

why do you need to reference the val() function? is there something in your column that you want to exclude?

Does: "order by AddressCol" in TSQL not accomplish what you want?

Migrating data from SQL Server 6.5 to SQL Server 2005

Hello,

I'm not very familiar to SQL Server, but I've to upgrade a DBMS from
V6.5 to V2005.

Quote:

Originally Posted by

>From the V6.5 I've got a backup file and a dump file (which seems to be

the same, at least it has the same size).

After installing V2005 - at another system - I could not find any
option to import a database from an old system, e.g. importing/reading
a dump file, backup file.

How can I migrate the data from V6.5 to V2005 ?

Is there a way to make an export - like in informix - which creates a
sql script including all data and definitions (all tables,views, stored
procedures, users, etc.) ?

Or can I connect directly V2005 to V6.5 and import the database this
way ?

Any help is appreciated.

Thanks a lot in advance.

Norbert(info.nrieger@.web.de) writes:

Quote:

Originally Posted by

I'm not very familiar to SQL Server, but I've to upgrade a DBMS from
V6.5 to V2005.
>

Quote:

Originally Posted by

>>From the V6.5 I've got a backup file and a dump file (which seems to be

the same, at least it has the same size).
>
After installing V2005 - at another system - I could not find any
option to import a database from an old system, e.g. importing/reading
a dump file, backup file.
>
How can I migrate the data from V6.5 to V2005 ?

There is only one tool in this world that can read a backup file from
SQL Server 6.5 and that's SQL Server 6.5. SQL Server underwent a complete
architecture change from 6.5 to SQL7, that's why. (Had you had a
backup from SQL 7, you could just have restored it on SQL 2005.)

So how do you get SQL 6.5? It used to be available on MSDN Subscriber
Downloads. I would expect that it still is, but it was a while since
I visited that site.

If you don't have an MSDN subscription that gives you access to downloads,
I suggest that you contact your local Microsoft office.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

migrating 7.0 to 2000

i have computer with windows 2000 an sql 7.0 (computerA)
goal is windows 2003 with sql 2005

I see my choices as is:

A) upgrade win2k to 2k3 then upgrade sql7 on w2k3 to sql2k5 on win2k3.
(i see many potential problems with that)

B) have computerB with clean install of win2k3 and install sql2k5 on it.
if this is the case, what is the best / easiest way to get the database from 7 to 2k5? Database copy wizard? dts? attaching the db?

Anything else I should lookout for ?

thnx,
vextThere might be better answers, but I'd set up the new server with the software that you intend to run on it (Windows 2003, SQL 2005). I'd backup the existing database, and restore that backup onto the new server.

-PatP|||what is the actual difference between using the Database copy wizard and Restoring a backup? and is the datafile still the same structure in 2005? will the restore upgrade if not?|||Theoretically, there shouldn't be a difference between Restoring a Backup and Copying a Database. That leads to all kinds of amusing observations, but I'll behave myself (at least for now). The primary difference is that restoring a backup is logically much more "solid" in that there are far fewer ways for it to go wrong...

The Copy Database Wizard is free to make many assumptions, many of which have a significant impact on performance and operational simplicity. These assumptions should not affect the copy of the quality, but I'm often unpleasantly surprised by them.

Restoring a backup is much less problematic for me. While some things (features, objects, etc) might change due to the difference in software releases (SQL 7 to SQL 2005 is a big jump), at least in my experience there will be far fewer surprises than you'd get via the Copy Database Wizard.

-PatP|||understood.

thnx for the input. I will do a restore when the time comes. thnxsql

Migrate w/o upgrade wizard

Hello,
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
Many thanks,
Pablo
Hi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>

Migrate w/o upgrade wizard

Hello,
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
--
Many thanks,
PabloHi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>

Migrate w/o upgrade wizard

Hello,
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
Many thanks,
PabloHi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>sql

Migrate Higher version of MDAC

Hi Friends,

I have a system with windows 2000 advanced server SP4 OS. In that system, How can i upgrade MDAC version from 2.5 to 2.8 sp2.

This is use of,

I am going to install sql server 2005 express edition advanced services SP2.

Please help me, how can i upgrade higher version of MDAC?

Thanks in Advance

Rameshkumar Thirumalaisamy

You just download the version you want from the Microsoft Download Center and install it. I believe that MDAC 2.8 is currently at SP1, not SP2 as you've indicated. You can find MDAC 2.8 SP1 here.

Mike

|||

Actually, if you install the SQL Server 2005 on the machine you can connect using the SNAC provider instead of using the MDAC stack. Although you should be up-to-date in the case another application needs parts of the MDAC stack.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

When installing SQL Server 2005 (any edition) on Windows 2000 there actually is a minimum version of MDAC that is required, although I can't recall what version is required, but 2.8 SP1 will certainly qualify since it's the newest. I don't know why this requirement exists only on Windows 2000.

Mike

Migrate Higher version of MDAC

Hi Friends,

I have a system with windows 2000 advanced server SP4 OS. In that system, How can i upgrade MDAC version from 2.5 to 2.8 sp2.

This is use of,

I am going to install sql server 2005 express edition advanced services SP2.

Please help me, how can i upgrade higher version of MDAC?

Thanks in Advance

Rameshkumar Thirumalaisamy

You just download the version you want from the Microsoft Download Center and install it. I believe that MDAC 2.8 is currently at SP1, not SP2 as you've indicated. You can find MDAC 2.8 SP1 here.

Mike

|||

Actually, if you install the SQL Server 2005 on the machine you can connect using the SNAC provider instead of using the MDAC stack. Although you should be up-to-date in the case another application needs parts of the MDAC stack.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

When installing SQL Server 2005 (any edition) on Windows 2000 there actually is a minimum version of MDAC that is required, although I can't recall what version is required, but 2.8 SP1 will certainly qualify since it's the newest. I don't know why this requirement exists only on Windows 2000.

Mike

Microsoft SQL Server Upgrade Wizard

I need to convert from SQL Server 7 to 2000 and I have the 2000 installation
media - but where do I find the Microsoft SQL Server Upgrade Wizard ? Is it
included in the installation cd? or do I need to get a different product?Are you installing on a new server or upgrading an existing SQL 7 box?
In either case, you should have the option to install the upgrade wizard =
during the installation.
Moving databases from SQL7 to SQL2k is easy -- simply back them up and =
restore them to the 2k box. Note: it is not possible to go the other =
way! (at least not with BACKUP and RESTORE).
--=20
Keith
"confused" <anonymous@.discussions.microsoft.com> wrote in message =
news:44F65E3A-8EC2-45C5-8E1B-23B9868DF4D1@.microsoft.com...
> I need to convert from SQL Server 7 to 2000 and I have the 2000 =
installation media - but where do I find the Microsoft SQL Server =
Upgrade Wizard ? Is it included in the installation cd? or do I need to =
get a different product?

Microsoft SQL Server Setup Support Files (English) -- Installation failed

I'm trying in vain to upgrade sql server 2000 to 2005 with great headache and pain.

I (finally) have removed all Beta, and other incompatible version of .NET, Visual Studio and any other offending components, and made it to the first page of the install shield.

The .NET 2.0 components installed fine - but I get a fatal error trying to install the SQL Server Set Support Files.

I do have a log file - and have tired searching on the various error codes in it, but am coming up blank. Please advise - this is taking forever!

sample of error msgs in log file:

MSI (s) (B0:E0) [12:33:06:613]: Note: 1: 1935 2: 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.NetEnterpriseServers.ExceptionMessageBox,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:613]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.

MSI (s) (B0:E0) [12:33:06:613]: Executing op: ComponentRegister(ComponentId={52723CBD-3400-458C-988A-4D012E6CAEDB},KeyPath=<\Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0",State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.
MSI (s) (B0:E0) [12:33:06:629]: MSCOREE not loaded loading copy from system32
MSI (s) (B0:E0) [12:33:06:629]: Assembly Error:Function not defined in specified DLL.

MSI (s) (B0:E0) [12:33:06:629]: Note: 1: 1935 2: {52723CBD-3400-458C-988A-4D012E6CAEDB} 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:629]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}

Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}
MSI (s) (B0:E0) [12:33:06:629]: User policy value 'DisableRollback' is 0
MSI (s) (B0:E0) [12:33:06:629]: Machine policy value 'DisableRollback' is 0
Action ended 12:33:06: InstallFinalize. Return value 3.

mandpenny

Please read this blog and see if it helps with the problem.

http://blogs/jdbaker/archive/2006/04/20/10684.aspx

|||

Thanks for the reply Raja, but I can't get to that URL - pg. cannot be displayed error...

Mandy

|||

I had a similar problem - removing the beta version of SQL Native Client (which came with the 2005 CTP) fixed it

Dave

Microsoft SQL Server Setup Support Files (English) -- Installation failed

I'm trying in vain to upgrade sql server 2000 to 2005 with great headache and pain.

I (finally) have removed all Beta, and other incompatible version of .NET, Visual Studio and any other offending components, and made it to the first page of the install shield.

The .NET 2.0 components installed fine - but I get a fatal error trying to install the SQL Server Set Support Files.

I do have a log file - and have tired searching on the various error codes in it, but am coming up blank. Please advise - this is taking forever!

sample of error msgs in log file:

MSI (s) (B0:E0) [12:33:06:613]: Note: 1: 1935 2: 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.NetEnterpriseServers.ExceptionMessageBox,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:613]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.

MSI (s) (B0:E0) [12:33:06:613]: Executing op: ComponentRegister(ComponentId={52723CBD-3400-458C-988A-4D012E6CAEDB},KeyPath=<\Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0",State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.
MSI (s) (B0:E0) [12:33:06:629]: MSCOREE not loaded loading copy from system32
MSI (s) (B0:E0) [12:33:06:629]: Assembly Error:Function not defined in specified DLL.

MSI (s) (B0:E0) [12:33:06:629]: Note: 1: 1935 2: {52723CBD-3400-458C-988A-4D012E6CAEDB} 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:629]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}

Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}
MSI (s) (B0:E0) [12:33:06:629]: User policy value 'DisableRollback' is 0
MSI (s) (B0:E0) [12:33:06:629]: Machine policy value 'DisableRollback' is 0
Action ended 12:33:06: InstallFinalize. Return value 3.

mandpenny

Please read this blog and see if it helps with the problem.

http://blogs/jdbaker/archive/2006/04/20/10684.aspx

|||

Thanks for the reply Raja, but I can't get to that URL - pg. cannot be displayed error...

Mandy

|||

I had a similar problem - removing the beta version of SQL Native Client (which came with the 2005 CTP) fixed it

Dave

Microsoft SQL Server Management Studio SP2 upgrade

Hi
Having an issue after sp2 install on SQl 2005. The problem I am having is
when I try to open the Maintenance Plans applet in system manager. I get the
following error:
TITLE: Microsoft SQL Server Management Studio
--
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
Invalid column name 'from_msx'.
Invalid column name 'has_targets'. (Microsoft SQL Server, Error: 207)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=207&LinkId=20476
--
BUTTONS:
OK
--
I do not see any of the previse jobs the only thing I get is this error.
Any help is appreciated.
Dell Poweredge 1950
Windows 2003 STD sp2
Intel Xeon 3.2
4.0 gb Ram
--
Joel Cavazos
Network Administrator
MCSE, MCSA, MCPDid you upgrade the client tools but not the server instance (database
services)?
--
Aaron Bertrand
SQL Server MVP
"jcavazos" <jcavazos@.discussions.microsoft.com> wrote in message
news:DE12769F-1002-48C7-8487-89753A36CC84@.microsoft.com...
> Hi
> Having an issue after sp2 install on SQl 2005. The problem I am having is
> when I try to open the Maintenance Plans applet in system manager. I get
> the
> following error:
> TITLE: Microsoft SQL Server Management Studio
> --
> Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> Invalid column name 'from_msx'.
> Invalid column name 'has_targets'. (Microsoft SQL Server, Error: 207)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=207&LinkId=20476
> --
> BUTTONS:
> OK
> --
> I do not see any of the previse jobs the only thing I get is this error.
> Any help is appreciated.
> Dell Poweredge 1950
> Windows 2003 STD sp2
> Intel Xeon 3.2
> 4.0 gb Ram
> --
> Joel Cavazos
> Network Administrator
> MCSE, MCSA, MCP|||Aaron
Going back thur the update summary log I did find that thier was a error in
the update process regarding the database services the error is:
----
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29534
Error Description : MSP Error: 29534 Service 'MSSQLSERVER' could
not be started. Verify that you have sufficient privileges to start system
services. The error code is (1067) The process terminated unexpectedly.
----
Sorry I totally missed this.
--
Joel Cavazos
Network Administrator
MCSE, MCSA, MCP
"Aaron Bertrand [SQL Server MVP]" wrote:
> Did you upgrade the client tools but not the server instance (database
> services)?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "jcavazos" <jcavazos@.discussions.microsoft.com> wrote in message
> news:DE12769F-1002-48C7-8487-89753A36CC84@.microsoft.com...
> > Hi
> >
> > Having an issue after sp2 install on SQl 2005. The problem I am having is
> > when I try to open the Maintenance Plans applet in system manager. I get
> > the
> > following error:
> >
> > TITLE: Microsoft SQL Server Management Studio
> > --
> >
> > Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
> >
> > For help, click:
> > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
> >
> > --
> > ADDITIONAL INFORMATION:
> >
> > An exception occurred while executing a Transact-SQL statement or batch.
> > (Microsoft.SqlServer.ConnectionInfo)
> >
> > --
> >
> > Invalid column name 'from_msx'.
> > Invalid column name 'has_targets'. (Microsoft SQL Server, Error: 207)
> >
> > For help, click:
> > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=207&LinkId=20476
> >
> > --
> > BUTTONS:
> >
> > OK
> > --
> >
> > I do not see any of the previse jobs the only thing I get is this error.
> > Any help is appreciated.
> >
> > Dell Poweredge 1950
> > Windows 2003 STD sp2
> > Intel Xeon 3.2
> > 4.0 gb Ram
> > --
> > Joel Cavazos
> > Network Administrator
> > MCSE, MCSA, MCP
>
>

Microsoft SQL Server Management Studio SP2 upgrade

Hi
Having an issue after sp2 install on SQl 2005. The problem I am having is
when I try to open the Maintenance Plans applet in system manager. I get th
e
following error:
TITLE: Microsoft SQL Server Management Studio
--
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
Invalid column name 'from_msx'.
Invalid column name 'has_targets'. (Microsoft SQL Server, Error: 207)
For help, click:
http://go.microsoft.com/fwlink?Prod...07&LinkId=20476
BUTTONS:
OK
--
I do not see any of the previse jobs the only thing I get is this error.
Any help is appreciated.
Dell Poweredge 1950
Windows 2003 STD sp2
Intel Xeon 3.2
4.0 gb Ram
--
Joel Cavazos
Network Administrator
MCSE, MCSA, MCPDid you upgrade the client tools but not the server instance (database
services)?
Aaron Bertrand
SQL Server MVP
"jcavazos" <jcavazos@.discussions.microsoft.com> wrote in message
news:DE12769F-1002-48C7-8487-89753A36CC84@.microsoft.com...
> Hi
> Having an issue after sp2 install on SQl 2005. The problem I am having is
> when I try to open the Maintenance Plans applet in system manager. I get
> the
> following error:
> TITLE: Microsoft SQL Server Management Studio
> --
> Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> Invalid column name 'from_msx'.
> Invalid column name 'has_targets'. (Microsoft SQL Server, Error: 207)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...07&LinkId=20476
> --
> BUTTONS:
> OK
> --
> I do not see any of the previse jobs the only thing I get is this error.
> Any help is appreciated.
> Dell Poweredge 1950
> Windows 2003 STD sp2
> Intel Xeon 3.2
> 4.0 gb Ram
> --
> Joel Cavazos
> Network Administrator
> MCSE, MCSA, MCP|||Aaron
Going back thur the update summary log I did find that thier was a error in
the update process regarding the database services the error is:
----
--
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB92189
6_sqlrun_sql.msp.log
Error Number : 29534
Error Description : MSP Error: 29534 Service 'MSSQLSERVER' could
not be started. Verify that you have sufficient privileges to start system
services. The error code is (1067) The process terminated unexpectedly.
----
--
Sorry I totally missed this.
--
Joel Cavazos
Network Administrator
MCSE, MCSA, MCP
"Aaron Bertrand [SQL Server MVP]" wrote:

> Did you upgrade the client tools but not the server instance (database
> services)?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "jcavazos" <jcavazos@.discussions.microsoft.com> wrote in message
> news:DE12769F-1002-48C7-8487-89753A36CC84@.microsoft.com...
>
>