SQL Manager.msc help help help

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

hey Z

i get the 120 eval of SQL from MS$$
and of course it needs to have a CSLID attached to it which i am sure is generated from an installtion to that server and DB correct? (novice speaking here)

crap! you mean i just cant get an MMC and have it work with like click it imports?? no no no yu have to do what to import this
msc mmc snapin? how do i generate its needed CSLID???
thanks

I am going to my sons football game..but will look what you experience DBA masters say
thanks Z

robert(itdaddy).....morelike itdummy! crap
need DBA training in MSSQL now!!!!!!!!!!!!!

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Did anybody else's brain hurt after reading this?

Seriously - I'm not sure what you're trying to say here. You probably need to swallow the pill and make a call to Symantec PSS and explain your situation to them. I have a feeling that problems in your organisation may run a little bit deeper than this, if you are being expected to try to rectify a DB error despite the OSQL commands not working - there is (I state this categorically) NO WAY ON GOD'S EARTH that you will be able to detach and reattach the DB with the GUI tool if you couldn't do it with OSQL - OSQL uses the exact same method for detaching and reattaching a DB as Enterprise Mangler does.

Seriously - call Symantec and see what they say.

 

hey big Z here is the answer to my Veritas MSSQL issue.

event id say database corrupt or not found.

a week ago i changed the digital certifiate on our Mail server
cause i was trying to adjust and give it the correct name
for IE web outlook access security screen to not appear.

lo and behold i fu$$ it up.. come to find out

MSSQL uses SSL and dig cert to authenticate to Veritas
so when this certificate was redone by me; no more secure authentication (bad linkage errrors)
so when i exported the certs i needed to keep
and started MSSQL without them and then imported them
it kept track of the new dig certs i need and walla!

linkage good and Veritas backup again.

well i learned alot from the Veritas Engineer
to me it was fun but i hate screwing up due to lack of knowldge
but the only way i can get more is to go thru the trenches; just dont like to look bad; but admited to my boss it was my fault
he said i learned that is what matters; i am glad i did
wow did i learn alot and how to maintain the database
thru the BE utilitty once in while when auto doesnt work
but thought i would report this finding.
that yes Veritas and MSSQ use the SSL and dig cert
to authen to eachother.
go figure.

i had a hunch it was this;

]
but linkage goood and path found!

yeah!

itdaddy (no more virgin for me on MSSQL) ouch!

 

The beta of SQL Server 2005 would screw up SQL Server 2000 EM, but the gamma (release) works side-by-side with the old client utilities just fine. In fact, I can say definitively from experience that SQL Server 7.0 EM manager would co-exist with the 6.5 EM too, as I had to run that setup on my workstation for many years. And on the server end, in 7.0 you had to use the "switch" utility to rename services and restart an old 6.5 installation, but it too could be installed on the same box. Since 2000 and named instances was/were introduced, you've been able to run the server services side-by-side without any such utility. I have an XP Home box running SQL Server 2000 and 2005 Developer Editions at the same time (as named instances) right now, as a matter of fact.