Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts

Friday, March 30, 2012

Running an Instance of SQL Server 2000 in SQL Server 2005

Can I run an instance of SQL Server 2000 in SQL Server 2005?

I was planning on restoring a backup of my SQL Server 2000 db to SS 2005, but keep the SS 2000 configuration. The main reason for doing so is to maintain the DTS packages I have in SS 2000 because my understanding is that these are not easily duplicated in SS 2005 Integration Services.

Thanks-Dave

You cannot run "an Instance of SQL Server 2000 in SQL Server 2005".

However, you can attach a SQL 2000 database to SQL 2005, and leave the 'compatibility level' set for SQL 2000.

But perhaps you mean to ask if you can ALSO have a SQL 2000 server INSTANCE on the same computer as a SQL 2005 server Instance -and if so, that would be 'Yes'. (You would actually 'install' the SQL 2000 software...)

|||

Arnie,

I do plan on attaching a SQL 2000 database to SQL 2005 and leaving the 'compatibility level' set for SQL 2000...

With that said, will I be able to access my DTS packages from SQL 2000? Where do I reference these in SQL 2005? If i'm running in SQL 2000 compatibility level will the SQL 2000 DTS packages function the same?

Thanks-David

|||

When you Attach /Resotre a SQL Server 2000 database in SQL Server 2005 instance , the compatibility level will be 80 (that is of sql server 2000) for this database. But its nothing to do with DTS. For DTS in sql server 2005 , you have an option for backward compatibility.

Open your SQL Server 2005 -- You can find "Management " node expand it -- you will find "Legacy" -- under it DTS

you can import DTS package of sql server 2000 here and you can run. But i would always recomment to re-design the DTS packages in SSIS , coz you have to anyway migrate this if not today , tomarrrow

Madhu

|||

Madhu,

Thanks for the response. I will import the SS 2000 DTS packages into SS 2205 and test. As for re-designing these in SSIS I will have to wait and see before moving forward.

David

sql

Friday, March 23, 2012

Running 64 Bit instance and 32 bit instance on Same Server

We are using an OEM ODBC connector that, to date, only works with the 32 bit
version of SQL 2005. My production server is a 64 bit version so I am still
maintaing the old server with the 32 bit for this ONE connectivity
requirement. The ODBC / OLEDB connector is used for a LINKED server to a
PROGRESS database.
Can I install the 32 BIT version of SQL on the same (64bit version of)
Windows Server 2003, and should I expect that the OEM ODBC driver would
function in the 32 bit instance as it does on the 32 bit Server?
--
Thanks~
JimDear Jim,
Thank you for posting here.
From your description, I understand that:
Your current ODBC connector is based on SQL Server 2005 32 bit; however
production server is a 64 bit version and you would like to know whether we
can install SQL Server 32bit on the 64 bit Windows Server 2003 and run both
64 bit and 32 bit SQL instances on it.
If I have misunderstood about your concern, feel free to let me know.
Windows Server 2003 64 bit Edition fully supports SQL Server 2005 32 bit
Editions. You can refer to the section "Operating System Requirements
(32-Bit)" of this article "Hardware and Software Requirements for
Installing SQL Server 2005":
http://msdn2.microsoft.com/en-us/library/ms143506.aspx
So, we are able to install the 32bit instance on the same 64 bit server. In
addition, we need to use "odbcad32.exe" on the 64bit system to configure
DSN for 32 bit driver. In most cases, the OEM ODBC connector should work in
this scenario. We can also contact the manufacturer of this ODBC connector
to confirm this.
If anything is unclear in my post, please don't hesitate to let me know.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Running 64 Bit instance and 32 bit instance on Same Server
| thread-index: Acgb8YBLwppW8NlwQ/C3lA9P6QDrsQ==| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?QmlnSmltQ2FzaA==?= <Bigjimcash@.noemail.noemail>
| Subject: Running 64 Bit instance and 32 bit instance on Same Server
| Date: Wed, 31 Oct 2007 12:09:03 -0700
| Lines: 12
| Message-ID: <EDE96934-8B17-4CDA-90D4-64D64211C8CF@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| Newsgroups: microsoft.public.sqlserver.server
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:29189
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| We are using an OEM ODBC connector that, to date, only works with the 32
bit
| version of SQL 2005. My production server is a 64 bit version so I am
still
| maintaing the old server with the 32 bit for this ONE connectivity
| requirement. The ODBC / OLEDB connector is used for a LINKED server to a
| PROGRESS database.
|
| Can I install the 32 BIT version of SQL on the same (64bit version of)
| Windows Server 2003, and should I expect that the OEM ODBC driver would
| function in the 32 bit instance as it does on the 32 bit Server?
| --
| Thanks~
| Jim
||||Dear Jim,
We wanted to see if the information provided was helpful. Please keep us
posted on your progress and let us know if you have any additional
questions or concerns.
We are looking forward to your response.
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| X-Tomcat-ID: 54548849
| References: <EDE96934-8B17-4CDA-90D4-64D64211C8CF@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-adamqu@.online.microsoft.com (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Thu, 01 Nov 2007 06:25:20 GMT
| Subject: RE: Running 64 Bit instance and 32 bit instance on Same Server
| X-Tomcat-NG: microsoft.public.sqlserver.server
| Message-ID: <7#wKAAFHIHA.4508@.TK2MSFTNGHUB02.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| Lines: 82
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:29229
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Dear Jim,
|
| Thank you for posting here.
|
| From your description, I understand that:
|
| Your current ODBC connector is based on SQL Server 2005 32 bit; however
| production server is a 64 bit version and you would like to know whether
we
| can install SQL Server 32bit on the 64 bit Windows Server 2003 and run
both
| 64 bit and 32 bit SQL instances on it.
|
| If I have misunderstood about your concern, feel free to let me know.
|
| Windows Server 2003 64 bit Edition fully supports SQL Server 2005 32 bit
| Editions. You can refer to the section "Operating System Requirements
| (32-Bit)" of this article "Hardware and Software Requirements for
| Installing SQL Server 2005":
| http://msdn2.microsoft.com/en-us/library/ms143506.aspx
|
| So, we are able to install the 32bit instance on the same 64 bit server.
In
| addition, we need to use "odbcad32.exe" on the 64bit system to configure
| DSN for 32 bit driver. In most cases, the OEM ODBC connector should work
in
| this scenario. We can also contact the manufacturer of this ODBC
connector
| to confirm this.
|
| If anything is unclear in my post, please don't hesitate to let me know.
|
| Have a nice day!
|
| Best regards,
|
| Adams Qu
| MCSE, MCDBA, MCTS
| Microsoft Online Support
|
| Microsoft Global Technical Support Center
|
| Get Secure! - www.microsoft.com/security
| =====================================================| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| =====================================================| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
| --
| | Thread-Topic: Running 64 Bit instance and 32 bit instance on Same Server
| | thread-index: Acgb8YBLwppW8NlwQ/C3lA9P6QDrsQ==| | X-WBNR-Posting-Host: 207.46.19.168
| | From: =?Utf-8?B?QmlnSmltQ2FzaA==?= <Bigjimcash@.noemail.noemail>
| | Subject: Running 64 Bit instance and 32 bit instance on Same Server
| | Date: Wed, 31 Oct 2007 12:09:03 -0700
| | Lines: 12
| | Message-ID: <EDE96934-8B17-4CDA-90D4-64D64211C8CF@.microsoft.com>
| | MIME-Version: 1.0
| | Content-Type: text/plain;
| | charset="Utf-8"
| | Content-Transfer-Encoding: 7bit
| | X-Newsreader: Microsoft CDO for Windows 2000
| | Content-Class: urn:content-classes:message
| | Importance: normal
| | Priority: normal
| | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| | Newsgroups: microsoft.public.sqlserver.server
| | Path: TK2MSFTNGHUB02.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:29189
| | NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| | X-Tomcat-NG: microsoft.public.sqlserver.server
| |
| | We are using an OEM ODBC connector that, to date, only works with the
32
| bit
| | version of SQL 2005. My production server is a 64 bit version so I am
| still
| | maintaing the old server with the 32 bit for this ONE connectivity
| | requirement. The ODBC / OLEDB connector is used for a LINKED server to
a
| | PROGRESS database.
| |
| | Can I install the 32 BIT version of SQL on the same (64bit version of)
| | Windows Server 2003, and should I expect that the OEM ODBC driver would
| | function in the 32 bit instance as it does on the 32 bit Server?
| | --
| | Thanks~
| | Jim
| |
|
|

Tuesday, March 20, 2012

Run SQL script on Instance Startup

Is there a way I can set up a SQL script to run when the instance
starts up?
SQL Server 2005 SP2

thanks!On Oct 18, 11:50 am, traceable1 <thham...@.gmail.comwrote:

Quote:

Originally Posted by

Is there a way I can set up a SQL script to run when the instance
starts up?
SQL Server 2005 SP2
>
thanks!


This link describes the use of 'Automatic Execution Stored Procedures'
than may fit the bill for what you are looking for.

http://msdn2.microsoft.com/en-us/library/ms191129.aspx|||Thank you!!

On Oct 18, 3:56 pm, Steve215 <stephen.mer...@.comcast.netwrote:

Quote:

Originally Posted by

On Oct 18, 11:50 am, traceable1 <thham...@.gmail.comwrote:
>

Quote:

Originally Posted by

Is there a way I can set up a SQL script to run when the instance
starts up?
SQL Server 2005 SP2


>

Quote:

Originally Posted by

thanks!


>
This link describes the use of 'Automatic Execution Stored Procedures'
than may fit the bill for what you are looking for.
>
http://msdn2.microsoft.com/en-us/library/ms191129.aspx

|||
Tibor Karaszi View profile
More options Oct 18, 10:58 am

Newsgroups: microsoft.public.sqlserver.server
From: "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com>
Date: Thu, 18 Oct 2007 17:58:37 +0200
Local: Thurs, Oct 18 2007 10:58 am
Subject: Re: Run script on Instance Startup
Reply | Reply to author | Forward | Print | Individual message | Show
original | Report this message | Find messages by this author
Put it in a stored procedure and mark the proc as an autostart proc
(sp_procoption).

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"traceable1" <thham...@.gmail.comwrote in message

news:1192722595.538697.92480@.y27g2000pre.googlegro ups.com...

- Hide quoted text -
- Show quoted text -

Quote:

Originally Posted by

Is there a way I can set up a SQL script to run when the instance
starts up?
SQL Server 2005 SP2


Quote:

Originally Posted by

thanks!


Reply Reply to author Forward Rate this post: Text
for clearing space

You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before
posting.
You do not have the permission required to post.

Tibor Karaszi View profile
More options Oct 18, 1:27 pm

Newsgroups: microsoft.public.sqlserver.server
From: "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com>
Date: Thu, 18 Oct 2007 20:27:45 +0200
Local: Thurs, Oct 18 2007 1:27 pm
Subject: Re: Run script on Instance Startup
Reply | Reply to author | Forward | Print | Individual message | Show
original | Report this message | Find messages by this author
Actually, one can claim that your alternative, Ekrem, is a cleaner
solution than mine. I.e., it
might feel better to have a client app (Agent) execute whatever TSQL
commands you want to run
instead of the database engine. (Of course, if one only start the
engine and not Agent, then the
script will not be executed.)

Good thinking. :-)

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Ekrem nsoy" <ek...@.btegitim.comwrote in message

news:1890C2B6-7DD2-40AE-AF10-01981F3ABD51@.microsoft.com...

- Hide quoted text -
- Show quoted text -

Quote:

Originally Posted by

Alternatively you can create a job to run your stuff which starts when SQL Server Agent starts...
(may not be as good as Tibor's suggestion :) but I already said, it's just an alternative)


Quote:

Originally Posted by

--
Ekrem nsoy


Quote:

Originally Posted by

"traceable1" <thham...@.gmail.comwrote in message
news:1192722595.538697.92480@.y27g2000pre.googlegro ups.com...


Quote:

Originally Posted by

Quote:

Originally Posted by

>Is there a way I can set up a SQL script to run when the instance
>starts up?
>SQL Server 2005 SP2


Quote:

Originally Posted by

Quote:

Originally Posted by

>thanks!


Reply Reply to author Forward Rate this post: Text
for clearing space

You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before
posting.
You do not have the permission required to post.

traceable1 View profile
More options Oct 18, 3:34 pm

Newsgroups: microsoft.public.sqlserver.server
From: traceable1 <thham...@.gmail.com>
Date: Thu, 18 Oct 2007 20:34:43 -0000
Local: Thurs, Oct 18 2007 3:34 pm
Subject: Re: Run script on Instance Startup
Reply | Reply to author | Forward | Print | Individual message | Show
original | Remove | Report this message | Find messages by this
author
Thank you so much for your feedback!

So how exactly would I set up the script to run when the Agent
starts?

On Oct 18, 1:27 pm, "Tibor Karaszi"

- Hide quoted text -
- Show quoted text -

<tibor_please.no.email_kara...@.hotmail.nomail.comwr ote:

Quote:

Originally Posted by

Actually, one can claim that your alternative, Ekrem, is a cleaner solution than mine. I.e., it
might feel better to have a client app (Agent) execute whatever TSQL commands you want to run
instead of the database engine. (Of course, if one only start the engine and not Agent, then the
script will not be executed.)


Quote:

Originally Posted by

Good thinking. :-)


Quote:

Originally Posted by

--
Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/...


Quote:

Originally Posted by

"Ekrem nsoy" <ek...@.btegitim.comwrote in message


Quote:

Originally Posted by

news:1890C2B6-7DD2-40AE-AF10-01981F3ABD51@.microsoft.com...


Quote:

Originally Posted by

Quote:

Originally Posted by

Alternatively you can create a job to run your stuff which starts when SQL Server Agent starts...
(may not be as good as Tibor's suggestion :) but I already said, it's just an alternative)


Quote:

Originally Posted by

Quote:

Originally Posted by

--
Ekrem nsoy


Quote:

Originally Posted by

Quote:

Originally Posted by

"traceable1" <thham...@.gmail.comwrote in message
news:1192722595.538697.92480@.y27g2000pre.googlegro ups.com...


Quote:

Originally Posted by

Quote:

Originally Posted by

Quote:

Originally Posted by

Is there a way I can set up a SQL script to run when the instance
starts up?
SQL Server 2005 SP2


Quote:

Originally Posted by

Quote:

Originally Posted by

Quote:

Originally Posted by

thanks!- Hide quoted text -


Quote:

Originally Posted by

- Show quoted text -


Reply Reply to author Forward

You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before
posting.
You do not have the permission required to post.

Tibor Karaszi View profile
More options Oct 18, 3:59 pm

Newsgroups: microsoft.public.sqlserver.server
From: "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com>
Date: Thu, 18 Oct 2007 22:59:38 +0200
Local: Thurs, Oct 18 2007 3:59 pm
Subject: Re: Run script on Instance Startup
Reply | Reply to author | Forward | Print | Individual message | Show
original | Report this message | Find messages by this author
Create an Agent job with one or several job steps containing your TSQL
(or whatever) code. Schedule
this job to be executed when Agent starts.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"traceable1" <thham...@.gmail.comwrote in message

news:1192739683.702442.18160@.k35g2000prh.googlegro ups.com...

Thank you so much for your feedback!

So how exactly would I set up the script to run when the Agent
starts?

On Oct 18, 1:27 pm, "Tibor Karaszi"

- Hide quoted text -
- Show quoted text -

<tibor_please.no.email_kara...@.hotmail.nomail.comwr ote:

Quote:

Originally Posted by

Actually, one can claim that your alternative, Ekrem, is a cleaner solution than mine. I.e., it
might feel better to have a client app (Agent) execute whatever TSQL commands you want to run
instead of the database engine. (Of course, if one only start the engine and not Agent, then the
script will not be executed.)


Quote:

Originally Posted by

Good thinking. :-)


Quote:

Originally Posted by

--
Tibor Karaszi, SQL Server
MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/...


Quote:

Originally Posted by

"Ekrem nsoy" <ek...@.btegitim.comwrote in message


Quote:

Originally Posted by

news:1890C2B6-7DD2-40AE-AF10-01981F3ABD51@.microsoft.com...


Quote:

Originally Posted by

Quote:

Originally Posted by

Alternatively you can create a job to run your stuff which starts when SQL Server Agent
starts...
(may not be as good as Tibor's suggestion :) but I already said, it's just an alternative)


Quote:

Originally Posted by

Quote:

Originally Posted by

--
Ekrem nsoy


Quote:

Originally Posted by

Quote:

Originally Posted by

"traceable1" <thham...@.gmail.comwrote in message
news:1192722595.538697.92480@.y27g2000pre.googlegro ups.com...


Quote:

Originally Posted by

Quote:

Originally Posted by

Quote:

Originally Posted by

Is there a way I can set up a SQL script to run when the instance
starts up?
SQL Server 2005 SP2


Quote:

Originally Posted by

Quote:

Originally Posted by

Quote:

Originally Posted by

thanks!- Hide quoted text -


Quote:

Originally Posted by

- Show quoted text -


On Oct 18, 3:56 pm, Steve215 <stephen.mer...@.comcast.netwrote:

Quote:

Originally Posted by

On Oct 18, 11:50 am, traceable1 <thham...@.gmail.comwrote:
>

Quote:

Originally Posted by

Is there a way I can set up a SQL script to run when the instance
starts up?
SQL Server 2005 SP2


>

Quote:

Originally Posted by

thanks!


>
This link describes the use of 'Automatic Execution Stored Procedures'
than may fit the bill for what you are looking for.
>
http://msdn2.microsoft.com/en-us/library/ms191129.aspx

Run simultaneously msde 2000 instance and one of 2005 express, possible?

Hi,
I got on my developer computer one instance of msde 2000. I want to test sql server express 2005, can I install it without "scrap" my other instance of 2000?

Strange question maybee, but it's what I wanna do!

Thanks all!

You can run these side by side as long as you give them different instances names.

Mike

|||Thanks Mike, I was waiting for an answer like that to launch the setup! :P

Bye

Run script on Instance Startup

Is there a way I can set up a SQL script to run when the instance
starts up?
SQL Server 2005 SP2
thanks!Put it in a stored procedure and mark the proc as an autostart proc (sp_procoption).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"traceable1" <thhamlin@.gmail.com> wrote in message
news:1192722595.538697.92480@.y27g2000pre.googlegroups.com...
> Is there a way I can set up a SQL script to run when the instance
> starts up?
> SQL Server 2005 SP2
> thanks!
>|||Actually, one can claim that your alternative, Ekrem, is a cleaner solution than mine. I.e., it
might feel better to have a client app (Agent) execute whatever TSQL commands you want to run
instead of the database engine. (Of course, if one only start the engine and not Agent, then the
script will not be executed.)
Good thinking. :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
news:1890C2B6-7DD2-40AE-AF10-01981F3ABD51@.microsoft.com...
> Alternatively you can create a job to run your stuff which starts when SQL Server Agent starts...
> (may not be as good as Tibor's suggestion :) but I already said, it's just an alternative)
> --
> Ekrem Önsoy
>
> "traceable1" <thhamlin@.gmail.com> wrote in message
> news:1192722595.538697.92480@.y27g2000pre.googlegroups.com...
>> Is there a way I can set up a SQL script to run when the instance
>> starts up?
>> SQL Server 2005 SP2
>> thanks!
>|||Thank you so much for your feedback!
So how exactly would I set up the script to run when the Agent starts?
On Oct 18, 1:27 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Actually, one can claim that your alternative, Ekrem, is a cleaner soluti=on than mine. I.e., it
> might feel better to have a client app (Agent) execute whatever TSQL comm=ands you want to run
> instead of the database engine. (Of course, if one only start the engine =and not Agent, then the
> script will not be executed.)
> Good thinking. :-)
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asp=
http://sqlblog.com/blogs/tibor_karaszi
> "Ekrem =D6nsoy" <ek...@.btegitim.com> wrote in message
> news:1890C2B6-7DD2-40AE-AF10-01981F3ABD51@.microsoft.com...
>
> > Alternatively you can create a job to run your stuff which starts when =SQL Server Agent starts...
> > (may not be as good as Tibor's suggestion :) but I already said, it's j=ust an alternative)
> > --
> > Ekrem =D6nsoy
> > "traceable1" <thham...@.gmail.com> wrote in message
> >news:1192722595.538697.92480@.y27g2000pre.googlegroups.com...
> >> Is there a way I can set up a SQL script to run when the instance
> >> starts up?
> >> SQL Server 2005 SP2
> >> thanks!- Hide quoted text -
> - Show quoted text -|||Create an Agent job with one or several job steps containing your TSQL (or whatever) code. Schedule
this job to be executed when Agent starts.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"traceable1" <thhamlin@.gmail.com> wrote in message
news:1192739683.702442.18160@.k35g2000prh.googlegroups.com...
Thank you so much for your feedback!
So how exactly would I set up the script to run when the Agent starts?
On Oct 18, 1:27 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Actually, one can claim that your alternative, Ekrem, is a cleaner solution than mine. I.e., it
> might feel better to have a client app (Agent) execute whatever TSQL commands you want to run
> instead of the database engine. (Of course, if one only start the engine and not Agent, then the
> script will not be executed.)
> Good thinking. :-)
> --
> Tibor Karaszi, SQL Server
> MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "Ekrem Önsoy" <ek...@.btegitim.com> wrote in message
> news:1890C2B6-7DD2-40AE-AF10-01981F3ABD51@.microsoft.com...
>
> > Alternatively you can create a job to run your stuff which starts when SQL Server Agent
> > starts...
> > (may not be as good as Tibor's suggestion :) but I already said, it's just an alternative)
> > --
> > Ekrem Önsoy
> > "traceable1" <thham...@.gmail.com> wrote in message
> >news:1192722595.538697.92480@.y27g2000pre.googlegroups.com...
> >> Is there a way I can set up a SQL script to run when the instance
> >> starts up?
> >> SQL Server 2005 SP2
> >> thanks!- Hide quoted text -
> - Show quoted text -|||Excellent! Thank ya'll so much!!
On Oct 18, 3:59 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Create an Agent job with one or several job steps containing your TSQL (o=r whatever) code. Schedule
> this job to be executed when Agent starts.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asp=
http://sqlblog.com/blogs/tibor_karaszi
> "traceable1" <thham...@.gmail.com> wrote in message
> news:1192739683.702442.18160@.k35g2000prh.googlegroups.com...
> Thank you so much for your feedback!
> So how exactly would I set up the script to run when the Agent starts?
> On Oct 18, 1:27 pm, "Tibor Karaszi"
>
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> > Actually, one can claim that your alternative, Ekrem, is a cleaner solu=tion than mine. I.e., it
> > might feel better to have a client app (Agent) execute whatever TSQL co=mmands you want to run
> > instead of the database engine. (Of course, if one only start the engin=e and not Agent, then the
> > script will not be executed.)
> > Good thinking. :-)
> > --
> > Tibor Karaszi, SQL Server
> > MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs=
/=2E..
> > "Ekrem =D6nsoy" <ek...@.btegitim.com> wrote in message
> >news:1890C2B6-7DD2-40AE-AF10-01981F3ABD51@.microsoft.com...
> > > Alternatively you can create a job to run your stuff which starts whe=n SQL Server Agent
> > > starts...
> > > (may not be as good as Tibor's suggestion :) but I already said, it's= just an alternative)
> > > --
> > > Ekrem =D6nsoy
> > > "traceable1" <thham...@.gmail.com> wrote in message
> > >news:1192722595.538697.92480@.y27g2000pre.googlegroups.com...
> > >> Is there a way I can set up a SQL script to run when the instance
> > >> starts up?
> > >> SQL Server 2005 SP2
> > >> thanks!- Hide quoted text -
> > - Show quoted text -- Hide quoted text -
> - Show quoted text -|||*** Sent via Developersdex http://www.developersdex.com ***|||Alternatively you can create a job to run your stuff which starts when SQL
Server Agent starts... (may not be as good as Tibor's suggestion :) but I
already said, it's just an alternative)
--
Ekrem Önsoy
"traceable1" <thhamlin@.gmail.com> wrote in message
news:1192722595.538697.92480@.y27g2000pre.googlegroups.com...
> Is there a way I can set up a SQL script to run when the instance
> starts up?
> SQL Server 2005 SP2
> thanks!
>|||:-)
--
Ekrem Önsoy
http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
MCBDA, MCTS: SQL Server 2005, MCITP:DBA, MCSD.Net, MCSE, MCT
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:B15F3A8E-AAFF-44D1-9BEB-CFA9845E2DEE@.microsoft.com...
> Actually, one can claim that your alternative, Ekrem, is a cleaner
> solution than mine. I.e., it might feel better to have a client app
> (Agent) execute whatever TSQL commands you want to run instead of the
> database engine. (Of course, if one only start the engine and not Agent,
> then the script will not be executed.)
> Good thinking. :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
> news:1890C2B6-7DD2-40AE-AF10-01981F3ABD51@.microsoft.com...
>> Alternatively you can create a job to run your stuff which starts when
>> SQL Server Agent starts... (may not be as good as Tibor's suggestion :)
>> but I already said, it's just an alternative)
>> --
>> Ekrem Önsoy
>>
>> "traceable1" <thhamlin@.gmail.com> wrote in message
>> news:1192722595.538697.92480@.y27g2000pre.googlegroups.com...
>> Is there a way I can set up a SQL script to run when the instance
>> starts up?
>> SQL Server 2005 SP2
>> thanks!
>>
>

Monday, March 12, 2012

Run out of alphabets

When you set up say 3 active and 1 passive multi instance cluster and
especially if any one instance uses say 10 alphabets, how do you configure
the cluster then ? Can you use something other than alphabets for your
resources ? This would be tied to a SAN too...
First investigate mount-points on cluster service :
http://support.microsoft.com/kb/280297
Then investigate mount-points for SQL :
http://support.microsoft.com/kb/819546/
HTH,
_Edwin.
"Hassan" <hassan@.hotmail.com> wrote in message
news:uM0CygnRHHA.3812@.TK2MSFTNGP06.phx.gbl...
> When you set up say 3 active and 1 passive multi instance cluster and
> especially if any one instance uses say 10 alphabets, how do you configure
> the cluster then ? Can you use something other than alphabets for your
> resources ? This would be tied to a SAN too...
>
|||"Edwin vMierlo" <EdwinvMierlo@.discussions.microsoft.com> wrote in message
news:uuYXgOqRHHA.1228@.TK2MSFTNGP06.phx.gbl...
> First investigate mount-points on cluster service :
> http://support.microsoft.com/kb/280297
> Then investigate mount-points for SQL :
> http://support.microsoft.com/kb/819546/
and then redesign you cluster to make sure you have enough drive letters...
I have seen and heard bad things about using mount points both in Exchange
and in SQL.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Denver starting Feb 12th
NYC starting Feb 19th
London starting March 6th
|||Mount points seem a lot more stable in SQL 2005, at least from what I have
seen and heard.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Russ Kaufmann [MVP]" <russ@.clusterhelp.com> wrote in message
news:ue$7SNuRHHA.2256@.TK2MSFTNGP02.phx.gbl...
> "Edwin vMierlo" <EdwinvMierlo@.discussions.microsoft.com> wrote in message
> news:uuYXgOqRHHA.1228@.TK2MSFTNGP06.phx.gbl...
> and then redesign you cluster to make sure you have enough drive
> letters...
> I have seen and heard bad things about using mount points both in Exchange
> and in SQL.
>
> --
> Russ Kaufmann
> MVP - Windows Server - Clustering
> ClusterHelp.com, a Microsoft Certified Gold Partner
> Web http://www.clusterhelp.com
> Blog http://msmvps.com/clusterhelp
> The next ClusterHelp classes are:
> Denver starting Feb 12th
> NYC starting Feb 19th
> London starting March 6th
>
|||I have tested using mounted volumes in SQL2005 quite extensively. Apart from
the fact that they forgot to require the dependency of SQL Server on a
mounted volume, I don't see any serious issue with supporting mounted volumes
with SQL2005 in a cluster.
Linchi
"Russ Kaufmann [MVP]" wrote:

> "Edwin vMierlo" <EdwinvMierlo@.discussions.microsoft.com> wrote in message
> news:uuYXgOqRHHA.1228@.TK2MSFTNGP06.phx.gbl...
> and then redesign you cluster to make sure you have enough drive letters...
> I have seen and heard bad things about using mount points both in Exchange
> and in SQL.
>
> --
> Russ Kaufmann
> MVP - Windows Server - Clustering
> ClusterHelp.com, a Microsoft Certified Gold Partner
> Web http://www.clusterhelp.com
> Blog http://msmvps.com/clusterhelp
> The next ClusterHelp classes are:
> Denver starting Feb 12th
> NYC starting Feb 19th
> London starting March 6th
>
>
|||I must admit I have seen bad things with mountpoints as well, however I have
yet to find a case where it is not related to bad configuration, and
predominantly the setup of dependencies.
rgds,
Edwin.
"Russ Kaufmann [MVP]" <russ@.clusterhelp.com> wrote in message
news:ue$7SNuRHHA.2256@.TK2MSFTNGP02.phx.gbl...
> "Edwin vMierlo" <EdwinvMierlo@.discussions.microsoft.com> wrote in message
> news:uuYXgOqRHHA.1228@.TK2MSFTNGP06.phx.gbl...
> and then redesign you cluster to make sure you have enough drive
letters...
> I have seen and heard bad things about using mount points both in Exchange
> and in SQL.
>
> --
> Russ Kaufmann
> MVP - Windows Server - Clustering
> ClusterHelp.com, a Microsoft Certified Gold Partner
> Web http://www.clusterhelp.com
> Blog http://msmvps.com/clusterhelp
> The next ClusterHelp classes are:
> Denver starting Feb 12th
> NYC starting Feb 19th
> London starting March 6th
>
|||If you are running SS2K or a mix of SS2K and SS2K5, then you have found the
limitation with multi-instancing and clusters: SQL Server 2000 does not
support drive mount points, at all, not even for SS2K5 on the same cluster.
http://support.microsoft.com/kb/819546/en-us
If you are only running SS2K5, then mount points are supported. You would
use 1 drive letter for the base drive, but then use mount points for the
remainder. You would need to create one lettered drive for each resource
group/SQL Server instance.
http://support.microsoft.com/kb/280297/
Sincerely,
Anthony Thomas

"Hassan" <hassan@.hotmail.com> wrote in message
news:uM0CygnRHHA.3812@.TK2MSFTNGP06.phx.gbl...
> When you set up say 3 active and 1 passive multi instance cluster and
> especially if any one instance uses say 10 alphabets, how do you configure
> the cluster then ? Can you use something other than alphabets for your
> resources ? This would be tied to a SAN too...
>