Modify /concatenate varbinary data in SQL Server 2005

I am trying to store large files /images in SQL Server 2005.

I have used varbinay data type for the table column. At front end i am storing value in blob and inserting record to this table. but SQL Server does not allow to insert directly blob data to varbinary . So we need to convert blob data to varbinary using convert() function. After conversion, check the data ,it gives some junk values. How do i insert blob data into table with column data type as varbinary ?

2) We are trying to send blob data to SQL server 2005 in chunks. How to do it if column in table is varbinary ?

Please advice.

Regards

Rithik

You can check the following article to get the idea.

Insert BLOB from ADO.NET

http://support.microsoft.com/kb/309158

Learn more facts about BLOB when you design database

http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part3/c1161.mspx?mfr=true

|||

Hi,

Thanks for your advice.

We are using powerbuilder 10 as front end and sql server 2005 as database. We use updateblob statement to update blob data to varbinary column in SQL Server script as follows.

1)Script :

UpdateBlob r_test Set blob_data = :lblob_filedata Where file_id =21;

2)And we used stored procedure as follows:

CRAETE PROCEDURE [dbo].[R_UPLOAD_FILES_TO_DB]
(
@.V_SOURCE_DATA VARBINARY(MAX),
@.V_FILE_ID NUMERIC(8)
)
AS

UPDATE R_TEST
SET DATA = @.V_SOURCE_DATA WHERE FILE_ID = @.V_FILE_ID

Blob data can have text files,bitmap files ,or any other file having size less than 2 GB.

The Table R_test Design :

Create table r_test

(data varbinary(max),fle_id numeric(8))

But when we checked the data we found it's not same.

SQL Server varbinary column stored blob data in different format. Why the data appears different ?

Please advice

Regards

Rithik

|||I want to store binary data in database. I have byte array, but i am unable to insert that in database because i don't know how to insert variable name of type BYTE in sql insert query.

my code is as follow

dim byteArray() as byte

strSQL = "INSERT INTO TEMP(TEMP_NAME,TEMP_BIN) VALUES('SANSHARK',?)"

how do i pass my byteArray in ?sql

Model DB problem..

attempted to move my Model and msdb database files to a different drive on the server. I did the following:
* Restarted SQL Server 2K with the -T3608 startup parameter
* successfully detached msdb and model DBs
* moved the msdbdata.mdf, msdblog.ldf, model.mdf and modellog.ldf
files to their new homes
* successfully reattached model and msdb

When I take away the -T3808 startup parameter and restart SQL Server, I do not see the model database in the db list in enterprise manager eventhough my 'attach' seemed to work. Now I get the following error when i try and query against the Model database using query analyzer:

"Could not locate entry in sysdatabases for database 'model'. No entry found with that name. Make sure that the name is entered correctly"

Also, when I look in the sysaltfiles table in Master, I see no reference whatsoever to the Model DB

What did I do wrong?attempted to move my Model and msdb database files to a different drive on the server. I did the following:
* Restarted SQL Server 2K with the -T3608 startup parameter
* successfully detached msdb and model DBs
* moved the msdbdata.mdf, msdblog.ldf, model.mdf and modellog.ldf
files to their new homes
* successfully reattached model and msdb

What did I do wrong?

Ouch! I HATE it when that happens. Here's a link, you've probably already read it (here (http://support.microsoft.com/default.aspx?scid=kb;en-us;224071)).

I would (in more or less this order):
1. Look carefully at the SQL Error log
2. Restart with -T3608 and attempt to re-attach model
3. Restore model from a backup (you did have a backup, right?)

I seem to recall from a distant memory that when you moved msdb and model, there was a particular sequence (one HAD to be done before the other). [Edit: here it is, smack in the middle of the link above].

Note If you are using this procedure together with moving the msdb
and model databases, the order of reattachment must be model first
and then msdb. If msdb is reattached first, it must be detached and
not reattached until after model has been attached.

I can't tell for certain from the steps you outline above which you did first.

I have used this procedure to move model, master, msdb and tempdb on several different occasions with no trouble at all (sorry, that doesn't help you, but I did want to verify that the steps outlined above DO work). As I recall, I usually make it a point to move msdb and model in separate steps (restarting SQL Server in between moving these two dbs).

Best of luck,

hmscottsql

mmc.exe - .dll files are corrupted

Windows NT 4.0 operating system SQL 7.0 is loaded. Sql enterprise manager is opend mmc.exe - .dll files are corrupted. Please giveme advice

ThankyouHi there,

welcome to thescipts, take care my fren.. :)

MMC recovery

We recently lost our hard disk on disk c: It contained
Windows 2000 system files, but no SQL Server 7.0 files.
Our program files, data, and backups were on drive d:.
After rebuilding the W2K server, we ran regrebld.exe to
reestabish the W2K registry entries. We were able to
restart SQL Server and the Agent, but MMC (Microsoft
Management Console) will not start due to problems with
missing CLSIDs. We are able to access the database and
Agent info from remote MMCs, but not on the local server.
I don't see any option to reinstall/register MMC. Any
ideas of what to do?I found instmmc.exe on the installation disk. I'll try it
in the morning.
>--Original Message--
>We recently lost our hard disk on disk c: It contained
>Windows 2000 system files, but no SQL Server 7.0 files.
>Our program files, data, and backups were on drive d:.
>After rebuilding the W2K server, we ran regrebld.exe to
>reestabish the W2K registry entries. We were able to
>restart SQL Server and the Agent, but MMC (Microsoft
>Management Console) will not start due to problems with
>missing CLSIDs. We are able to access the database and
>Agent info from remote MMCs, but not on the local
server.
>I don't see any option to reinstall/register MMC. Any
>ideas of what to do?
>.
>

MMC Can't open SQL Server Enterprise Manager.msc

Hi All,
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
...when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
RyanRyan,
Can you rename it to SQLEM.msc? Does that work? Then just create a
shortcut on your desktop or Start Menu, and all should be well.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Ryan Breakspear wrote:
> Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be becau
se
> the files does not exist, is not an MMC console, or was created by a later
> version of MMC. This may also be because you do not have sufficied access
> rights to the file.
> ...when trying to run Enterprise Manager. I have tried re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run enterprise
> manager if logged on as the local administrator. I can also run SQL Serve
r
> Enterprise Manager.msc if I rename it to anything else, and it seems to wo
rk
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> seems like a very odd issue.
> Thanks in advance.
> Ryan
>|||Yep, I can rename it to anything. I can run it fine renamed as something
else, I just wondered why the problem, and if there was a solution.
Thanks for your reply.
Ryan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:edplxoLcEHA.1248@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Ryan,
> Can you rename it to SQLEM.msc? Does that work? Then just create a
> shortcut on your desktop or Start Menu, and all should be well.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Ryan Breakspear wrote:
because[vbcol=seagreen]
later[vbcol=seagreen]
access[vbcol=seagreen]
the[vbcol=seagreen]
enterprise[vbcol=seagreen]
Server[vbcol=seagreen]
work[vbcol=seagreen]|||I have the exact same settings, and the exact same problem. Wish I had
found this workaround before re-installing everything... Still would
like to know what is causing this though...
Cheers - Craig
Ryan Breakspear wrote:
> *Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting
> the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
> because
> the files does not exist, is not an MMC console, or was created by a
> later
> version of MMC. This may also be because you do not have sufficied
> access
> rights to the file.
> ....when trying to run Enterprise Manager. I have tried
> re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run
> enterprise
> manager if logged on as the local administrator. I can also run SQL
> Server
> Enterprise Manager.msc if I rename it to anything else, and it seems
> to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2?
> It
> seems like a very odd issue.
> Thanks in advance.
> Ryan *
cjeff
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message888314.html|||I have been trying to fix this problem for some time. The fact that it
worked for you when you renamed it tipped me off to the source of the
problem. There is a cached version of the MMC file in the C:\Documents and
Settings\<username>\Application Data\Microsoft\MMC folder.
The problem is that on my system that cached file was corrupted.
Once I deleted the cached file, I was able to open SQL EntMgr with no proble
m.
"cjeff" wrote:

> I have the exact same settings, and the exact same problem. Wish I had
> found this workaround before re-installing everything... Still would
> like to know what is causing this though...
> Cheers - Craig
> Ryan Breakspear wrote:
>
> --
> cjeff
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message888314.html
>

MMC Can't open SQL Server Enterprise Manager.msc

Hi All,
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
...when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
Ryan
Ryan,
Can you rename it to SQLEM.msc? Does that work? Then just create a
shortcut on your desktop or Start Menu, and all should be well.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Ryan Breakspear wrote:
> Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
> the files does not exist, is not an MMC console, or was created by a later
> version of MMC. This may also be because you do not have sufficied access
> rights to the file.
> ...when trying to run Enterprise Manager. I have tried re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run enterprise
> manager if logged on as the local administrator. I can also run SQL Server
> Enterprise Manager.msc if I rename it to anything else, and it seems to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> seems like a very odd issue.
> Thanks in advance.
> Ryan
>
|||Yep, I can rename it to anything. I can run it fine renamed as something
else, I just wondered why the problem, and if there was a solution.
Thanks for your reply.
Ryan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:edplxoLcEHA.1248@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Ryan,
> Can you rename it to SQLEM.msc? Does that work? Then just create a
> shortcut on your desktop or Start Menu, and all should be well.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Ryan Breakspear wrote:
because[vbcol=seagreen]
later[vbcol=seagreen]
access[vbcol=seagreen]
the[vbcol=seagreen]
enterprise[vbcol=seagreen]
Server[vbcol=seagreen]
work[vbcol=seagreen]
|||I have the exact same settings, and the exact same problem. Wish I had found this workaround before re-installing everything... Still would like to know what is causing this though...
Cheers - Craig

Quote:

Originally posted by Ryan Breakspear
Hi All,
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
....when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
Ryan

|||I have been trying to fix this problem for some time. The fact that it
worked for you when you renamed it tipped me off to the source of the
problem. There is a cached version of the MMC file in the C:\Documents and
Settings\<username>\Application Data\Microsoft\MMC folder.
The problem is that on my system that cached file was corrupted.
Once I deleted the cached file, I was able to open SQL EntMgr with no problem.
"cjeff" wrote:

> I have the exact same settings, and the exact same problem. Wish I had
> found this workaround before re-installing everything... Still would
> like to know what is causing this though...
> Cheers - Craig
> Ryan Breakspear wrote:
>
> --
> cjeff
> Posted via http://www.mcse.ms
> View this thread: http://www.mcse.ms/message888314.html
>

MMC Can't open SQL Server Enterprise Manager.msc

Hi All,
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
...when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
RyanRyan,
Can you rename it to SQLEM.msc? Does that work? Then just create a
shortcut on your desktop or Start Menu, and all should be well.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Ryan Breakspear wrote:
> Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
> the files does not exist, is not an MMC console, or was created by a later
> version of MMC. This may also be because you do not have sufficied access
> rights to the file.
> ...when trying to run Enterprise Manager. I have tried re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run enterprise
> manager if logged on as the local administrator. I can also run SQL Server
> Enterprise Manager.msc if I rename it to anything else, and it seems to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> seems like a very odd issue.
> Thanks in advance.
> Ryan
>|||Yep, I can rename it to anything. I can run it fine renamed as something
else, I just wondered why the problem, and if there was a solution.
Thanks for your reply.
Ryan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:edplxoLcEHA.1248@.TK2MSFTNGP11.phx.gbl...
> Ryan,
> Can you rename it to SQLEM.msc? Does that work? Then just create a
> shortcut on your desktop or Start Menu, and all should be well.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Ryan Breakspear wrote:
> > Hi All,
> >
> > I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> > error:
> >
> > MMC cannot open the file c:\Program Files\Microsoft SQL
> > Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
because
> > the files does not exist, is not an MMC console, or was created by a
later
> > version of MMC. This may also be because you do not have sufficied
access
> > rights to the file.
> >
> > ...when trying to run Enterprise Manager. I have tried re-installing
the
> > server and client tools, and SP3a, but still the same error.
> >
> > I have administrator access to the PC, but strangely, I can run
enterprise
> > manager if logged on as the local administrator. I can also run SQL
Server
> > Enterprise Manager.msc if I rename it to anything else, and it seems to
work
> > all right.
> >
> > Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> > seems like a very odd issue.
> >
> > Thanks in advance.
> >
> > Ryan
> >
> >|||I have the exact same settings, and the exact same problem. Wish I had
found this workaround before re-installing everything... Still would
like to know what is causing this though...
Cheers - Craig
Ryan Breakspear wrote:
> *Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting
> the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
> because
> the files does not exist, is not an MMC console, or was created by a
> later
> version of MMC. This may also be because you do not have sufficied
> access
> rights to the file.
> ....when trying to run Enterprise Manager. I have tried
> re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run
> enterprise
> manager if logged on as the local administrator. I can also run SQL
> Server
> Enterprise Manager.msc if I rename it to anything else, and it seems
> to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2?
> It
> seems like a very odd issue.
> Thanks in advance.
> Ryan *
cjeff
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message888314.html|||I have been trying to fix this problem for some time. The fact that it
worked for you when you renamed it tipped me off to the source of the
problem. There is a cached version of the MMC file in the C:\Documents and
Settings\<username>\Application Data\Microsoft\MMC folder.
The problem is that on my system that cached file was corrupted.
Once I deleted the cached file, I was able to open SQL EntMgr with no problem.
"cjeff" wrote:
> I have the exact same settings, and the exact same problem. Wish I had
> found this workaround before re-installing everything... Still would
> like to know what is causing this though...
> Cheers - Craig
> Ryan Breakspear wrote:
> > *Hi All,
> >
> > I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting
> > the
> > error:
> >
> > MMC cannot open the file c:\Program Files\Microsoft SQL
> > Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
> > because
> > the files does not exist, is not an MMC console, or was created by a
> > later
> > version of MMC. This may also be because you do not have sufficied
> > access
> > rights to the file.
> >
> > ....when trying to run Enterprise Manager. I have tried
> > re-installing the
> > server and client tools, and SP3a, but still the same error.
> >
> > I have administrator access to the PC, but strangely, I can run
> > enterprise
> > manager if logged on as the local administrator. I can also run SQL
> > Server
> > Enterprise Manager.msc if I rename it to anything else, and it seems
> > to work
> > all right.
> >
> > Shall I just carry on using the new SQL Server Enterprise Manager 2?
> > It
> > seems like a very odd issue.
> >
> > Thanks in advance.
> >
> > Ryan *
>
> --
> cjeff
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message888314.html
>

MMC Cannot open

who knows how to fix this:
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC.
This may be because the file doesnt exist, is not an MMC console, or
was created by a later version of MMC. This may also be because
you do not have sufficient access rights to the file.
I have rebooted the server, and restarted my machine, uninstalled and reinstalled SQL Server 7.0 Client. I still can't start SQL Server Enterprise Manager. Can anyone help?
Thanks in advance
Jane
Jane, once again, have you considered using SQL Server 2000 Enterprise
Manager? You seem to have both installed on your machine, and when you try
to launch 7.0 it is looking in \80\ and causing a conflict. I suggest
uninstalling SQL 7.0 client, reinstalling 2000 client, installing 2000 SP3a,
and using 2000 client tools.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:C0397850-DCCD-4AEE-9ADF-AAD21DC84737@.microsoft.com...
> who knows how to fix this:
> MMC cannot open the file C:\Program Files\Microsoft SQL
> Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC.
> This may be because the file doesnt exist, is not an MMC console, or
> was created by a later version of MMC. This may also be because
> you do not have sufficient access rights to the file.
> I have rebooted the server, and restarted my machine, uninstalled and
reinstalled SQL Server 7.0 Client. I still can't start SQL Server Enterprise
Manager. Can anyone help?
> Thanks in advance
> Jane
>
|||Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000. The problem is very strange. I suppose I am locked by the server. Don't know what to do now.
As I said, I am new to SQL Server, I am trying to explore it. But there isn't a senior member in our team, so your help turns to be very important for me. I am looking forward to any ideas.
Cheers
Jane
|||Jane,
Refer the steps 3 to 5 given in the 'workaround' section of this article:
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000'
http://support.microsoft.com/default.aspx?id=272453
PS: I know that the title of the article doesnt concern you, but those steps
might help.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000.
The problem is very strange. I suppose I am locked by the server. Don't know
what to do now.
> As I said, I am new to SQL Server, I am trying to explore it. But there
isn't a senior member in our team, so your help turns to be very important
for me. I am looking forward to any ideas.
> Cheers
> Jane
|||Thanks for your help, but it doesn't work. Any ideas?
Jane
-- Dinesh T.K wrote: --
Jane,
Refer the steps 3 to 5 given in the 'workaround' section of this article:
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000'
http://support.microsoft.com/default.aspx?id=272453
PS: I know that the title of the article doesnt concern you, but those steps
might help.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000.
The problem is very strange. I suppose I am locked by the server. Don't know
what to do now.
> As I said, I am new to SQL Server, I am trying to explore it. But there
isn't a senior member in our team, so your help turns to be very important
for me. I am looking forward to any ideas.
> Cheers
> Jane
|||Jane,
May be EM is missing some DLLs .The relevant ones are
sqlns.dll,sqlmmc.dll,sqldmo.dll,dtsui.dll and sqllex.dll.Usually you can
find them in c:\mssql7\binn\.
Try re-registering them using regsvr32.exe.After each one, try opening up
EM.
If this too doesnt help, see if a reinstall of the relevant MDAC helps.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps[vbcol=seagreen]
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
2000.
> The problem is very strange. I suppose I am locked by the server.
Don't know[vbcol=seagreen]
> what to do now.
there
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
>
>
|||Jane,
What is the version of you mmc.exe? What is the OS and SP level of your
workstation?
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps[vbcol=seagreen]
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
2000.
> The problem is very strange. I suppose I am locked by the server.
Don't know[vbcol=seagreen]
> what to do now.
there
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
>
>

MMC Cannot open

who knows how to fix this
MMC cannot open the file C:\Program Files\Microsoft SQ
Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC
This may be because the file doesnt exist, is not an MMC console, o
was created by a later version of MMC. This may also be becaus
you do not have sufficient access rights to the file
I have rebooted the server, and restarted my machine, uninstalled and reinstalled SQL Server 7.0 Client. I still can't start SQL Server Enterprise Manager. Can anyone help?
Thanks in advanc
JanJane, once again, have you considered using SQL Server 2000 Enterprise
Manager? You seem to have both installed on your machine, and when you try
to launch 7.0 it is looking in \80\ and causing a conflict. I suggest
uninstalling SQL 7.0 client, reinstalling 2000 client, installing 2000 SP3a,
and using 2000 client tools.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:C0397850-DCCD-4AEE-9ADF-AAD21DC84737@.microsoft.com...
> who knows how to fix this:
> MMC cannot open the file C:\Program Files\Microsoft SQL
> Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC.
> This may be because the file doesnt exist, is not an MMC console, or
> was created by a later version of MMC. This may also be because
> you do not have sufficient access rights to the file.
> I have rebooted the server, and restarted my machine, uninstalled and
reinstalled SQL Server 7.0 Client. I still can't start SQL Server Enterprise
Manager. Can anyone help?
> Thanks in advance
> Jane
>|||Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000. The problem is very strange. I suppose I am locked by the server. Don't know what to do now
As I said, I am new to SQL Server, I am trying to explore it. But there isn't a senior member in our team, so your help turns to be very important for me. I am looking forward to any ideas
Cheer
Jane|||Jane,
Refer the steps 3 to 5 given in the 'workaround' section of this article:
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000'
http://support.microsoft.com/default.aspx?id=272453
PS: I know that the title of the article doesnt concern you, but those steps
might help.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000.
The problem is very strange. I suppose I am locked by the server. Don't know
what to do now.
> As I said, I am new to SQL Server, I am trying to explore it. But there
isn't a senior member in our team, so your help turns to be very important
for me. I am looking forward to any ideas.
> Cheers
> Jane|||Thanks for your help, but it doesn't work. Any ideas
Jan
-- Dinesh T.K wrote: --
Jane
Refer the steps 3 to 5 given in the 'workaround' section of this article
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000
http://support.microsoft.com/default.aspx?id=27245
PS: I know that the title of the article doesnt concern you, but those step
might help
-
Dines
SQL Server MV
-
-
SQL Server FAQ a
http://www.tkdinesh.co
"Jane" <anonymous@.discussions.microsoft.com> wrote in messag
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com..
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000
The problem is very strange. I suppose I am locked by the server. Don't kno
what to do now
> As I said, I am new to SQL Server, I am trying to explore it. But ther
isn't a senior member in our team, so your help turns to be very importan
for me. I am looking forward to any ideas
> Cheer
> Jan|||Jane,
May be EM is missing some DLLs .The relevant ones are
sqlns.dll,sqlmmc.dll,sqldmo.dll,dtsui.dll and sqllex.dll.Usually you can
find them in c:\mssql7\binn\.
Try re-registering them using regsvr32.exe.After each one, try opening up
EM.
If this too doesnt help, see if a reinstall of the relevant MDAC helps.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> > Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server
2000.
> The problem is very strange. I suppose I am locked by the server.
Don't know
> what to do now.
> > As I said, I am new to SQL Server, I am trying to explore it. But
there
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
> > Cheers
> > Jane
>
>|||Jane,
What is the version of you mmc.exe? What is the OS and SP level of your
workstation?
--
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> > Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server
2000.
> The problem is very strange. I suppose I am locked by the server.
Don't know
> what to do now.
> > As I said, I am new to SQL Server, I am trying to explore it. But
there
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
> > Cheers
> > Jane
>
>sql

MMC Cannot open

who knows how to fix this:
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC.
This may be because the file doesnt exist, is not an MMC console, or
was created by a later version of MMC. This may also be because
you do not have sufficient access rights to the file.
I have rebooted the server, and restarted my machine, uninstalled and reinst
alled SQL Server 7.0 Client. I still can't start SQL Server Enterprise Manag
er. Can anyone help?
Thanks in advance
JaneJane, once again, have you considered using SQL Server 2000 Enterprise
Manager? You seem to have both installed on your machine, and when you try
to launch 7.0 it is looking in \80\ and causing a conflict. I suggest
uninstalling SQL 7.0 client, reinstalling 2000 client, installing 2000 SP3a,
and using 2000 client tools.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:C0397850-DCCD-4AEE-9ADF-AAD21DC84737@.microsoft.com...
> who knows how to fix this:
> MMC cannot open the file C:\Program Files\Microsoft SQL
> Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC.
> This may be because the file doesnt exist, is not an MMC console, or
> was created by a later version of MMC. This may also be because
> you do not have sufficient access rights to the file.
> I have rebooted the server, and restarted my machine, uninstalled and
reinstalled SQL Server 7.0 Client. I still can't start SQL Server Enterprise
Manager. Can anyone help?
> Thanks in advance
> Jane
>|||Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000. The
problem is very strange. I suppose I am locked by the server. Don't know wh
at to do now.
As I said, I am new to SQL Server, I am trying to explore it. But there isn'
t a senior member in our team, so your help turns to be very important for m
e. I am looking forward to any ideas.
Cheers
Jane|||Jane,
Refer the steps 3 to 5 given in the 'workaround' section of this article:
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000'
http://support.microsoft.com/default.aspx?id=272453
PS: I know that the title of the article doesnt concern you, but those steps
might help.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000.
The problem is very strange. I suppose I am locked by the server. Don't know
what to do now.
> As I said, I am new to SQL Server, I am trying to explore it. But there
isn't a senior member in our team, so your help turns to be very important
for me. I am looking forward to any ideas.
> Cheers
> Jane|||Thanks for your help, but it doesn't work. Any ideas?
Jane
-- Dinesh T.K wrote: --
Jane,
Refer the steps 3 to 5 given in the 'workaround' section of this article:
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000'
http://support.microsoft.com/default.aspx?id=272453
PS: I know that the title of the article doesnt concern you, but those steps
might help.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000.
The problem is very strange. I suppose I am locked by the server. Don't know
what to do now.
> As I said, I am new to SQL Server, I am trying to explore it. But there
isn't a senior member in our team, so your help turns to be very important
for me. I am looking forward to any ideas.
> Cheers
> Jane|||Jane,
May be EM is missing some DLLs .The relevant ones are
sqlns.dll,sqlmmc.dll,sqldmo.dll,dtsui.dll and sqllex.dll.Usually you can
find them in c:\mssql7\binn\.
Try re-registering them using regsvr32.exe.After each one, try opening up
EM.
If this too doesnt help, see if a reinstall of the relevant MDAC helps.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
2000.[vbcol=seagreen]
> The problem is very strange. I suppose I am locked by the server.
Don't know
> what to do now.
there[vbcol=seagreen]
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
>
>|||Jane,
What is the version of you mmc.exe? What is the OS and SP level of your
workstation?
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
2000.[vbcol=seagreen]
> The problem is very strange. I suppose I am locked by the server.
Don't know
> what to do now.
there[vbcol=seagreen]
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
>
>

Misterious Change of Compatibility Level in a Data Base

Hi everybody:

We have recently migrated our DDBB from SQL 2000 to SQL 2005 in several Servers. We have 2 DDBB per Server and the size of mdf files are between 10 and 40 GB.

We put Compatibility Level in 90 in SQL 2005 but when we arrive at work we see that our Maintenace Plans failed because the Compatibility Level of one of Data Bases changed to 70.

We have a Trace executing the whole day registrying the execution of stored procedure 'sp_dbcmptlevel' but in despite of Compatibility Level changes, the Trace does not registry anything.

Has anyone passed before me for this situation? Thank you in advance and greetings,

Nuria

After migrating (backup/restore or detach /attahc) to SQL Server 2005 have u changed the Comaptibility level? By default, the compatibility level will be 80. What was the compatibility leve of this database in sql 2000? check that. I assume that it was 70

Madhu

|||

your sql 2000 db probably would have had a compatability of either 80 or 70 (65,60 are not supported in sql 2005).......so once you restore it in sql 2005 it would be in the default compatability level as it was in sql 2000 unless you manually change it.......

|||

Yes, after migrating (attach in our case) to SQL 2005 we have changed the Compatibility Level to 90.

Not sure what was the Compatibility Level before migrating of this specific Server because we have 52 Servers in total; some of them had 65, others had 70 and other had 80.

The amazing thing is that Compatibility Level changes alone from 90 to 70.

|||

Yes, after migrating (attach in our case) to SQL 2005 we have changed the Compatibility Level to 90.

The amazing thing is that Compatibility Level changes alone from 90 to 70.

Mistakenly dropped database in SQL Server! Data recovery?

Could anyone please help with any ideas?
A database was mistakenly dropped in SQL Server. There were no backup files
. Nothing else has been written to the hard drive so the data should still
be on the hard drive (not overwritten). Can anyone help or offer any ideas
as to how I might be able t
o recover this? Is there data recovery software that will look at the hardd
rive to find and restore this data (similar to a recycle bin restore?) Any
assistance would be greatly appreciated as soon as possible. I would be ve
ry grateful for any ideas/s
uggestions.search on google for undelete or unerase softwares, there are plenty of them
available.
but they will work only till nothing else overrites on the disk.
And its always good to have backups of important databases.
regards,
harshal.
"Steve" <anonymous@.discussions.microsoft.com> wrote in message
news:404D6405-6AD1-48CB-BC01-5CEC9A87DD1A@.microsoft.com...
> Could anyone please help with any ideas?
> A database was mistakenly dropped in SQL Server. There were no backup
files. Nothing else has been written to the hard drive so the data should
still be on the hard drive (not overwritten). Can anyone help or offer any
ideas as to how I might be able to recover this? Is there data recovery
software that will look at the harddrive to find and restore this data
(similar to a recycle bin restore?) Any assistance would be greatly
appreciated as soon as possible. I would be very grateful for any
ideas/suggestions.

Mistakenly dropped database in SQL Server! Data recovery?

Could anyone please help with any ideas?
A database was mistakenly dropped in SQL Server. There were no backup files. Nothing else has been written to the hard drive so the data should still be on the hard drive (not overwritten). Can anyone help or offer any ideas as to how I might be able to recover this? Is there data recovery software that will look at the harddrive to find and restore this data (similar to a recycle bin restore?) Any assistance would be greatly appreciated as soon as possible. I would be very grateful for any ideas/suggestions.search on google for undelete or unerase softwares, there are plenty of them
available.
but they will work only till nothing else overrites on the disk.
And its always good to have backups of important databases.
regards,
harshal.
"Steve" <anonymous@.discussions.microsoft.com> wrote in message
news:404D6405-6AD1-48CB-BC01-5CEC9A87DD1A@.microsoft.com...
> Could anyone please help with any ideas?
> A database was mistakenly dropped in SQL Server. There were no backup
files. Nothing else has been written to the hard drive so the data should
still be on the hard drive (not overwritten). Can anyone help or offer any
ideas as to how I might be able to recover this? Is there data recovery
software that will look at the harddrive to find and restore this data
(similar to a recycle bin restore?) Any assistance would be greatly
appreciated as soon as possible. I would be very grateful for any
ideas/suggestions.

Mistake importing .db

I am trying to import files of the type .db but I am not getting. SQL
exhibits an error message. What can beWhat type of files are they?
>--Original Message--
>
>I am trying to import files of the type .db but I am not
getting. SQL
>exhibits an error message. What can be
>
>.
>

Missing transaction logs

can anyone please point me in the right direction as to how to go about rebuilding the transaction log files on a database?

here is the scenario:

1 - transaction log drive failed and transaction log file is basically gone.

2 - database file is fine.

3 - backup is too old or for all intents and purposes non-existent.

the server initially showed the database as suspect. the database was detached and an attempt was made to attach it with a recovered copy of the transaction log file but apparently it was too corrupted and the server didn't like it.

any suggestions would be greatly appreciated.

by the way, after looking at some of the posts here, i tried ApexSQL Log and Red-Gate Rescue bundle but these tools seem to require a database to at least show up on the database list, even if it is suspect.

the database doesn't even show up on the list since it was detached.

thanks in advance.

For SQL 2005, you could try attaching using CREATE DATABASE with the ATTACH_REBUILD_LOG option. This will only work if the data file was shut down cleanly, though.

If this does not work, you might try creating a new database, setting it OFFLINE with ALTER DATABASE, deleting the data and log file, copy the data file from your old database to be the one from the new database, set the database ONLINE with ALTER DATABASE (which will likely fail), and then set the database to EMERGENCY with ALTER DATABASE. Then you can look at the "DBCC Operation in Emergency Mode" section in the topic "DBCC (Transact-SQL)" to try to salvage the database.

|||

have u tried sp_attach_single_file_db

Madhu

|||

this is a SQL 2000 box.

would this still work?

|||

I hadn't tried what you suggest.

i looked it up in the help and it seems pretty clear that the database has to be detached in just the right way and at least one transaction log file needs to be available.

but, following your suggestion i tried it anyway and the response was basically the same as trying to mount the database in the usual way. The response to the attempt was: Could not open new database 'Lab_Config'. CREATE DATABASE is aborted. Device activation error. The physical file name 'L:\SqlLogs\Lab_Config_log.LDF' may be incorrect.

Drive L: is the destroyed drive.

|||

here is a rundown of what i did. maybe it is not correct or you have a suggestion on how this procedure can better be used to resolve this issue.

the statement used was taken from the help section for this stored procedure and it is as follows:

EXEC sp_attach_single_file_db @.dbname = 'LabConfig',
@.physname = 'E:\DataBases\Data\Lab_Config.mdf'

the response was:

Server: Msg 1813, Level 16, State 2, Line 1
Could not open new database 'LabConfig'. CREATE DATABASE is aborted.
Device activation error. The physical file name 'L:\SqlLogs\\Lab_Config_log.LDF' may be incorrect.

Please note the double reverse slash in the path in the response! does that look right?

i have several databases on this server that are without transaction logs. i tried the above stored procedure on all of them and the double reverse slash was present in all the responses.

by the way, drive L: has been replaced and it is now functional. the directory in SqlLogs exists and is configured with Full Access for Everyone.

|||

there should not be any log in the L drive while u run this command. make sure that 'L:\SqlLogs\\Lab_Config_log.LDF' if exists in L drive cut & paste to some other location and try the same. And also it reminds me that, this command only works with singel log and datafile database.

Madhu

|||

the L:\sqllogs directory is empty.

and all the databases in this condition are single log and datafile databases.

|||

You're going to have to use undocumented commands to get around this - please contact Product Support who will be able to help you use them correctly.

Thanks

Missing Tools after Setup

In the MSDE BOOKs there is a list of utilities and there directorys that i
should have:
x:\Program Files\Microsoft SQL Server\MSSQL\Binn1
-bcp2
-console
-isql2
-sqlagent
-sqldiag
-sqlmaint
-sqlservr
-vswitch
x:\Program Files\Microsoft SQL Server\80\Tools\Binn
-bcp2
-dtsrun
-dtswiz
-isql2
-isqlw
-itwiz
-odbccmpt
-osql
-rebuildm
-sqlftwiz
x:\Program Files\Microsoft SQL Server\80\Com
-distrib3
-logread3
-replmerg3
-snapshot3
x:\Program Files\Common Files\Microsoft Shared\Service Manager
-scm
x:\Program Files\Common Files\Microsoft Shared\?
-regxmlss
That is the list that i should have, here is the list that i do have:
x:\Program Files\Microsoft SQL Server\MSSQL\Binn1
-cmdwrap.exe
-sqlagent.exe
-sqlmaint.exe
-sqlservr.exe
x:\Program Files\Microsoft SQL Server\80\Tools\Binn
-bcp.exe
-cnfgsvr.exe
-dcomscm.exe
-DTSRUN.exe
-OSQL.exe
-scm.exe
-sqladhlp.exe
-sqlmangr.exe
-SVRNETCN.exe
x:\Program Files\Microsoft SQL Server\80\Com
-DISTRIB.exe
-replmerg.exe
-snapshot.exe
x:\Program Files\Common Files\Microsoft Shared\Service Manager
NO Service Manager Directory Exists
x:\Program Files\Common Files\Microsoft Shared\?
It says that this all should have been installed on the install by default
here is how installed
i moved my command prompt to the directory containing the setup folder
(C:\MSDERela)
then i ran
setup SAPWD="??"
this installed fine
what did i do wrong?
ALso i am very new to databases
the only thing that i have ever used is access which is pretty cut and dry.
I have had a lot of trouble finding simple tutorials for a beginner if any
one knows of one please let me know.
In the mean time a couple of quick questions:
1) does a database file have to be in the directory: C:\Program
Files\Microsoft SQL Server\MSSQL\Data
in order for it to work?
2) other than osql how can i access my data? The Books say that thre is a
SQL Server Query analyzer but could not find it (see beginning of post)
thanks Again for the help
WStoreyII
Hi,
I'm not sure which MSDE book you are referring to but the tools you mention
are those that are installed with SQL Server, not with the MSDE. The MSDE
ships with limited tools. The intention is that your application will do the
work. We have some tools you could try at our site. Others are at:
http://www.microsoft.com/sql/msde/pa.../default.aspx.
The data files do not have to be in a specific folder but you will find life
much easier if you have them all in a particular folder.
If you are going to be doing development for the MSDE, I'd strongly suggest
you purchase a copy of the SQL Server Developer Edition. I gather it's
currently only around $49 USD and provides a wealth of things you'll find
useful during development.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"WStoreyII" <WStoreyII@.discussions.microsoft.com> wrote in message
news:9109A07D-4093-4473-AB0A-CFDFD9611C06@.microsoft.com...
> In the MSDE BOOKs there is a list of utilities and there directorys that i
> should have:
> x:\Program Files\Microsoft SQL Server\MSSQL\Binn1
> -bcp2
> -console
> -isql2
> -sqlagent
> -sqldiag
> -sqlmaint
> -sqlservr
> -vswitch
> x:\Program Files\Microsoft SQL Server\80\Tools\Binn
> -bcp2
> -dtsrun
> -dtswiz
> -isql2
> -isqlw
> -itwiz
> -odbccmpt
> -osql
> -rebuildm
> -sqlftwiz
> x:\Program Files\Microsoft SQL Server\80\Com
> -distrib3
> -logread3
> -replmerg3
> -snapshot3
> x:\Program Files\Common Files\Microsoft Shared\Service Manager
> -scm
> x:\Program Files\Common Files\Microsoft Shared\?
> -regxmlss
> That is the list that i should have, here is the list that i do have:
> x:\Program Files\Microsoft SQL Server\MSSQL\Binn1
> -cmdwrap.exe
> -sqlagent.exe
> -sqlmaint.exe
> -sqlservr.exe
> x:\Program Files\Microsoft SQL Server\80\Tools\Binn
> -bcp.exe
> -cnfgsvr.exe
> -dcomscm.exe
> -DTSRUN.exe
> -OSQL.exe
> -scm.exe
> -sqladhlp.exe
> -sqlmangr.exe
> -SVRNETCN.exe
> x:\Program Files\Microsoft SQL Server\80\Com
> -DISTRIB.exe
> -replmerg.exe
> -snapshot.exe
> x:\Program Files\Common Files\Microsoft Shared\Service Manager
> NO Service Manager Directory Exists
> x:\Program Files\Common Files\Microsoft Shared\?
> It says that this all should have been installed on the install by default
> here is how installed
> i moved my command prompt to the directory containing the setup folder
> (C:\MSDERela)
> then i ran
> setup SAPWD="??"
> this installed fine
> what did i do wrong?
> ALso i am very new to databases
> the only thing that i have ever used is access which is pretty cut and
> dry.
> I have had a lot of trouble finding simple tutorials for a beginner if any
> one knows of one please let me know.
> In the mean time a couple of quick questions:
> 1) does a database file have to be in the directory: C:\Program
> Files\Microsoft SQL Server\MSSQL\Data
> in order for it to work?
> 2) other than osql how can i access my data? The Books say that thre is a
> SQL Server Query analyzer but could not find it (see beginning of post)
> thanks Again for the help
> WStoreyII
>
|||Greg's correct. MSDE was not intended to ship
with the full compliment of (management) tools
as SQL Server is.
If you're want to get up and running as quick as
possible then Microsoft Access (2000 and above)
is an excellent interface to MSDE for your own
internal development purposes. Micrsoft press has
a decent book on Access Data Projects also.
If you're wanting to use MSDE to develop a
distributable application, then you'll need to
be coding everything yourself.
Good luck.

Missing MDF files but databases run fine?

About two months ago, we had a problem with a couple SQL 2005 databases. We
got everything working and all has been fine. Today, I noticed that the
databases that we had a problem with have LDF file but no MDF files. I don't
know much about SQL but does that make sense? Is there any way to make the
MDF file at this point?
Thanks!
Arch WillinghamWhat do you mean by 'no MDF files'? You can have a scenario where the drive
that hosts a database file disappears and the database may still function as
usual for a while until it has to access the disk.
Linchi
"Arch Willingham" wrote:
> About two months ago, we had a problem with a couple SQL 2005 databases. We
> got everything working and all has been fine. Today, I noticed that the
> databases that we had a problem with have LDF file but no MDF files. I don't
> know much about SQL but does that make sense? Is there any way to make the
> MDF file at this point?
> Thanks!
> Arch Willingham
>
>|||Never mind....weird thing. I am a holdout thatstill uses the old file
manager (WINFILE.EXE). For whatever reason, teh MDF files are hidden to it
but they are there when you look at the directory with Explorer.
Weird as I can see all other hidden and system files.
Arch
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:CEE64FB0-73F3-483E-A4DF-3EEB750908DC@.microsoft.com...
> What do you mean by 'no MDF files'? You can have a scenario where the
> drive
> that hosts a database file disappears and the database may still function
> as
> usual for a while until it has to access the disk.
> Linchi
> "Arch Willingham" wrote:
>> About two months ago, we had a problem with a couple SQL 2005 databases.
>> We
>> got everything working and all has been fine. Today, I noticed that the
>> databases that we had a problem with have LDF file but no MDF files. I
>> don't
>> know much about SQL but does that make sense? Is there any way to make
>> the
>> MDF file at this point?
>> Thanks!
>> Arch Willingham
>>

Missing files after using File System Task

Hi All,

I don't know if anyone faced this issue. We are having a strange problem. Our process was working well when it was implemented on 32 bit processor.IT ran perfectly for 6 months with out a problem. But when we moved the packages to a 64 bit machine, this issue along with some other issues started to show up.

The issue is we are missing files in the source folder.

Our process is designed such that a source process, brings in a file and updates a status for the file in a audit table. The ETL process picks up the file, then assigns the status as ‘running’ when SRC process is complete and loads into Target DB, and updates ETL status to complete. But current problem is the ETL is losing files after it assigns the status as running. When we looked into the DB weather the data is loaded, we could not find any data related to these files.

we are have mapping level parameters for source path and target path.

We are using a For Each Loop task, and processing files(which are simple flat files) in the source path. The file name is stored in the mapping level parameter. Once the file is process we are moving them into a target path.

Our src and target file paths are on the same drive, just have src folder, inside src folder we have processed folder and failed folder. So files are picked from the source folder and moved into processed folder after processing. The files are not even moved to a failed folder.

There are lot other processing going on this box, and the trend observed is that when more processors are running at peak hour, the missing files’ count is more.

Right now we are refetching those files, as a work around, but does any one has any suggestion why this is happening or any better implementation suggestions?

Thanks

We solved our problem. This was due to the combination of problems.

1. Environment setup for our new 64 bit server

2. Use of event handler for 'On Error' instead of 'On task failure'.

3. Overwrite destination in move file task properties in Event handler.

4. Consistent connection (I don't exactly remember the word, but its in the properties of the connections in connection manager)

1st and 4th issue: The sympotom was the missing files were more when the system was too busy, also processing other packages. When we set up our initial 32 bit machine, we had our named pipes enabled on both client and server. so no issues. But in our new 64 bit environment, the server named pipes was disabled (Shared Memory, TCP/IP were enabled) and client's was enabled, so when client wants a connection, it looks in the same order, 1st Shared Memory, 2nd TCP/IP and last named pipes. But the server, only gives connection on first 2. So the connection were timing out in peak processing.

Added to that the connection properties in the package(4th issue), was not stable state, so every time, its encounters a task in the package which needs DB connection, its requests new connection. So this issue multiplied because the named pipes were disabled. So the solution to this both issues is, just enable named pipes on the server (or disable on client, enable is better since the process has extra options for connections). In the package conection properties, select connection as stable state. This option helps to have stable connection from the start of package execution to the end, instead of connection and disconnecting for each task.

2nd & 3rd issue: This issue was already present in our 32 bit also, but did not show up since we did not have connection failure error due to named pipes. Since connection was timing out on our new environment, each failure consitues to an error, so when the first error raised, the src file was moved to the destination folder(with overwrite destination option true). But due to connection failures, we had often multiple error events, so for subsequest error events, its tries to moved again the src file which is not present since it was moved the first time. So for subsequest errors, since we had overwrite destination option to true, the package first deletes the target files, and tries to move the file and fails, since the src file is not present. This leads to the missing file problem.

The solution to this problem is, just set overwrite destination option to false in file task. Based on your requirement, you can also have the event handler on the 'On Task Failure' event instead of 'on Error event'.

Hope this helps a lot of pains to lot of people, and saves lot of bucks to many companies.

Excuse my spelling mistakes if any.

Thanks,

Venkat

Missing files after using File System Task

Hi All,

I don't know if anyone faced this issue. We are having a strange problem. Our process was working well when it was implemented on 32 bit processor.IT ran perfectly for 6 months with out a problem. But when we moved the packages to a 64 bit machine, this issue along with some other issues started to show up.

The issue is we are missing files in the source folder.

Our process is designed such that a source process, brings in a file and updates a status for the file in a audit table. The ETL process picks up the file, then assigns the status as ‘running’ when SRC process is complete and loads into Target DB, and updates ETL status to complete. But current problem is the ETL is losing files after it assigns the status as running. When we looked into the DB weather the data is loaded, we could not find any data related to these files.

we are have mapping level parameters for source path and target path.

We are using a For Each Loop task, and processing files(which are simple flat files) in the source path. The file name is stored in the mapping level parameter. Once the file is process we are moving them into a target path.

Our src and target file paths are on the same drive, just have src folder, inside src folder we have processed folder and failed folder. So files are picked from the source folder and moved into processed folder after processing. The files are not even moved to a failed folder.

There are lot other processing going on this box, and the trend observed is that when more processors are running at peak hour, the missing files’ count is more.

Right now we are refetching those files, as a work around, but does any one has any suggestion why this is happening or any better implementation suggestions?

Thanks

We solved our problem. This was due to the combination of problems.

1. Environment setup for our new 64 bit server

2. Use of event handler for 'On Error' instead of 'On task failure'.

3. Overwrite destination in move file task properties in Event handler.

4. Consistent connection (I don't exactly remember the word, but its in the properties of the connections in connection manager)

1st and 4th issue: The sympotom was the missing files were more when the system was too busy, also processing other packages. When we set up our initial 32 bit machine, we had our named pipes enabled on both client and server. so no issues. But in our new 64 bit environment, the server named pipes was disabled (Shared Memory, TCP/IP were enabled) and client's was enabled, so when client wants a connection, it looks in the same order, 1st Shared Memory, 2nd TCP/IP and last named pipes. But the server, only gives connection on first 2. So the connection were timing out in peak processing.

Added to that the connection properties in the package(4th issue), was not stable state, so every time, its encounters a task in the package which needs DB connection, its requests new connection. So this issue multiplied because the named pipes were disabled. So the solution to this both issues is, just enable named pipes on the server (or disable on client, enable is better since the process has extra options for connections). In the package conection properties, select connection as stable state. This option helps to have stable connection from the start of package execution to the end, instead of connection and disconnecting for each task.

2nd & 3rd issue: This issue was already present in our 32 bit also, but did not show up since we did not have connection failure error due to named pipes. Since connection was timing out on our new environment, each failure consitues to an error, so when the first error raised, the src file was moved to the destination folder(with overwrite destination option true). But due to connection failures, we had often multiple error events, so for subsequest error events, its tries to moved again the src file which is not present since it was moved the first time. So for subsequest errors, since we had overwrite destination option to true, the package first deletes the target files, and tries to move the file and fails, since the src file is not present. This leads to the missing file problem.

The solution to this problem is, just set overwrite destination option to false in file task. Based on your requirement, you can also have the event handler on the 'On Task Failure' event instead of 'on Error event'.

Hope this helps a lot of pains to lot of people, and saves lot of bucks to many companies.

Excuse my spelling mistakes if any.

Thanks,

Venkat

Missing dll folder in SQL Server 2005

Hello, I have have some instructions to put a dll file in the folder
"C:\Program Files\Microsoft SQL Server\MSSQL\Binn\dll" which I see on a
machine with SQL Server 2000. On machines with SQL Server 2005 you have 3
folders MSSQL.1, MSSQL.2, MSSQL.3 and none of them have a dll folder. Where
do you think I would be the dll.
ThanksHi Don,
Are these instructions from a specific application? Does it mention if it is
compatible with SQL Server 2005?
Ben Nevarez
"Don" wrote:
> Hello, I have have some instructions to put a dll file in the folder
> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\dll" which I see on a
> machine with SQL Server 2000. On machines with SQL Server 2005 you have 3
> folders MSSQL.1, MSSQL.2, MSSQL.3 and none of them have a dll folder. Where
> do you think I would be the dll.
> Thanks
>|||Exactly my thoughts, Ben. My guess is that it is an extended stored procedure, and if the
instructions doesn't say how to install it on 2005, we shouldn't assume it has been tested on 2005.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:D1FD01B8-51AC-4570-92C7-EB0254257714@.microsoft.com...
> Hi Don,
> Are these instructions from a specific application? Does it mention if it is
> compatible with SQL Server 2005?
> Ben Nevarez
>
>
> "Don" wrote:
>> Hello, I have have some instructions to put a dll file in the folder
>> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\dll" which I see on a
>> machine with SQL Server 2000. On machines with SQL Server 2005 you have 3
>> folders MSSQL.1, MSSQL.2, MSSQL.3 and none of them have a dll folder. Where
>> do you think I would be the dll.
>> Thanks|||Yes, it's for a extended stored procedure called xp_calendar. And there are
notes about having it work with SQl 2005 just not about were to put the dll.
I had installed it on a SQL Server 2000 as a test and xp_calendar worked
well, but when I went to install it at the client running 2005 I saw that it
does not have the dll folder.
http://www.sqlservercentral.com/articles/Miscellaneous/2985/
http://www.logicom-inc.com/xp_sql2exchange/xp_sql2exchange.html
Thanks
Don
"Tibor Karaszi" wrote:
> Exactly my thoughts, Ben. My guess is that it is an extended stored procedure, and if the
> instructions doesn't say how to install it on 2005, we shouldn't assume it has been tested on 2005.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:D1FD01B8-51AC-4570-92C7-EB0254257714@.microsoft.com...
> >
> > Hi Don,
> >
> > Are these instructions from a specific application? Does it mention if it is
> > compatible with SQL Server 2005?
> >
> > Ben Nevarez
> >
> >
> >
> >
> > "Don" wrote:
> >
> >> Hello, I have have some instructions to put a dll file in the folder
> >> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\dll" which I see on a
> >> machine with SQL Server 2000. On machines with SQL Server 2005 you have 3
> >> folders MSSQL.1, MSSQL.2, MSSQL.3 and none of them have a dll folder. Where
> >> do you think I would be the dll.
> >>
> >> Thanks
> >>
>
>|||I would add the files to the binn folder and then adjust the paths in the file "xp_add.sql"
accordingly. You would need to find what folder (MSSQL.1 etc) corresponds to your instance name,
check the below reg key for that:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Don" <Don@.discussions.microsoft.com> wrote in message
news:0AC640AC-92C5-478F-82EA-6DD80D9BB418@.microsoft.com...
> Yes, it's for a extended stored procedure called xp_calendar. And there are
> notes about having it work with SQl 2005 just not about were to put the dll.
> I had installed it on a SQL Server 2000 as a test and xp_calendar worked
> well, but when I went to install it at the client running 2005 I saw that it
> does not have the dll folder.
> http://www.sqlservercentral.com/articles/Miscellaneous/2985/
> http://www.logicom-inc.com/xp_sql2exchange/xp_sql2exchange.html
> Thanks
> Don
> "Tibor Karaszi" wrote:
>> Exactly my thoughts, Ben. My guess is that it is an extended stored procedure, and if the
>> instructions doesn't say how to install it on 2005, we shouldn't assume it has been tested on
>> 2005.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:D1FD01B8-51AC-4570-92C7-EB0254257714@.microsoft.com...
>> >
>> > Hi Don,
>> >
>> > Are these instructions from a specific application? Does it mention if it is
>> > compatible with SQL Server 2005?
>> >
>> > Ben Nevarez
>> >
>> >
>> >
>> >
>> > "Don" wrote:
>> >
>> >> Hello, I have have some instructions to put a dll file in the folder
>> >> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\dll" which I see on a
>> >> machine with SQL Server 2000. On machines with SQL Server 2005 you have 3
>> >> folders MSSQL.1, MSSQL.2, MSSQL.3 and none of them have a dll folder. Where
>> >> do you think I would be the dll.
>> >>
>> >> Thanks
>> >>
>>