HELP! Unable to select database engine in management studio

Hi All,

I am new to SQL Server and having trouble using SQL Server Management Studio. I am unable to select the Database Engine in management studio.

I am able to see the instance of default database engine (MSSQLServer) running in Reporting Services manager as well as in Surface area configuration manager, but it is not visible in the drop down list in Management Studio's "Select Database Engine" menu.

I had removed Sql server 2005 earlier ( I was able to select the database engine in Management Studio then). But when I installed it again, I was unable to install the Sql Server Tools (it said that my Upgrade is blocked). So, I cleaned the Windows Registry of all keys containing 'Sql'. After this I tried installing it again and successfully installed Sql Server 2005 + ALL TOOLS. But this time I am unable to select the database engine in management studio.

Thanks and Regards to ALL

You may need to rebuild the machine from scratch. Did you install any beta version of the 2.0 framework? If so a complete rebuild of the machine may be required.|||

Hi TATWORTH,

Thanks for the reply.

I may not wish to rebuild the machine as it is a triple boot system with 2000/xp/suse 10.1. If I reinstall XP, I may have to reinstall linux...

Is there any alternative?

Regards

|||Try installing SQL Server again - not as a reinstall of the default instance but as a new instance.|||

Ok.

Will reinstall as a seperate instance and tell you.

Regards

Help! Unable to restore DB from SQL7 to SQL2000

Hi Good Day everybody,
Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
below:
Current Server (Server A)
a) Windows NT4 SP6a
b) SQL 7 + SP4
c) Default Collation: SQL_Latin1_General_CP1_CI_AS
d) Default Data Location: E:\MSSQL7
New Server (Server B)
a) Window 2000 Server SP4
b) SQL 2000 + SP3a
c) Default Collation: Latin1_General_CP1_CI_AS (required to set as default)
d) Default Data Location: D:\Program Files\Microsoft SQL Server
Authentication Mode:
a) Mixed Mode
b) SQL and Windows Authentication
* Both server are login with same userid and password.
Problem:
I have create and new user database "PA_CCCTemp" in the SQL2000 server.
Besides, I also backup user database "PA_CCC" from SQL7.
However, during I restore databases that I have backup into the SQL2000
server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
set holds a backup of a database other than the existing 'PA_CCCTemp"
database. Restore Databse is terminating abnormally.
I do not know what is the problem caused. Either the database is different
name, or the restoration location are different from the original place, or
the collation is different.
I also need help on how I can migrate the database from SQL7 to SQL 2000,
includes user id and logon password.
Regards,
Polar Bear
Hi,
It seems you have given a physical location which is not in the new server
(Drive and directory) while loading in SQL 2000.
Please follow the below steps in query analyzer:-
Restore filelistonly from disk='c:\backup\dbname.bak'
( replace the 'c:\backup\dbname.bak' with the actual backup file name with
path where the file resides.)
This will give you the Logical and Physical file names of the Backup file
name. While loading you should give the
correct logical file name and the place to keep the physical file. But
Physical file name can be a diffrent one.
Restore Database <dbname> from disk= 'c:\backup\dbname.bak' with
move 'logical_mdf_name' to 'c:\mssql\data\phys_data_name.Xmdf',
move 'logical_ldf_name' to 'c:\mssql\data\phys_log_name.lXdf'
(Replace the logical_mdf_name and logical_ldf_name with the logical name you
got from RESTORE FILELISTONLY command.
Ensure that the directory give in physical file name is there in the server)
Thanks
Hari
SQL Server MVP
Thanks
Hari
SQL Server MVP
"Polar Bear" <Polar Bear@.discussions.microsoft.com> wrote in message
news:227A549B-7D5A-48DA-A4F5-1850CE31B84B@.microsoft.com...
> Hi Good Day everybody,
> Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
> below:
> Current Server (Server A)
> a) Windows NT4 SP6a
> b) SQL 7 + SP4
> c) Default Collation: SQL_Latin1_General_CP1_CI_AS
> d) Default Data Location: E:\MSSQL7
> New Server (Server B)
> a) Window 2000 Server SP4
> b) SQL 2000 + SP3a
> c) Default Collation: Latin1_General_CP1_CI_AS (required to set as
> default)
> d) Default Data Location: D:\Program Files\Microsoft SQL Server
> Authentication Mode:
> a) Mixed Mode
> b) SQL and Windows Authentication
> * Both server are login with same userid and password.
> Problem:
> I have create and new user database "PA_CCCTemp" in the SQL2000 server.
> Besides, I also backup user database "PA_CCC" from SQL7.
> However, during I restore databases that I have backup into the SQL2000
> server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
> set holds a backup of a database other than the existing 'PA_CCCTemp"
> database. Restore Databse is terminating abnormally.
> I do not know what is the problem caused. Either the database is different
> name, or the restoration location are different from the original place,
> or
> the collation is different.
> I also need help on how I can migrate the database from SQL7 to SQL 2000,
> includes user id and logon password.
> Regards,
> Polar Bear
>

Help! Unable to restore DB from SQL7 to SQL2000

Hi Good Day everybody,
Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
below:
Current Server (Server A)
a) Windows NT4 SP6a
b) SQL 7 + SP4
c) Default Collation: SQL_Latin1_General_CP1_CI_AS
d) Default Data Location: E:\MSSQL7
New Server (Server B)
a) Window 2000 Server SP4
b) SQL 2000 + SP3a
c) Default Collation: Latin1_General_CP1_CI_AS (required to set as default)
d) Default Data Location: D:\Program Files\Microsoft SQL Server
Authentication Mode:
a) Mixed Mode
b) SQL and Windows Authentication
* Both server are login with same userid and password.
Problem:
I have create and new user database "PA_CCCTemp" in the SQL2000 server.
Besides, I also backup user database "PA_CCC" from SQL7.
However, during I restore databases that I have backup into the SQL2000
server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
set holds a backup of a database other than the existing 'PA_CCCTemp"
database. Restore Databse is terminating abnormally.
I do not know what is the problem caused. Either the database is different
name, or the restoration location are different from the original place, or
the collation is different.
I also need help on how I can migrate the database from SQL7 to SQL 2000,
includes user id and logon password.
Regards,
Polar BearHi,
It seems you have given a physical location which is not in the new server
(Drive and directory) while loading in SQL 2000.
Please follow the below steps in query analyzer:-
Restore filelistonly from disk='c:\backup\dbname.bak'
( replace the 'c:\backup\dbname.bak' with the actual backup file name with
path where the file resides.)
This will give you the Logical and Physical file names of the Backup file
name. While loading you should give the
correct logical file name and the place to keep the physical file. But
Physical file name can be a diffrent one.
Restore Database <dbname> from disk= 'c:\backup\dbname.bak' with
move 'logical_mdf_name' to 'c:\mssql\data\phys_data_name.­mdf',
move 'logical_ldf_name' to 'c:\mssql\data\phys_log_name.l­df'
(Replace the logical_mdf_name and logical_ldf_name with the logical name you
got from RESTORE FILELISTONLY command.
Ensure that the directory give in physical file name is there in the server)
Thanks
Hari
SQL Server MVP
Thanks
Hari
SQL Server MVP
"Polar Bear" <Polar Bear@.discussions.microsoft.com> wrote in message
news:227A549B-7D5A-48DA-A4F5-1850CE31B84B@.microsoft.com...
> Hi Good Day everybody,
> Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
> below:
> Current Server (Server A)
> a) Windows NT4 SP6a
> b) SQL 7 + SP4
> c) Default Collation: SQL_Latin1_General_CP1_CI_AS
> d) Default Data Location: E:\MSSQL7
> New Server (Server B)
> a) Window 2000 Server SP4
> b) SQL 2000 + SP3a
> c) Default Collation: Latin1_General_CP1_CI_AS (required to set as
> default)
> d) Default Data Location: D:\Program Files\Microsoft SQL Server
> Authentication Mode:
> a) Mixed Mode
> b) SQL and Windows Authentication
> * Both server are login with same userid and password.
> Problem:
> I have create and new user database "PA_CCCTemp" in the SQL2000 server.
> Besides, I also backup user database "PA_CCC" from SQL7.
> However, during I restore databases that I have backup into the SQL2000
> server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
> set holds a backup of a database other than the existing 'PA_CCCTemp"
> database. Restore Databse is terminating abnormally.
> I do not know what is the problem caused. Either the database is different
> name, or the restoration location are different from the original place,
> or
> the collation is different.
> I also need help on how I can migrate the database from SQL7 to SQL 2000,
> includes user id and logon password.
> Regards,
> Polar Bear
>sql

Help! Unable to restore DB from SQL7 to SQL2000

Hi Good Day everybody,
Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
below:
Current Server (Server A)
a) Windows NT4 SP6a
b) SQL 7 + SP4
c) Default Collation: SQL_Latin1_General_CP1_CI_AS
d) Default Data Location: E:\MSSQL7
New Server (Server B)
a) Window 2000 Server SP4
b) SQL 2000 + SP3a
c) Default Collation: Latin1_General_CP1_CI_AS (required to set as default)
d) Default Data Location: D:\Program Files\Microsoft SQL Server
Authentication Mode:
a) Mixed Mode
b) SQL and Windows Authentication
* Both server are login with same userid and password.
Problem:
I have create and new user database "PA_CCCTemp" in the SQL2000 server.
Besides, I also backup user database "PA_CCC" from SQL7.
However, during I restore databases that I have backup into the SQL2000
server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The back
up
set holds a backup of a database other than the existing 'PA_CCCTemp"
database. Restore Databse is terminating abnormally.
I do not know what is the problem caused. Either the database is different
name, or the restoration location are different from the original place, or
the collation is different.
I also need help on how I can migrate the database from SQL7 to SQL 2000,
includes user id and logon password.
Regards,
Polar BearHi,
It seems you have given a physical location which is not in the new server
(Drive and directory) while loading in SQL 2000.
Please follow the below steps in query analyzer:-
Restore filelistonly from disk='c:\backup\dbname.bak'
( replace the 'c:\backup\dbname.bak' with the actual backup file name with
path where the file resides.)
This will give you the Logical and Physical file names of the Backup file
name. While loading you should give the
correct logical file name and the place to keep the physical file. But
Physical file name can be a diffrent one.
Restore Database <dbname> from disk= 'c:\backup\dbname.bak' with
move 'logical_mdf_name' to 'c:\mssql\data\phys_data_name._mdf',
move 'logical_ldf_name' to 'c:\mssql\data\phys_log_name.l_df'
(Replace the logical_mdf_name and logical_ldf_name with the logical name you
got from RESTORE FILELISTONLY command.
Ensure that the directory give in physical file name is there in the server)
Thanks
Hari
SQL Server MVP
Thanks
Hari
SQL Server MVP
"Polar Bear" <Polar Bear@.discussions.microsoft.com> wrote in message
news:227A549B-7D5A-48DA-A4F5-1850CE31B84B@.microsoft.com...
> Hi Good Day everybody,
> Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
> below:
> Current Server (Server A)
> a) Windows NT4 SP6a
> b) SQL 7 + SP4
> c) Default Collation: SQL_Latin1_General_CP1_CI_AS
> d) Default Data Location: E:\MSSQL7
> New Server (Server B)
> a) Window 2000 Server SP4
> b) SQL 2000 + SP3a
> c) Default Collation: Latin1_General_CP1_CI_AS (required to set as
> default)
> d) Default Data Location: D:\Program Files\Microsoft SQL Server
> Authentication Mode:
> a) Mixed Mode
> b) SQL and Windows Authentication
> * Both server are login with same userid and password.
> Problem:
> I have create and new user database "PA_CCCTemp" in the SQL2000 server.
> Besides, I also backup user database "PA_CCC" from SQL7.
> However, during I restore databases that I have backup into the SQL2000
> server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The ba
ckup
> set holds a backup of a database other than the existing 'PA_CCCTemp"
> database. Restore Databse is terminating abnormally.
> I do not know what is the problem caused. Either the database is different
> name, or the restoration location are different from the original place,
> or
> the collation is different.
> I also need help on how I can migrate the database from SQL7 to SQL 2000,
> includes user id and logon password.
> Regards,
> Polar Bear
>

HELP! Cannot connect !

While I am connecting to SQL server 2000 EE from a
different client machine using Query Analyzer it gives me
the following error message .
Unable to connect to server >
Server : MSG 18452 Level 16 state 1
[Microsoft ODBC ][SQL Server Driver][SQL server] Login
failed for user '(null)' Reason , not associated with a
trusted SQL server connection.
I can connect to two other SQL servers in the same domain
just fine with QueryAnalyzer. The machine that I cannot
connect to is also my PDC. It is running Win2KSP4, the
client is WinXPSP1. I've added and removed the machine
from the domain (at my wits end) just to make sure the
accounts are not cached. This is the only computer I'm
having these client problems with, no matter who logs in.
SQL Server I cannot connect to using Windows Login is
also my PDC (Development environment)
I can connect to two other SQL servers that are member
servers on the same domain. All servers are running
SQL2000EE/SP3a MDAC 2.7SP1 on Win2K, including domain
controller.
I can log into the SQL server in question using sa
account from the client (which is running
XPSP1/SQL2000Tools/MDAC2.7FOR XP.
If I try to add databases using Enterprise Manager from
the client, I can add the other two DB servers, however I
get the same error when trying to add the SQL server in
question.
I'm stumped as the Windows Domain account has to be
working as I can authenticate to connect to the domain as
well as the other two SQL servers. (I've tried this with
a regular user account with SQL rights as well as my
domain admin account which has SQL rights.
I can connect to the server in question from any other
client in the office using the two windows domain
accounts that do not work on the client.
I'd rather not reformat te client and start over as there
are other tools (Rational) installed whose license is a
real pain to get redone. BTW, all other clients have
identical configurations (Rational, etc) which work.
I've tried uninstalling/resinstalling the SQL tools/SP3a,
reset the computer domain account (doesn't matter as I
can connect to the other two servers), something in the
registry etc must have got trashed is all I can figure.
Tried removing TCP and readding using client network
utility. Tried setting up an alias in same tool. Same
result. Can connect just fine as sa.
Thanks for any suggsetions!The login failed for user NULL indicates a problem with authenticating on
the DC when attempting the connection. It could also indicate that the user
who is attempting to logon to the SQL Server does not have permission to
access the server itself. Verify that the user can map to a share on the
SQL Server machine. If he can then check the NT Security log on the DC
where he is validated and see if there are any errors generated when he
attempts to connect to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I tried this with my domain admin account as well. Can
map shares on that server ok. Can login to server using
sa or Windows login fine over Named Pipes (server set to
both auth). When I try to login over TCP, can only login
using sa, Windows Login won't work. This server is also
the single PDC (development net).. get this, can log into
two other SQL servers (member servers only) from same
client using Named Pipes AND TCP using sa or Windows
Login.
I've un-installed TCP, removed/readded machine from
domain, it has to be something on this client...|||You get that error when the sa account hasn't been set on the server. Expand
the sql server => management folder => right click sql server agent
properties =>. last tab is connection .You would see that the sql server
connection is set to use 'windows NT authentication', you would need to
change it to SQL authentication
hope that helps
Ayo Coker
"Phil" <anonymous@.discussions.microsoft.com> wrote in message
news:fa4a01c3f1a9$47689870$a501280a@.phx.gbl...
> I tried this with my domain admin account as well. Can
> map shares on that server ok. Can login to server using
> sa or Windows login fine over Named Pipes (server set to
> both auth). When I try to login over TCP, can only login
> using sa, Windows Login won't work. This server is also
> the single PDC (development net).. get this, can log into
> two other SQL servers (member servers only) from same
> client using Named Pipes AND TCP using sa or Windows
> Login.
> I've un-installed TCP, removed/readded machine from
> domain, it has to be something on this client...
>

Help! Are my DTS Packages gone for good?

Something was wrong with my local SQL Server environment. I was unable to
connect to my own SQL Server running on my own workstation. So I uninstalled
and reinstalled. I knew my database files would be safe and sure enough, I
just reattached them after reinstalling.
But where are my DTS Packages? Are these gone for good, or are these
still in some location from which they can be recovered?
Thanks for your advice,
Joe Geretz
depends. If you save the DTS packages as VB files, you still have a change
to find them in OS directory. Otherwise, they are gone after msdb is
uninstalled.
Don't you have a msdb backup?
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Something was wrong with my local SQL Server environment. I was unable to
> connect to my own SQL Server running on my own workstation. So I
> uninstalled and reinstalled. I knew my database files would be safe and
> sure enough, I just reattached them after reinstalling.
> But where are my DTS Packages? Are these gone for good, or are these
> still in some location from which they can be recovered?
> Thanks for your advice,
> Joe Geretz
>
|||do you have msdb backup? any DTS backup?
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Something was wrong with my local SQL Server environment. I was unable to
> connect to my own SQL Server running on my own workstation. So I
> uninstalled and reinstalled. I knew my database files would be safe and
> sure enough, I just reattached them after reinstalling.
> But where are my DTS Packages? Are these gone for good, or are these
> still in some location from which they can be recovered?
> Thanks for your advice,
> Joe Geretz
>
|||Point well taken. All source is saved to Visual Source Safe but database
procs and utilities - weak link! I guess I'd always assumed these to be
resident in one particular database or another, but obviously they're not.
How do you do a DTS Backup? We use DTS to backup our databases from one
server to another, but backing up the DTS packages themselves? I didn't know
you could do that.
Thanks,
- Joe Geretz -
"Patrick" <patriarck@.gmail.com> wrote in message
news:uEWLQtpwEHA.1452@.TK2MSFTNGP11.phx.gbl...
> do you have msdb backup? any DTS backup?
>
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
>
|||You can save as VBscript or just save as .dts file
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:OcFw21pwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Point well taken. All source is saved to Visual Source Safe but database
> procs and utilities - weak link! I guess I'd always assumed these to be
> resident in one particular database or another, but obviously they're not.
> How do you do a DTS Backup? We use DTS to backup our databases from one
> server to another, but backing up the DTS packages themselves? I didn't
> know you could do that.
> Thanks,
> - Joe Geretz -
> "Patrick" <patriarck@.gmail.com> wrote in message
> news:uEWLQtpwEHA.1452@.TK2MSFTNGP11.phx.gbl...
>
|||Patrick,
DTS saved as VB cannot be saved back to a server. Not as easy. You would
have to include it into a VB snippet and save it from VB. That would loose
you graphical layout and comments. Regular way would be backing up msdb or
saving DTS as structured files.
Ilya
"Patrick" <patriarck@.gmail.com> wrote in message
news:%23xEVEIrwEHA.1392@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> You can save as VBscript or just save as .dts file
>
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:OcFw21pwEHA.2172@.TK2MSFTNGP14.phx.gbl...
not.[vbcol=seagreen]
and[vbcol=seagreen]
these
>
|||Yes, very important, depending to whom you speak... BACK UP YOUR SYSTEM
DATABASES...ALWAYS!
Sincerely,
Anthony Thomas
"Ilya Margolin" wrote:

> Patrick,
> DTS saved as VB cannot be saved back to a server. Not as easy. You would
> have to include it into a VB snippet and save it from VB. That would loose
> you graphical layout and comments. Regular way would be backing up msdb or
> saving DTS as structured files.
> Ilya
> "Patrick" <patriarck@.gmail.com> wrote in message
> news:%23xEVEIrwEHA.1392@.tk2msftngp13.phx.gbl...
> not.
> and
> these
>
>
|||If you didn't save them as files, just restore your backup of msdb.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Something was wrong with my local SQL Server environment. I was unable to
> connect to my own SQL Server running on my own workstation. So I uninstalled
> and reinstalled. I knew my database files would be safe and sure enough, I
> just reattached them after reinstalling.
> But where are my DTS Packages? Are these gone for good, or are these
> still in some location from which they can be recovered?
> Thanks for your advice,
> Joe Geretz
>
|||Guys you can get a realy good tool called DTSBackup from SQLDTS.com.
We back up 3000 scripts weekly. Just for peace of mind.
"Tibor Karaszi" wrote:

> If you didn't save them as files, just restore your backup of msdb.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
>
>

Help! Are my DTS Packages gone for good?

Something was wrong with my local SQL Server environment. I was unable to
connect to my own SQL Server running on my own workstation. So I uninstalled
and reinstalled. I knew my database files would be safe and sure enough, I
just reattached them after reinstalling.
But where are my DTS Packages' Are these gone for good, or are these
still in some location from which they can be recovered?
Thanks for your advice,
Joe Geretzdepends. If you save the DTS packages as VB files, you still have a change
to find them in OS directory. Otherwise, they are gone after msdb is
uninstalled.
Don't you have a msdb backup?
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Something was wrong with my local SQL Server environment. I was unable to
> connect to my own SQL Server running on my own workstation. So I
> uninstalled and reinstalled. I knew my database files would be safe and
> sure enough, I just reattached them after reinstalling.
> But where are my DTS Packages' Are these gone for good, or are these
> still in some location from which they can be recovered?
> Thanks for your advice,
> Joe Geretz
>|||do you have msdb backup? any DTS backup?
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Something was wrong with my local SQL Server environment. I was unable to
> connect to my own SQL Server running on my own workstation. So I
> uninstalled and reinstalled. I knew my database files would be safe and
> sure enough, I just reattached them after reinstalling.
> But where are my DTS Packages' Are these gone for good, or are these
> still in some location from which they can be recovered?
> Thanks for your advice,
> Joe Geretz
>|||Point well taken. All source is saved to Visual Source Safe but database
procs and utilities - weak link! I guess I'd always assumed these to be
resident in one particular database or another, but obviously they're not.
How do you do a DTS Backup? We use DTS to backup our databases from one
server to another, but backing up the DTS packages themselves? I didn't know
you could do that.
Thanks,
- Joe Geretz -
"Patrick" <patriarck@.gmail.com> wrote in message
news:uEWLQtpwEHA.1452@.TK2MSFTNGP11.phx.gbl...
> do you have msdb backup? any DTS backup?
>
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
>|||You can save as VBscript or just save as .dts file
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:OcFw21pwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Point well taken. All source is saved to Visual Source Safe but database
> procs and utilities - weak link! I guess I'd always assumed these to be
> resident in one particular database or another, but obviously they're not.
> How do you do a DTS Backup? We use DTS to backup our databases from one
> server to another, but backing up the DTS packages themselves? I didn't
> know you could do that.
> Thanks,
> - Joe Geretz -
> "Patrick" <patriarck@.gmail.com> wrote in message
> news:uEWLQtpwEHA.1452@.TK2MSFTNGP11.phx.gbl...
>|||Patrick,
DTS saved as VB cannot be saved back to a server. Not as easy. You would
have to include it into a VB snippet and save it from VB. That would loose
you graphical layout and comments. Regular way would be backing up msdb or
saving DTS as structured files.
Ilya
"Patrick" <patriarck@.gmail.com> wrote in message
news:%23xEVEIrwEHA.1392@.tk2msftngp13.phx.gbl...
> You can save as VBscript or just save as .dts file
>
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:OcFw21pwEHA.2172@.TK2MSFTNGP14.phx.gbl...
not.[vbcol=seagreen]
and[vbcol=seagreen]
these[vbcol=seagreen]
>|||Yes, very important, depending to whom you speak... BACK UP YOUR SYSTEM
DATABASES...ALWAYS!
Sincerely,
Anthony Thomas
"Ilya Margolin" wrote:

> Patrick,
> DTS saved as VB cannot be saved back to a server. Not as easy. You would
> have to include it into a VB snippet and save it from VB. That would loose
> you graphical layout and comments. Regular way would be backing up msdb or
> saving DTS as structured files.
> Ilya
> "Patrick" <patriarck@.gmail.com> wrote in message
> news:%23xEVEIrwEHA.1392@.tk2msftngp13.phx.gbl...
> not.
> and
> these
>
>|||If you didn't save them as files, just restore your backup of msdb.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Something was wrong with my local SQL Server environment. I was unable to
> connect to my own SQL Server running on my own workstation. So I uninstall
ed
> and reinstalled. I knew my database files would be safe and sure enough, I
> just reattached them after reinstalling.
> But where are my DTS Packages' Are these gone for good, or are these
> still in some location from which they can be recovered?
> Thanks for your advice,
> Joe Geretz
>|||Guys you can get a realy good tool called DTSBackup from SQLDTS.com.
We back up 3000 scripts weekly. Just for peace of mind.
"Tibor Karaszi" wrote:

> If you didn't save them as files, just restore your backup of msdb.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
>
>

Help! Are my DTS Packages gone for good?

Something was wrong with my local SQL Server environment. I was unable to
connect to my own SQL Server running on my own workstation. So I uninstalled
and reinstalled. I knew my database files would be safe and sure enough, I
just reattached them after reinstalling.
But where are my DTS Packages' Are these gone for good, or are these
still in some location from which they can be recovered?
Thanks for your advice,
Joe Geretzdepends. If you save the DTS packages as VB files, you still have a change
to find them in OS directory. Otherwise, they are gone after msdb is
uninstalled.
Don't you have a msdb backup?
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Something was wrong with my local SQL Server environment. I was unable to
> connect to my own SQL Server running on my own workstation. So I
> uninstalled and reinstalled. I knew my database files would be safe and
> sure enough, I just reattached them after reinstalling.
> But where are my DTS Packages' Are these gone for good, or are these
> still in some location from which they can be recovered?
> Thanks for your advice,
> Joe Geretz
>|||do you have msdb backup? any DTS backup?
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Something was wrong with my local SQL Server environment. I was unable to
> connect to my own SQL Server running on my own workstation. So I
> uninstalled and reinstalled. I knew my database files would be safe and
> sure enough, I just reattached them after reinstalling.
> But where are my DTS Packages' Are these gone for good, or are these
> still in some location from which they can be recovered?
> Thanks for your advice,
> Joe Geretz
>|||Point well taken. All source is saved to Visual Source Safe but database
procs and utilities - weak link! I guess I'd always assumed these to be
resident in one particular database or another, but obviously they're not.
How do you do a DTS Backup? We use DTS to backup our databases from one
server to another, but backing up the DTS packages themselves? I didn't know
you could do that.
Thanks,
- Joe Geretz -
"Patrick" <patriarck@.gmail.com> wrote in message
news:uEWLQtpwEHA.1452@.TK2MSFTNGP11.phx.gbl...
> do you have msdb backup? any DTS backup?
>
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
>> Something was wrong with my local SQL Server environment. I was unable to
>> connect to my own SQL Server running on my own workstation. So I
>> uninstalled and reinstalled. I knew my database files would be safe and
>> sure enough, I just reattached them after reinstalling.
>> But where are my DTS Packages' Are these gone for good, or are these
>> still in some location from which they can be recovered?
>> Thanks for your advice,
>> Joe Geretz
>>
>|||You can save as VBscript or just save as .dts file
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:OcFw21pwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Point well taken. All source is saved to Visual Source Safe but database
> procs and utilities - weak link! I guess I'd always assumed these to be
> resident in one particular database or another, but obviously they're not.
> How do you do a DTS Backup? We use DTS to backup our databases from one
> server to another, but backing up the DTS packages themselves? I didn't
> know you could do that.
> Thanks,
> - Joe Geretz -
> "Patrick" <patriarck@.gmail.com> wrote in message
> news:uEWLQtpwEHA.1452@.TK2MSFTNGP11.phx.gbl...
>> do you have msdb backup? any DTS backup?
>>
>> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
>> news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
>> Something was wrong with my local SQL Server environment. I was unable
>> to connect to my own SQL Server running on my own workstation. So I
>> uninstalled and reinstalled. I knew my database files would be safe and
>> sure enough, I just reattached them after reinstalling.
>> But where are my DTS Packages' Are these gone for good, or are these
>> still in some location from which they can be recovered?
>> Thanks for your advice,
>> Joe Geretz
>>
>>
>|||Patrick,
DTS saved as VB cannot be saved back to a server. Not as easy. You would
have to include it into a VB snippet and save it from VB. That would loose
you graphical layout and comments. Regular way would be backing up msdb or
saving DTS as structured files.
Ilya
"Patrick" <patriarck@.gmail.com> wrote in message
news:%23xEVEIrwEHA.1392@.tk2msftngp13.phx.gbl...
> You can save as VBscript or just save as .dts file
>
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:OcFw21pwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> > Point well taken. All source is saved to Visual Source Safe but database
> > procs and utilities - weak link! I guess I'd always assumed these to be
> > resident in one particular database or another, but obviously they're
not.
> >
> > How do you do a DTS Backup? We use DTS to backup our databases from one
> > server to another, but backing up the DTS packages themselves? I didn't
> > know you could do that.
> >
> > Thanks,
> >
> > - Joe Geretz -
> >
> > "Patrick" <patriarck@.gmail.com> wrote in message
> > news:uEWLQtpwEHA.1452@.TK2MSFTNGP11.phx.gbl...
> >> do you have msdb backup? any DTS backup?
> >>
> >>
> >> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> >> news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> >> Something was wrong with my local SQL Server environment. I was unable
> >> to connect to my own SQL Server running on my own workstation. So I
> >> uninstalled and reinstalled. I knew my database files would be safe
and
> >> sure enough, I just reattached them after reinstalling.
> >>
> >> But where are my DTS Packages' Are these gone for good, or are
these
> >> still in some location from which they can be recovered?
> >>
> >> Thanks for your advice,
> >>
> >> Joe Geretz
> >>
> >>
> >>
> >>
> >
> >
>|||Yes, very important, depending to whom you speak... BACK UP YOUR SYSTEM
DATABASES...ALWAYS!
Sincerely,
Anthony Thomas
"Ilya Margolin" wrote:
> Patrick,
> DTS saved as VB cannot be saved back to a server. Not as easy. You would
> have to include it into a VB snippet and save it from VB. That would loose
> you graphical layout and comments. Regular way would be backing up msdb or
> saving DTS as structured files.
> Ilya
> "Patrick" <patriarck@.gmail.com> wrote in message
> news:%23xEVEIrwEHA.1392@.tk2msftngp13.phx.gbl...
> > You can save as VBscript or just save as .dts file
> >
> >
> > "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> > news:OcFw21pwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> > > Point well taken. All source is saved to Visual Source Safe but database
> > > procs and utilities - weak link! I guess I'd always assumed these to be
> > > resident in one particular database or another, but obviously they're
> not.
> > >
> > > How do you do a DTS Backup? We use DTS to backup our databases from one
> > > server to another, but backing up the DTS packages themselves? I didn't
> > > know you could do that.
> > >
> > > Thanks,
> > >
> > > - Joe Geretz -
> > >
> > > "Patrick" <patriarck@.gmail.com> wrote in message
> > > news:uEWLQtpwEHA.1452@.TK2MSFTNGP11.phx.gbl...
> > >> do you have msdb backup? any DTS backup?
> > >>
> > >>
> > >> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> > >> news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> > >> Something was wrong with my local SQL Server environment. I was unable
> > >> to connect to my own SQL Server running on my own workstation. So I
> > >> uninstalled and reinstalled. I knew my database files would be safe
> and
> > >> sure enough, I just reattached them after reinstalling.
> > >>
> > >> But where are my DTS Packages' Are these gone for good, or are
> these
> > >> still in some location from which they can be recovered?
> > >>
> > >> Thanks for your advice,
> > >>
> > >> Joe Geretz
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> >
> >
>
>|||If you didn't save them as files, just restore your backup of msdb.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Something was wrong with my local SQL Server environment. I was unable to
> connect to my own SQL Server running on my own workstation. So I uninstalled
> and reinstalled. I knew my database files would be safe and sure enough, I
> just reattached them after reinstalling.
> But where are my DTS Packages' Are these gone for good, or are these
> still in some location from which they can be recovered?
> Thanks for your advice,
> Joe Geretz
>|||Guys you can get a realy good tool called DTSBackup from SQLDTS.com.
We back up 3000 scripts weekly. Just for peace of mind.
"Tibor Karaszi" wrote:
> If you didn't save them as files, just restore your backup of msdb.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:%23nGKAopwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> > Something was wrong with my local SQL Server environment. I was unable to
> > connect to my own SQL Server running on my own workstation. So I uninstalled
> > and reinstalled. I knew my database files would be safe and sure enough, I
> > just reattached them after reinstalling.
> >
> > But where are my DTS Packages' Are these gone for good, or are these
> > still in some location from which they can be recovered?
> >
> > Thanks for your advice,
> >
> > Joe Geretz
> >
> >
>
>

HELP! ODBC becoming unusable

Here goes: We have situation at a customer site where users are suddenly unable to connect to SQL 2K via ASP using ODBC via DSN. While the customer is in this state, our Windows clients, which connect using OLE DB (ADO) to the same DB as the ASP, seem to be connecting without problems. Therefore, the problem seems to be with ODBC.

Additional details about the problem site:
SQL ODBC 3.50
Win2K Server SP 4.
SQL2k SP2.
MDAC 2.62
<100 users total
Moderate usage of our ASP interface

Note: SQL2k and IIS are on the same LAN-side server.

FYI: Another part of the problem is that I'm a developer and am not that familiar with the tools available to help me troubleshoot this kind of problem.

We've tried using Perfmon to monitor connection pooling, but nothing stood-out.

We've tried using netstat (with various switches), but nothing stood-out.

Does anybody have any advice?At least apply SP3 to your SQL.|||http://www.winnetmag.com/Windows/Article/ArticleID/3507/3507.html and take help of ODBC trace.
Check this KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;268591 and corresponding referenced KBAs to take help of ODBC tracing to troubleshoot the problem.

Ensure both client and server are enabled with similar protocol, service packs as referred.|||Originally posted by rdjabarov
At least apply SP3 to your SQL.

Thanks. We will be advising them to update SQL to SP3, but it's not very comforting to us to give what they'll perceive as a solution, when we heavn't even identified the problem.|||While many of us here know client connectivity, it's still a SQL Server forum, not SQL Client ;)

I'd follow Satya's suggestions, at least you can see for yourself if you're even getting to the server.|||Originally posted by Satya
http://www.winnetmag.com/Windows/Article/ArticleID/3507/3507.html and take help of ODBC trace.
Check this KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;268591 and corresponding referenced KBAs to take help of ODBC tracing to troubleshoot the problem.

Ensure both client and server are enabled with similar protocol, service packs as referred.
That's some great information! But won't this only trace activity across an open connection (implicit or explicit)? If so, I'm not sure it'll help because the problems is that at some point, the ASP are simply unable to connect via DSN using ODBC.

Given that it's as though SQL is simply inaccessable via the DSN, even when the ADO OLE DB client app is connecting fine, we've been speculating (with help from Microsoft) that the problem is with ODBC's connection pooling. We've tried to set-up performance logging of connection pooling in-house in an effort to determine it's potential usefulness to our scenario in production, but our in-house graphs show no activity...probably due to the relatively low activity in our development environment. We walked the customer through setting it up on their server anyhow.

Just recently, the problem occurred again on the customer's server. Before they could reboot the server, we took the opportunity to run NETSTAT to view the sockets for clues, but there were less than 20 results. Possibly because they have SQL and IIS on the same server?

This sucks because all we want to do is get an idea of how to duplicate the problem in a controlled environment so we can either a) adjust our ASP accordingly or b) give them a solution that we know addresses the problem.

Thoughts, comments, advice?|||Originally posted by rdjabarov
While many of us here know client connectivity, it's still a SQL Server forum, not SQL Client ;)

I'd follow Satya's suggestions, at least you can see for yourself if you're even getting to the server.
Was the frist comment a suggestion that my question (i.e. how to troubleshoot SQL connectivity issues) is outside of the scope of this forum? If so, please advise a more approriate forum. Thanks.

HELP!

i am running a windows sharepoint services site.. I get an error that says "Unable to connect to database. Check database connection information and make sure the database server is running."
i check my event log and get this..
Event Type:Information
Event Source:MSSQLSERVER/MSDE
Event Category:None
Event ID:1
Date:5/10/2004
Time:8:49:04 AM
User:N/A
Computer:211551S
Description:
You are running a version of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (also called MSDE) that has known security vulnerabilities when used in conjunction with the Microsoft Windows Server 2003 family. To reduce your computer'
s vulnerability to certain virus attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE, or both have been disabled. To enable these ports, you must install a patch, or the most recent service pack for Microsoft SQL Server 2000 or M
SDE from http://www.microsoft.com/sql/downloads/default.asp
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
how do I get this thing up and running again.. please e-mail me at jason_adolf@.sra.com
That's an informational message in your event log that you
will get if you are running SQL Server at something less
than SP3. You should install SQL Server SP3.
-Sue
On Mon, 10 May 2004 06:01:05 -0700, jason7
<jason_adolf@.sra.com> wrote:

>i am running a windows sharepoint services site.. I get an error that says "Unable to connect to database. Check database connection information and make sure the database server is running."
>i check my event log and get this..
>Event Type:Information
>Event Source:MSSQLSERVER/MSDE
>Event Category:None
>Event ID:1
>Date:5/10/2004
>Time:8:49:04 AM
>User:N/A
>Computer:211551S
>Description:
>You are running a version of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (also called MSDE) that has known security vulnerabilities when used in conjunction with the Microsoft Windows Server 2003 family. To reduce your computer
's vulnerability to certain virus attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE, or both have been disabled. To enable these ports, you must install a patch, or the most recent service pack for Microsoft SQL Server 2000 or
MSDE from http://www.microsoft.com/sql/downloads/default.asp
>For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
>
>how do I get this thing up and running again.. please e-mail me at jason_adolf@.sra.com

HELP!

i am running a windows sharepoint services site.. I get an error that says
"Unable to connect to database. Check database connection information and m
ake sure the database server is running."
i check my event log and get this..
Event Type: Information
Event Source: MSSQLSERVER/MSDE
Event Category: None
Event ID: 1
Date: 5/10/2004
Time: 8:49:04 AM
User: N/A
Computer: 211551S
Description:
You are running a version of Microsoft SQL Server 2000 or Microsoft SQL Serv
er 2000 Desktop Engine (also called MSDE) that has known security vulnerabil
ities when used in conjunction with the Microsoft Windows Server 2003 family
. To reduce your computer'
s vulnerability to certain virus attacks, the TCP/IP and UDP network ports o
f Microsoft SQL Server 2000, MSDE, or both have been disabled. To enable th
ese ports, you must install a patch, or the most recent service pack for Mic
rosoft SQL Server 2000 or M
SDE from http://www.microsoft.com/sql/downloads/default.asp
For more information, see Help and Support Center at k/events.asp." target="_blank">http://go.microsoft.com/fwlin
k/events.asp.
how do I get this thing up and running again.. please e-mail me at jason_ado
lf@.sra.comThat's an informational message in your event log that you
will get if you are running SQL Server at something less
than SP3. You should install SQL Server SP3.
-Sue
On Mon, 10 May 2004 06:01:05 -0700, jason7
<jason_adolf@.sra.com> wrote:

>i am running a windows sharepoint services site.. I get an error that says
"Unable to connect to database. Check database connection information and
make sure the database server is running."
>i check my event log and get this..
>Event Type: Information
>Event Source: MSSQLSERVER/MSDE
>Event Category: None
>Event ID: 1
>Date: 5/10/2004
>Time: 8:49:04 AM
>User: N/A
>Computer: 211551S
>Description:
>You are running a version of Microsoft SQL Server 2000 or Microsoft SQL Server 2000
Desktop Engine (also called MSDE) that has known security vulnerabilities when used
in conjunction with the Microsoft Windows Server 2003 family. To reduce your compu
ter
's vulnerability to certain virus attacks, the TCP/IP and UDP network ports
of Microsoft SQL Server 2000, MSDE, or both have been disabled. To enable t
hese ports, you must install a patch, or the most recent service pack for Mi
crosoft SQL Server 2000 or
MSDE from http://www.microsoft.com/sql/downloads/default.asp
>For more information, see Help and Support Center at nk/events.asp." target="_blank">http://go.microsoft.com/fwli
nk/events.asp.
>
>how do I get this thing up and running again.. please e-mail me at jason_adolf@.sra.
com

HELP!

i am running a windows sharepoint services site.. I get an error that says "Unable to connect to database. Check database connection information and make sure the database server is running.
i check my event log and get this.
Event Type: Informatio
Event Source: MSSQLSERVER/MSD
Event Category: Non
Event ID:
Date: 5/10/200
Time: 8:49:04 A
User: N/
Computer: 211551
Description
You are running a version of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (also called MSDE) that has known security vulnerabilities when used in conjunction with the Microsoft Windows Server 2003 family. To reduce your computer's vulnerability to certain virus attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE, or both have been disabled. To enable these ports, you must install a patch, or the most recent service pack for Microsoft SQL Server 2000 or MSDE from http://www.microsoft.com/sql/downloads/default.as
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp
how do I get this thing up and running again.. please e-mail me at jason_adolf@.sra.comThat's an informational message in your event log that you
will get if you are running SQL Server at something less
than SP3. You should install SQL Server SP3.
-Sue
On Mon, 10 May 2004 06:01:05 -0700, jason7
<jason_adolf@.sra.com> wrote:
>i am running a windows sharepoint services site.. I get an error that says "Unable to connect to database. Check database connection information and make sure the database server is running."
>i check my event log and get this..
>Event Type: Information
>Event Source: MSSQLSERVER/MSDE
>Event Category: None
>Event ID: 1
>Date: 5/10/2004
>Time: 8:49:04 AM
>User: N/A
>Computer: 211551S
>Description:
>You are running a version of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (also called MSDE) that has known security vulnerabilities when used in conjunction with the Microsoft Windows Server 2003 family. To reduce your computer's vulnerability to certain virus attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE, or both have been disabled. To enable these ports, you must install a patch, or the most recent service pack for Microsoft SQL Server 2000 or MSDE from http://www.microsoft.com/sql/downloads/default.asp
>For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
>
>how do I get this thing up and running again.. please e-mail me at jason_adolf@.sra.com