New SQL 2005 instance using 2000 engine?

Hello,
I installed SQL 2005 Standard on the same server (2K3) with SQL 2000. My named instance I installed is coming up with "Version 8.00.2039" in the Server Management Studio and will not let me restore a database back-up I made on a 2005 development workstation (I'm assuming it's because it's trying to use the 2000 engine instead of the 2005). Is there a way I can force this instance to use the 2005 engine rather than the 2000?

Thanks,

Steve

SQL 2005 will not use the 2000 engine.

It sounds like your connecting to the wrong instance, try running

select @.@.VERSION

you should see something like :

Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

for 2005.

To double check you connection string, e.g. your instance name. Try the following :

Run SQL Server 2005 Surface Area Configuration
Click "Surface Area Configuration for Services and Connections

You will see your SQL2005 Instances, expand the SQL instance, expand Database Engine, click Service.

Note the Display Name "In my instance its SQL Server (SQLEXPRESS)"

Run services.msc

Select the SQL server name from the display named noted above.

Select properties

Copy the Path to execute, in my instances its :

"c:\Program Files (x86)\Microsoft SQL Server\MSSQL.4\MSSQL\Binn\sqlservr.exe" -sSQLEXPRESS

Run this from a cmd line.

Look at the output, you looking for :

Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].

For me, I can connect on \\SERVERNAME\SQLExpress

for my SQL instance, eg not SQL Express I get :

Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ]

So, we have NO instance (MSSQLSERVER is the default), so to connect we just connect to \\SERVERNAME

Let me know if this helps.

Thanks

Steve

|||Yup, that was exactly what happened. I apparently created a 2000 instance instead of a 2005 instance in my late night stupor, and was convinced it was suppose to be 2005. =)

Thanks!|||

Yep, I have seen that done before, I have even seen someone rebuild a SQL server from stracth as they were convinced that somehow the instance was 'broke'

glad to be of help.

Steve

New server with SQL Server 2005 standard x64 crashing

We have new 64-bit server and SQL Server 2005 where we moved databases and
applications from a 32-bit server and SQL Server 2000. Since we have moved
the databases and application to the new server the server crashes and
reboots at an irregular interval. This reboot seems to always be proceeded
by the memory working set for SQL Server being paged out and available memory
going up by a large amount. This usually occurs hours before the server
crashes. The available memory stays high until the server crashes.
OS: Server 2003 Standard edition x64 Edition
Version 5.2.3790 Service Pack 2 Build 3790
Hardware: HP ProLiant DL380 G5 with two Dual core cpu's 3000 MHz.
4 GB of memory
SQL Server Standard Edition (64-bit) Version: 9.00.3054.00
Using the performance monitory we can see the memory event that proceeds the
reboot and have ruled out some likely candidates like the Anti-virus and
backup software. The reboots occur anywhere from less the 24 hours apart to
4 days.
Does anyone know of any problems with SQL Server Standard x64 and memory
problems?
Any suggestions on how to identify if SQL Server is the problem or help
identifying some other service or driver as the cause of this problem?
--
MarkI have found it helpful to set the maximum memory setting in SQL Server to
less than the total available on the server. Based on the amount of memory
on the server this max amount would from 512 MB to 1024 MB less than the
maximum installed memory amount.
"masmith" wrote:
> We have new 64-bit server and SQL Server 2005 where we moved databases and
> applications from a 32-bit server and SQL Server 2000. Since we have moved
> the databases and application to the new server the server crashes and
> reboots at an irregular interval. This reboot seems to always be proceeded
> by the memory working set for SQL Server being paged out and available memory
> going up by a large amount. This usually occurs hours before the server
> crashes. The available memory stays high until the server crashes.
> OS: Server 2003 Standard edition x64 Edition
> Version 5.2.3790 Service Pack 2 Build 3790
> Hardware: HP ProLiant DL380 G5 with two Dual core cpu's 3000 MHz.
> 4 GB of memory
> SQL Server Standard Edition (64-bit) Version: 9.00.3054.00
> Using the performance monitory we can see the memory event that proceeds the
> reboot and have ruled out some likely candidates like the Anti-virus and
> backup software. The reboots occur anywhere from less the 24 hours apart to
> 4 days.
> Does anyone know of any problems with SQL Server Standard x64 and memory
> problems?
> Any suggestions on how to identify if SQL Server is the problem or help
> identifying some other service or driver as the cause of this problem?
> --
> Mark
>|||> Does anyone know of any problems with SQL Server Standard x64 and memory
> problems?
I dont have a link at hand, but I am pretty sure that SP2 for SQL Server
fixes this issue. We had the same issue from time to time, and we ended up
setting the min and max memory usage for the sql server 1 GB lower than the
total amount of memory. I searched google, and found a site saying, that the
SP2 would fix this issue.
If you haven't installed SP2, then you should take a look at the bugfixes
for that - and maybe you can permanent fix the problem with that.
/Sjang

New Installation of SQL Server 2000

Hi,
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBA
Newbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com

New Installation of SQL Server 2000

Hi,
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBANewbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com

New Installation of Sql Server 2000

Hello Guru's, I need your help!

I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not supported on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New to SQL ServerUnless you paid over $20,000 for SQL Server, it is probably 32 bit. I think the 64 bit version of SQL server states in @.@.version that it is 64 bit, so if you do not see anything, you very likely have 32 bit.

You need SQL Server SP3 to run on Windows 2003 with no problems. Just download the patch, run it, and you should be all set.|||Thank You Very Much!!! :)

New Installation of SQL Server 2000

Hi,
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBANewbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com

New Install - Log Says Eval Expired, But It's Not an Eval

I have installed the standard edition of SQL2005 w Reporting Services on my XP Pro desktop. SQL2005 works fine, but SSRS will not. In the log, I see the message that the evaluation copy has expired--but the install is not an eval copy. I have tried uninstalling SQL Server a couple of times, but no change. Anyone know why this is happening?

What is the errors you are getting with trying to work with RS?

The message you see in the log file does not apply if you are installing any version except the Evaluation version.

|||Another log displays the message "object not set to instance of an object".

New Data Connection Problem in VS.NET 2005

I have all of the prerequisites installed:

- SQL Server 2005 Compact Edition

- Visual Studio 2005 SP1 (Standard Edition)

- SQL Server Management Studio Express SP2

When trying to add a new Compact Edition SQL DB data connection from within Visual Studio ("SQL Mobile", "SQL Compact...", etc.), nothing is available for it. I have Access, ODBC, SQL Server, SQL DB File, Oracle, and Other. Even when selecting other, there are no Compact/Mobile types available.

Please Help...I've been going crazy trying to get this option.

Thank you

Anybody? Anybody at all?|||

I guess you'll have to settle for me.

I too have had problems installing the lastest SP of Visual Studio (VS) which includes the latest SQL Server Compact Edition (SQLCe) binaries. The problem is that you must make sure that if you've installed any CTPs they must be scrubbed off first. So, assuming you've done that or never installed the beta CTPs (which were used to implement SQL Server Everywhere Edition), you need to first install VS 2005 SP1 from http://msdn2.microsoft.com/en-us/vstudio/bb265237.aspx. Next, you might also need to install the SQLCe MSI to get the bit installed in the GAC. These bits can be found here http://www.microsoft.com/sql/editions/compact/downloads.mspx. As shown in my EBook "Hitchhiker's Guide to SQL Server 2005 Compact Edition", you can also download the SDK but you should now see the SQL Server Compact Edition as one of the choices when creating a Data Connection.

hth

|||APipeDream

I am having the same problem - did you get anywhere with it ?
|||

No, that's the order I used already, and I don't have any CTPs installed. I also have the SDK installed.

|||

So am I.

I uninstalled/re-installed all componenets still no luck.

I found a solution:

I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.

|||

Gotta create a DDEX Provider?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1477140&SiteID=1

|||

I found a solution:

I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.

|||

Thanks This worked:

I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.

New Data Connection Problem in VS.NET 2005

I have all of the prerequisites installed:

- SQL Server 2005 Compact Edition

- Visual Studio 2005 SP1 (Standard Edition)

- SQL Server Management Studio Express SP2

When trying to add a new Compact Edition SQL DB data connection from within Visual Studio ("SQL Mobile", "SQL Compact...", etc.), nothing is available for it. I have Access, ODBC, SQL Server, SQL DB File, Oracle, and Other. Even when selecting other, there are no Compact/Mobile types available.

Please Help...I've been going crazy trying to get this option.

Thank you

Anybody? Anybody at all?|||

I guess you'll have to settle for me.

I too have had problems installing the lastest SP of Visual Studio (VS) which includes the latest SQL Server Compact Edition (SQLCe) binaries. The problem is that you must make sure that if you've installed any CTPs they must be scrubbed off first. So, assuming you've done that or never installed the beta CTPs (which were used to implement SQL Server Everywhere Edition), you need to first install VS 2005 SP1 from http://msdn2.microsoft.com/en-us/vstudio/bb265237.aspx. Next, you might also need to install the SQLCe MSI to get the bit installed in the GAC. These bits can be found here http://www.microsoft.com/sql/editions/compact/downloads.mspx. As shown in my EBook "Hitchhiker's Guide to SQL Server 2005 Compact Edition", you can also download the SDK but you should now see the SQL Server Compact Edition as one of the choices when creating a Data Connection.

hth

|||APipeDream

I am having the same problem - did you get anywhere with it ?
|||

No, that's the order I used already, and I don't have any CTPs installed. I also have the SDK installed.

|||

So am I.

I uninstalled/re-installed all componenets still no luck.

I found a solution:

I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.

|||

Gotta create a DDEX Provider?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1477140&SiteID=1

|||

I found a solution:

I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.

|||

Thanks This worked:

I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.

New Data Connection Problem in VS.NET 2005

I have all of the prerequisites installed:

- SQL Server 2005 Compact Edition

- Visual Studio 2005 SP1 (Standard Edition)

- SQL Server Management Studio Express SP2

When trying to add a new Compact Edition SQL DB data connection from within Visual Studio ("SQL Mobile", "SQL Compact...", etc.), nothing is available for it. I have Access, ODBC, SQL Server, SQL DB File, Oracle, and Other. Even when selecting other, there are no Compact/Mobile types available.

Please Help...I've been going crazy trying to get this option.

Thank you

Anybody? Anybody at all?|||

I guess you'll have to settle for me.

I too have had problems installing the lastest SP of Visual Studio (VS) which includes the latest SQL Server Compact Edition (SQLCe) binaries. The problem is that you must make sure that if you've installed any CTPs they must be scrubbed off first. So, assuming you've done that or never installed the beta CTPs (which were used to implement SQL Server Everywhere Edition), you need to first install VS 2005 SP1 from http://msdn2.microsoft.com/en-us/vstudio/bb265237.aspx. Next, you might also need to install the SQLCe MSI to get the bit installed in the GAC. These bits can be found here http://www.microsoft.com/sql/editions/compact/downloads.mspx. As shown in my EBook "Hitchhiker's Guide to SQL Server 2005 Compact Edition", you can also download the SDK but you should now see the SQL Server Compact Edition as one of the choices when creating a Data Connection.

hth

|||APipeDream

I am having the same problem - did you get anywhere with it ?
|||

No, that's the order I used already, and I don't have any CTPs installed. I also have the SDK installed.

|||

So am I.

I uninstalled/re-installed all componenets still no luck.

I found a solution:

I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.

|||

Gotta create a DDEX Provider?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1477140&SiteID=1

|||

I found a solution:

I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.

|||

Thanks This worked:

I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.

new custom flat file connection manager component

The standard flat file connection component does not handle flat files with different column counts on different rows. Since that's the type of file I have to read, I like to create a modified version of the flat file connection manager that can do this. I have found some info in how to create a connection manager. But I can't find anything that tels me how to build one that would be recognized by the flat file source dataflow component.

So how do you build an connection manager that can used by the standard flat file source component? Anyone ever did this or knows were to get the docs?

I know my problem is also solvable by reading the row into a single column and then using a script component to split them but that is not the solution I want.

The new connection manager is not going to solve this problem. The parsing logic is not part of the connection manager, it is part of the Flat File source adapter. You would need to build a new source, not connection manager.

Thanks,

Bob